[NeXus-committee] NeXus paper v10, NIAC

Pete Jemian prjemian at gmail.com
Fri Sep 5 18:05:26 BST 2014


Attached are my comments on the draft manuscript, in a very raw form. 
Over the weekend, I expect to post them as a pull request.  Only a few 
of these comments will be described below.

[1] The first comment is about validation and refers to Section VI, 
paragraph 3, last sentence.  The .tex file source provides the context 
to my remark here:
A tool exists to perform such validation.%
% TODO: can we please add some kind of reference to where the validation 
tool can be found?
% JAVA source code is here:
% https://github.com/nexusformat/code/tree/master/applications/NXvalidate
% is there a JAR file available?

[2] In the abstract, might we consider using "measurements" where the 
word "experiments" is marked?

[3] In section 1, the paragraph starting with "The first necessity"
Since we only state one necessity, this should be reworded.

[4] Section titles that start with "NeXus".  As Joachim stated, this is 
redundant as the entire manuscript is about NeXus.

[5] In Section II, paragraph 3, the remarks about NXcollection are out 
of place.  Move them as noted.  Instead, finish the thought just started 
and discuss how to extended the files with additional /content/.

[6] In section III, strike my comment.

[7] Section III.A, paragraph 1 gives one of many /possible/ data file 
structures.  With the exception of the second NXentry group, this looks 
like a great starting point for instruments to use.

[8] Section III.A.2, last paragraph, last sentence.  Must we present 
this pathology?  It's a problem that any data file format must have. 
Does it fit with the previous sentence?

[9] Section IV, paragraph 1, sentence 1: data reduction and analysis are 
separate steps for many techniques.  Coordinates of beam line components 
is only of interest to reduction.

[10] Comment at bottom of page 4: my musing, probably won't be added to 
my proposed changes.

[11] Section V, paragraph 2. Emphasize this text:
/All allowed fields are optional./
Is it worth noting that there is one required field, on this class path:
/NXentry/NXdata/{data}/@signal=1

[12] Move section VIII before section VII


Regards,
    Pete


> On 28/08/14 16:03, Mark Könnecke wrote:
>> Hi,
>>
>> the feedback on the NeXus paper has died down somewhat.  I need all coauthors consent in order
>> to submit the paper. In order to move this forward, I suggest the following procedure:
>>
>> * Attached you find a new draft.
>> * You have two weeks to comment. After that period, I assume consent and proceed to submit the paper.
>> * Significant changes to meaning and content of the paper will give rise to a new version. Which in turn
>>    will restart the two week comment period. I do not want to restart for minor spelling or wording changes.
>>
>> Please have another look and let us move this on. If you do not consent to the way I handle this, please
>> voice your concern.
>>
>> The copyright for the paper will be with RSI. They publish under a creative commons attribution license 3.0,
>> see:http://creativecommons.org/licenses/by/3.0/   . If someone is unhappy about this, let us know.
>>
>> ==================================================================
>>
>> If you intend to join NIAC, please start the registration process with APS NOW!
>> Especially for non US citizens it takes several weeks to process. If you are unsure, rather
>> start the registration now and cancel afterwards.
>> ====================================================================
>>
>>
>> Best Regards,
>>
>>      Mark Koennecke
>>
>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 140905114021_0001.pdf
Type: application/pdf
Size: 6127482 bytes
Desc: not available
URL: <http://lists.nexusformat.org/pipermail/nexus-committee/attachments/20140905/2703aff7/attachment.pdf>


More information about the NeXus-committee mailing list