<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>Hi Mark,</div>
<div>I’m sorry I missed the Telco. However, I still think the design section that I replaced is not acceptable as it currently stands. It does not reflect the section title, ‘Design Principles’, at all. If there is repetition, then I think some refactoring
of the text will be essential if the new reader is not to be completely confused by the time they get to Section III.</div>
<div><br>
</div>
<div>I’m busy the next couple of days, but I’ll have another look at the weekend.</div>
<div><br>
</div>
<div>Ray</div>
<br>
<div>
<div>On Oct 2, 2014, at 4:45 AM, Mark Könnecke <<a href="mailto:mark.koennecke@psi.ch">mark.koennecke@psi.ch</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
Dear Ray,<br>
<br>
Am 11.09.2014 um 01:11 schrieb Osborn, Raymond <<a href="mailto:rosborn@anl.gov">rosborn@anl.gov</a>>:<br>
<br>
<blockquote type="cite">Dear colleagues,<br>
I have just uploaded a separate branch to the ‘communications’ repository that contains a revised version of the paper. I must apologize for being so late in the game. I know that there has been a lot of edits made over the past month, and most of the paper
I thought was perfectly fine. However, I did feel that Section II, the Design Principles, didn’t provide the kind of overview that someone completely new to NeXus would need, so I have largely rewritten it.<br>
<br>
A few other changes:<br>
<br>
1) I removed “This is a very important use case” from the abstract. I think that’s redundant - it’s obviously important or we wouldn’t describe it as the first purpose of the format. I also switched “experiment” for “beamline” - non-facility users might be
vague about what a beamline is.<br>
2) I added the old Physica B reference from 1997. I think it shows how consistent we’ve been in our design principles, but it could be removed if people don’t want it.<br>
3) In the introduction, I changed “A link structure” to “Features to enable rapid data visualization.” The original implies that data in the NXdata is nearly always linked to an NXdetector group, but we later talk about processed data not requiring links so
it’s not mandatory (in any case, I never use such links in my own files). The important design feature is that HDF5 attributes define signals and axes, not that the signal and axes may be linked from another group.<span class="Apple-converted-space"> </span><br>
4) For similar reasons, in Section III.A, I rewrote some of the text about default visualization, changing “typically” to “often” concerning links.<br>
5) Also in Section III.A, I rewrote the paragraph on the NXmonitor group. Obviously, some people think that decision was a mistake. I don’t agree - monitor data is almost as important as the other data before data reduction, particularly at pulsed neutron sources
- but, in any case, I don’t think we should be apologizing for our past decisions in a paper designed to promote the format. That’s for our internal discussions.<span class="Apple-converted-space"> </span><br>
<br>
For the same reason, I would argue that we should remove the section on how long NeXus has taken to become established. We’ve made tremendous progress since 2006, so I’m not sure we should be defensive about it. However, I haven’t deleted it in my version because
I didn’t know what to replace it with.<br>
<br>
I haven’t issued a Pull request yet. I thought people might want to check the differences before anyone did a merge.<br>
<br>
</blockquote>
<br>
<br>
Sorry for the late reply. We have discussed your version of the NeXus paper on the last Telco. We have a problem with the rewritten design section:<span class="Apple-converted-space"> </span><br>
it repeats information about the NeXus hierarchy which is discussed at length right in the section below. We feel that we should avoid such repetition in $<br>
a paper which is this short.<br>
<br>
Regards,<br>
<br>
Mark<br>
<br>
<br>
<br>
<br>
<blockquote type="cite">With best regards,<br>
Ray<br>
--<span class="Apple-converted-space"> </span><br>
Ray Osborn, Senior Scientist<br>
Materials Science Division<br>
Argonne National Laboratory<br>
Argonne, IL 60439, USA<br>
Phone: +1 (630) 252-9011<br>
Email:<span class="Apple-converted-space"> </span><a href="mailto:ROsborn@anl.gov">ROsborn@anl.gov</a><br>
<br>
<br>
<br>
_______________________________________________<br>
NeXus-committee mailing list<br>
<a href="mailto:NeXus-committee@nexusformat.org">NeXus-committee@nexusformat.org</a><br>
<a href="http://lists.nexusformat.org/mailman/listinfo/nexus-committee">http://lists.nexusformat.org/mailman/listinfo/nexus-committee</a></blockquote>
</div>
</blockquote>
</div>
<br>
<div apple-content-edited="true">-- <br>
Ray Osborn, Senior Scientist<br>
Materials Science Division<br>
Argonne National Laboratory<br>
Argonne, IL 60439, USA<br>
Phone: +1 (630) 252-9011<br>
Email: <a href="mailto:ROsborn@anl.gov">ROsborn@anl.gov</a><br>
<br>
</div>
<br>
</body>
</html>