<div dir="ltr">Dear Andreas,<br><div><br>We call it the "NeXus NXmx application definition". The intention is to support a wide range of NeXus files for MX. You are welcome to use that label for files that comply. If you find that too narrow, I would suggest "NeXus NXmx application definition with Dectris Eiger extensions". We'll be happy to work with you to clarify things. I would suggest participating in the NeXus telco's that will be coming up as we talk through any further clarifications and adjustments in making NXmx 1.5 and NXtransformations 1.1 final.<br><br></div><div>Regards,<br></div><div> Herbert<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 18, 2016 at 4:20 PM, Andreas Förster <span dir="ltr"><<a href="mailto:andreas.foerster@dectris.com" target="_blank">andreas.foerster@dectris.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Dear Herbert,<div><br></div><div>thank you for simplifying the description of the sample transformation axes. We'll modify the EIGER firmware accordingly in due time.</div><div><br></div><div>Is my understanding correct that the description is sufficiently general and broad as to cover data coming from a variety of detectors? In that case, could this format, even informally, not to be referred to as EIGER format? The impression that we're imposing something on the community is not only wrong but also counterproductive.</div><div><br></div><div>Thank you and all best.</div><div><br></div><div><br></div><div>Andreas</div><div><br></div><div><br></div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Fri, Oct 14, 2016 at 3:17 PM, Herbert J. Bernstein <span dir="ltr"><<a href="mailto:yayahjb@gmail.com" target="_blank">yayahjb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>I have now added a revised NXtransformations 1.1 proposal in the NXmx_multimodule_and_dectris_c<wbr>hanges branch and have posted it to the <a href="http://hdrmx.medsbio.org" target="_blank">hdrmx.medsbio.org</a>. The major changes are:<br><br></div> 1. The formerly proposed AXISNAME_range has been removed from the proposal as duplicative of AXISNAME_end, and the proposed AXISNAME_average_range has been changed to AXISNAME_increment_set to conform better to NeXus conventions. <br><br></div> 2. The proposed transformation type 'general' has been replaced by simply not providing a transformation_type omitting that attribute.<br><br></div>The new proposals for both NXmx and NXtransformations can be seen at:<br><br><a href="http://hdrmx.medsbio.org/NIAC_2016/manual2/build/html/classes/applications/NXmx.html?highlight=nxmx" target="_blank">http://hdrmx.medsbio.org/NIAC_<wbr>2016/manual2/build/html/classe<wbr>s/applications/NXmx.html?<wbr>highlight=nxmx</a><br><br></div>and<br><br><a href="http://hdrmx.medsbio.org/NIAC_2016/manual3/build/html/classes/base_classes/NXtransformations.html?highlight=nxtransformations" target="_blank">http://hdrmx.medsbio.org/NIAC_<wbr>2016/manual3/build/html/classe<wbr>s/base_classes/NXtransformatio<wbr>ns.html?highlight=<wbr>nxtransformations</a><span class="m_3367964034139628410HOEnZb"><font color="#888888"><br> <br><div> -- HJB<br></div><div><br></div></font></span></div><div class="m_3367964034139628410HOEnZb"><div class="m_3367964034139628410h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 14, 2016 at 10:34 AM, Herbert J. Bernstein <span dir="ltr"><<a href="mailto:yayahjb@gmail.com" target="_blank">yayahjb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>After discussion at NIAC, I have revised the NXmx 1.5 proposal in the NXmx_multimodule_and_dectris_c<wbr>hanges branch and on the <a href="http://hdrmx.medsbio.org" target="_blank">hdrmx.medsbio.org</a> web site. The main change was to add an enumeration of the beam profile choices to include a rectangular option.<br><br></div>We also have some changes to the NXtransformations 1.1 proposal. That is still to be drafted in detail.<br></div><div class="m_3367964034139628410m_-3628207942521431348HOEnZb"><div class="m_3367964034139628410m_-3628207942521431348h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 5, 2016 at 9:42 PM, Herbert J. Bernstein <span dir="ltr"><<a href="mailto:yayahjb@gmail.com" target="_blank">yayahjb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="m_3367964034139628410m_-3628207942521431348m_-1399721269681835741m_5533533629043109159gmail-comment-body m_3367964034139628410m_-3628207942521431348m_-1399721269681835741m_5533533629043109159gmail-markdown-body m_3367964034139628410m_-3628207942521431348m_-1399721269681835741m_5533533629043109159gmail-markdown-format m_3367964034139628410m_-3628207942521431348m_-1399721269681835741m_5533533629043109159gmail-js-comment-body">
<p>In preparation for the NIAC meeting:<br></p><p>I have created a branch,
NXmx_multimodule_and_dectris_c<wbr>hanges, with a draft of the proposed
changes to NXmx and NXtransformations. You can see the nxdl files in
that branch on github. You can see the definitions at:</p>
<p><a href="http://hdrmx.medsbio.org/NIAC_2016/manual/build/html/classes/applications/NXmx.html?highlight=nxmx" target="_blank">http://hdrmx.medsbio.org/NIAC_<wbr>2016/manual/build/html/classes<wbr>/applications/NXmx.html?highli<wbr>ght=nxmx</a></p>
<p>and</p>
<p><a href="http://hdrmx.medsbio.org/NIAC_2016/manual/build/html/classes/base_classes/NXtransformations.html?highlight=nxtransformations" target="_blank">http://hdrmx.medsbio.org/NIAC_<wbr>2016/manual/build/html/classes<wbr>/base_classes/NXtransformation<wbr>s.html?highlight=nxtransformat<wbr>ions</a></p>
<p>and the blank-suppressed differences at</p>
<p><a href="http://hdrmx.medsbio.org/NIAC_2016/NXmx.diff" target="_blank">http://hdrmx.medsbio.org/NIAC_<wbr>2016/NXmx.diff</a></p>
<p>and</p>
<p><a href="http://hdrmx.medsbio.org/NIAC_2016/NXtransformations.diff" target="_blank">http://hdrmx.medsbio.org/NIAC_<wbr>2016/NXtransformations.diff</a></p>
<p>The rationale for the proposed changes is as follows:</p>
<ol><li> NXmx changes
<br>1.1. Version number updated from 1.4 to 1.5 -- to help software
packages in distinguishing files made to conform to the changed version.
<br>1.2. Add documentation of the possibility of a third image dimension.
This case arises for the CSPAD and helps to organize data arrays to
correspond to the module structure of multi-module detectors. The main
change was to add a variable dataRank to carry a rank of either 2 or 3
and to add an optional index k after i and j.
<br>1.3. Add explicit, but optional use of the NXdetector_group base class
for the case of a detector in which each module has its own data array,
rather than the case being considered in 1.2, above. In this case the
relationship among multiple the relationships among multiple NXdetector
groups needs to be stated. This was, of course, already an implicit
option under NXmx 1.4, but now we are making the possibility explicit,
with documentation that comes closer to the descriptions used with CBF
for the same situation. Note that CBF calls a NXdetector_group a
detector and an NXdetector a detector element, and deal an
NXdetector_module using and array_structure_list_section.
<br>1.4. Add additional documentation in the NXmx use of NXdetector_module
and add an optional data_stride field in the NXmx use of
NXdetector_module for completeness.
<br>1.5. Add optional new total_flux, incident_beam_size, and profile in
the NXmx use of NXbeam. These are needed to provide a place to put
information crystallographers record</li><li> NXtransformations changes <br>2.1. Version number updated from 1.0 to 1.1 -- to help software
packages in distinguishing files made to conform to the changed version.
<br>2.2. To help people understand the distinctions among axis types and
what information they need to provide, add an explicit general axis
type, for such things as the direction of gravity or other special
reference coordinate axes they need to track but probably don't move,
change from the upercase pseudovariable TRANSFORMATION to AXISNAME
(making it consistent with NXDATA) and make an new upper case
pseudovariable AXISUNITS to help explain the units they need to provide
for rotation and translation axes.
<br>2.3. Add new AXISNAME_end, AXISNAME_range and AXISNAME_average_range
fields to hold information on the scan steps taken in crystallographic
experiments. These are also needed to provide a place to put
information crystallographers record.</li></ol>
</div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div>-- <br><div class="m_3367964034139628410gmail_signature" data-smartmail="gmail_signature"><a href="https://www.dectris.com" target="_blank"></a><div><span style="font-family:Verdana;font-size:large">Andreas Förster, Ph.D.</span></div><div><font size="1" face="Verdana"><span style="color:rgb(128,128,128)">MX Application Scientist, Scientific Sales</span></font></div><div><span style="white-space:pre-wrap"> </span></div><div><font size="1" color="#808080"><font face="Verdana">Phone: </font></font><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small"><a href="tel:%2B41%2056%20500%202100" value="+41565002100" target="_blank">+41 56 500 2100</a></span><font size="1" color="#808080"><font face="Verdana"> </font><span style="font-family:Arial,Helvetica,sans-serif;line-height:14px">|</span><span style="font-family:Verdana"> Direct</span><span style="font-family:Verdana">:</span><span style="font-family:Verdana"> </span></font><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small"><a href="tel:%2B41%2056%20500%202176" value="+41565002176" target="_blank">+41 56 500 2176</a></span><font size="1" color="#808080"><span style="font-family:Verdana"> </span><span style="font-family:Arial,Helvetica,sans-serif;line-height:14px">|</span><span style="font-family:Verdana"> </span><font style="font-family:Verdana">Email:</font><span style="font-family:Verdana"> <a href="mailto:andreas.foerster@dectris.com" target="_blank">andreas.<wbr>foerster@dectris.com</a></span></font></div><div><span style="font-size:x-small;color:rgb(128,128,128);font-family:Verdana">DECTRIS Ltd. </span><span style="font-size:x-small;color:rgb(128,128,128);font-family:Verdana;line-height:14px">|</span><span style="font-size:x-small;color:rgb(128,128,128);font-family:Verdana;line-height:14px"> Taefernweg 1</span><span style="font-size:x-small;color:rgb(128,128,128);font-family:Verdana;line-height:14px"> </span><span style="font-size:x-small;color:rgb(128,128,128);font-family:Verdana;line-height:14px">| 5405 Baden-Daettwil</span><span style="font-size:x-small;color:rgb(128,128,128);font-family:Verdana;line-height:14px"> </span><font style="font-size:x-small;color:rgb(128,128,128);font-family:Verdana;line-height:14px">| Switz</font><font size="1"><font face="Verdana"><font style="color:rgb(128,128,128);line-height:14px">erland</font><span style="color:rgb(128,128,128);line-height:14px"> </span><font style="color:rgb(128,128,128);line-height:14px">|<wbr> </font></font><a href="https://www.dectris.com" target="_blank"><font face="Verdana">www.dectris.com</font></a></font></div><div><font size="1"><font style="color:rgb(128,128,128);font-family:Verdana;line-height:14px"><br></font></font></div><div><div><a href="https://www.linkedin.com/company/5067919" target="_blank"><img src="https://www.dectris.com/tl_files/root/signatur/linkein-ico1.png" alt="LinkedIn" style="width:15px;height:15px;margin-left:400px;float:left"></a></div></div><div> <a href="https://www.facebook.com/pages/Dectris-Ltd/623855944369304" target="_blank"><img src="https://www.dectris.com/tl_files/root/signatur/facebook-ico1.png" alt="facebook" style="width:15px;height:15px"></a> <a href="https://twitter.com/DECTRIS_News" target="_blank"><img src="https://www.dectris.com/tl_files/root/signatur/twitter-ico1.png" style="width:15px;height:15px"></a></div><div><br></div><div><br></div><div><img src="https://www.dectris.com/tl_files/root/signatur/dectris_plus%20slogan.png" style="float:left;height:30px;width:262px;margin-left:195px"></div><div><font size="1" color="#808080" face="Verdana"><br></font></div><div><font size="1" color="#808080" face="Verdana"><br></font></div><div><font size="1" color="#808080" face="Verdana"><br></font></div><div><font size="1" color="#808080" face="Verdana">Confidentiality Note: This message is intended only for the use of the named </font></div><div><font size="1" color="#808080" face="Verdana">recipient(s) </font><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small">and may contain confidential and/or privileged information. </span><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small">If you </span></div><div><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small">are not the intended </span><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small">recipient, please contact the sender and delete </span><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small">the message.</span></div><div><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small">Any unauthorized use of </span><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small">the information contained in this </span><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small">message is prohibited.</span></div><div><span style="color:rgb(128,128,128);font-family:Verdana;font-size:x-small"><br></span></div><div><font size="1" color="#808080" face="Verdana"><br></font></div></div>
</div>
</blockquote></div><br></div>