[Nexus] Basic questions about application definitions

[Andrew GOETZ]

Dear Tobias + Pete,

thank you both for your quick replies. They clarify the situation a lot.

I understand it is difficult to know who is using the application 
definitions but maybe a survey could be done on the mailing list to find 
out how many use which application definition and which software 
implements them.

Regards

Andy

On 12/02/2015 18:07, Tobias Richter wrote:
> Dear Andy,
>
> To answer your first second question first (before I forget): I have 
> not come across anything in NeXus that requires you to duplicate data. 
> Linking is always allowed. There are some opposite cases like the one 
> you quote below, where linking is mandated in a particular way. In my 
> view that’s more of a legacy item. As long as data can be retrieved 
> from the specified location using the underlying contain format, I 
> don’t care how it gets there.
>
> Otherwise Pete has written something on subentry that may help. If it 
> doesn’t speak up!
>
> The majority of the application definitions where generated at some 
> point far back in time with the best intentions. You have to start 
> somewhere, right? Most facilities are only now slowly taking up the 
> task to implement them (fully). When problems are found we try and 
> resolve them. Unfortunately there is not yet an army of volunteers out 
> there that implements and tests everything for us.
>
> Regards,
>
> Tobias
>
>
>> On 12 Feb 2015, at 17:39, Andrew GOETZ <andy.gotz at ESRF.FR 
>> <mailto:andy.gotz at ESRF.FR>> wrote:
>>
>> Hi,
>>
>> at the ESRF we were looking at the application definitions and saw by 
>> chance that the fluorescence one:
>>
>> http://download.nexusformat.org/doc/html/classes/applications/NXfluo.html
>>
>> has a typo in it which makes it unusable as it is :
>>
>> *data*: /NXdata/ 
>> <http://download.nexusformat.org/doc/html/classes/base_classes/NXdata.html#nxdata>
>>
>>     *energy* –> /entry/instrument/fluorecence/energy
>>
>>     *data* –> /entry/instrument/fluorecence/data
>>
>> This begs the question : how many sites are using the Application 
>> definitions and how do you get around the bugs?
>>
>> A second question we had is that the way the application definitions 
>> are defined today implies they duplicate data in the file instead of 
>> linking to it. This is because they insist on creating NXsubentry. 
>> Please correct me if we have misunderstood the use of NXsubentry.
>>
>> Our second question is : does this bother anyone else than us?
>>
>> Kind regards
>>
>> Andy + Christophe
>>
>>
>> _______________________________________________
>> NeXus mailing list
>> NeXus at nexusformat.org <mailto:NeXus at nexusformat.org>
>> http://lists.nexusformat.org/mailman/listinfo/nexus
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nexusformat.org/pipermail/nexus/attachments/20150212/4c6da3dc/attachment.html>