<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Dear Andy,</div>
<div class=""><br class="">
</div>
<div class="">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. </div>
<div class=""><br class="">
</div>
<div class="">Otherwise Pete has written something on subentry that may help. If it doesn’t speak up!</div>
<div class=""><br class="">
</div>
<div class="">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. </div>
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class=""><br class="">
</div>
<div class="">Tobias</div>
<div class=""><br class="">
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 12 Feb 2015, at 17:39, Andrew GOETZ <<a href="mailto:andy.gotz@ESRF.FR" class="">andy.gotz@ESRF.FR</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class="">Hi,<br class="">
<br class="">
at the ESRF we were looking at the application definitions and saw by chance that the fluorescence one:
<br class="">
<br class="">
<a class="moz-txt-link-freetext" href="http://download.nexusformat.org/doc/html/classes/applications/NXfluo.html">http://download.nexusformat.org/doc/html/classes/applications/NXfluo.html</a><br class="">
<br class="">
has a typo in it which makes it unusable as it is :<br class="">
<br class="">
<p class=""><strong class="">data</strong>: <a class="internal reference" href="http://download.nexusformat.org/doc/html/classes/base_classes/NXdata.html#nxdata">
<em class="">NXdata</em></a></p>
<blockquote class="">
<div class="">
<p class=""><strong class="">energy</strong> –> /entry/instrument/fluorecence/energy</p>
<p class=""><strong class="">data</strong> –> /entry/instrument/fluorecence/data<br class="">
</p>
</div>
</blockquote>
This begs the question : how many sites are using the Application definitions and how do you get around the bugs?
<br class="">
<br class="">
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.<br class="">
<br class="">
Our second question is : does this bother anyone else than us? <br class="">
<br class="">
Kind regards<br class="">
<br class="">
Andy + Christophe<br class="">
<div class=""><br class="">
</div>
<br class="">
</div>
_______________________________________________<br class="">
NeXus mailing list<br class="">
<a href="mailto:NeXus@nexusformat.org" class="">NeXus@nexusformat.org</a><br class="">
http://lists.nexusformat.org/mailman/listinfo/nexus<br class="">
</div>
</blockquote>
</div>
<br class="">
</body>
</html>