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

[Tobias.Richter at diamond.ac.uk]

Maybe there is a lesson to be learned from the fact that one of the success stories for an application definition does not actually define an application at all. Similarly the hard and important parts of defining the "application definition" for crystallography are not really specific to the technique. 
I can certainly see value in capturing calibration information in a certain way for a particular technique, like in NXtomto. But we find here that same method is now used for ptychography. 
We might be using the wrong basis for our application vector space. 

Regards,

Tobias


> -----Original Message-----
> From: NeXus-committee [mailto:nexus-committee-bounces at nexusformat.org]
> On Behalf Of Peterson, Peter F.
> Sent: 16 July 2014 14:34
> To: nexus-committee at nexusformat.org
> Subject: Re: [NeXus-committee] obsolescence and evolution: NeXus needs
> a historic dimension
> 
> Event files are actually a success story
> https://github.com/nexusformat/definitions/blob/master/contributed_defi
> niti
> ons/NXsnsevent.nxdl.xml and
> https://github.com/nexusformat/definitions/blob/master/base_classes/NXe
> vent
> _data.nxdl.xml .
> 
> While the definition is hiding the ³contributed_definitions² area, it
> was written by NIAC members (in 2011) with modifications to make data
> fields be usable in muon measurements as well as the TOF neutrons that
> it was created for. Both SNS and ISIS write out event data that
> validate using the definition and can be read by the same code without
> specialization.
> NeXus does have sharable files across instruments and facilities, even
> if it is for ³just for raw² data.
> 
> P^2
> 
> On 7/16/14, 9:05 AM, "Pete Jemian" <prjemian at gmail.com> wrote:
> 
> >
> >
> >On 7/16/2014 7:13 AM, Joachim Wuttke wrote:
> >> Anyway, formal validity is perhaps a necessary, but certainly not a
> >> sufficient condition for interoperability.
> >
> >This is actually a goal for any NeXus application definition.  A NeXus
> >data file that is valid against the relevant application definition
> >meets the structural criteria declared sufficient for
> interoperability.
> >
> >Perhaps another measure of interoperability is the data content.  The
> >data might be arranged in a NeXus data file with valid structure but
> >useless content for the processing step (such as no valid range of
> data
> >satisfying the Guinier approximation in small-angle scattering or no
> >intensity peaks for powder diffraction analysis).  Standardization of
> >data content or quality is not addressed by NeXus.
> >
> >Pete
> >
> >_______________________________________________
> >NeXus-committee mailing list
> >NeXus-committee at nexusformat.org
> >http://lists.nexusformat.org/mailman/listinfo/nexus-committee
> 
> 
> _______________________________________________
> NeXus-committee mailing list
> NeXus-committee at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-committee

-- 
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom