[NeXus-committee] obsolescence and evolution: NeXus needs a historic dimension

[Osborn, Raymond]

Joachim,
I don’t think we’ve had sufficiently powerful generic NeXus visualization tools, which is one of the reasons for developing NeXpy. I think that’s the reason why NeXus has largely been used to archive facility data and hasn’t been used much by facility users. I hope that will change as more tools become available.

I think that instrument scientists at ISIS and SNS have come to depend on the Mantid framework to do the method-specific reduction. It can read the raw NeXus files created by their instruments and export the reduced data in NeXus format, but it can’t read generic NeXus files (level 1 and 2 in my previous email) as far as I’m aware.

Ray

On Jul 16, 2014, at 9:48 AM, Joachim Wuttke <j.wuttke at fz-juelich.de> wrote:

> Pete, thank you for this background information
> 
>> That contract is that the data  file provides the data for default visualization.
> 
> So far, I have not at all thought of default visualization as
> a key feature of NeXus.
> 
> Are raw NeXus visualization tools actually used by instrument
> scientists? Where? Why aren't they running their raw-data through
> some method-specific reduction?
> 
> - Joachim
> 
> _______________________________________________
> NeXus-committee mailing list
> NeXus-committee at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-committee

-- 
Ray Osborn, Senior Scientist
Materials Science Division
Argonne National Laboratory
Argonne, IL 60439, USA
Phone: +1 (630) 252-9011
Email: ROsborn at anl.gov