[NeXus-committee] DECTRIS example summary
yayahjb
yayahjb at gmail.com
Mon Jan 14 14:18:03 GMT 2013
The one fussy disagreement I have with this summary would be on
signal=1. I am not sure this matters, but I think the current rule is that
we are only supposed to have one dataset with "plottable" data, i.e.
with signal=1. If that rule is important, then I we probably should
ask for signal=2, signal=3, etc. on the second, third, etc. dataset.
I think this is actually consistent with an old NeXus rule when you had
multiple datasets. The alternatives would be to change the rule and
say either:
You can have multiple plotable datasets with signal=1 or
The plotable datasets have signal=n, where n designates
the order of plotting, starting with 1.
The second version would be consistent with this particular data.
Sorry to be fussy
Regards,
Herbert
On 1/14/13 8:38 AM, Mark Koennecke wrote:
> Hi,
>
> from your feedback and my own study I find that there are the
> following problems
> with the example file as is:
>
> - Structure is wrong regarding linked data sets. Should be either:
>
> * entry:NXentry/data_00001:NXdata/data (Preferred ....)
> * entry:NXData/data:NXdata/data_0001
>
> - On data, signal=1 attribute is missing
> - On external link, NeXus attribute
> NAPIMOUNT=nxfile://th02c_ps02_1_data_000001.h5#data
> missing
> - In detector, flatfield, efficiency data is missing. This is not
> critical,
> I just wonder.
>
> Am I right? Is this what I tell DECTRIS tomorrow? Or do I miss something?
>
> Also, what is the opinion, do we need another Telco on this one?
>
> Regards,
>
> Mark
>
>
> _______________________________________________
> NeXus-committee mailing list
> NeXus-committee at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-committee
>
More information about the NeXus-committee
mailing list