<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Pete<br>
<br>
<div class="moz-cite-prefix">On 05/11/16 13:33, Pete Jemian wrote:<br>
</div>
<blockquote
cite="mid:CA+JrzyM7Mc=p=uQ+OEExC2ef8E4brZe7KCwVjkb4uQgq5R67ZA@mail.gmail.com"
type="cite">
<pre wrap="">The source is definitely a part of the instrument, not something at the top
level of the experiment (NXentry). Consider the case of a synchrotron X-ray
experiment with a laser pump. There are two sources to be documented.
They both belong under the description of the pump/probe instrument.
Why should the beam be part of the sample? Makes no sense at all. The
sample has no beam. The beam does not describe the sample in any useful
way. NXbeam documents the state of the beam at some position along the
path from source to detector. It could go in many places along the optical
path.</pre>
</blockquote>
Besides the fact that NXbeam is mentioned as a possible child for
NXsample<br>
it makes perfect sense there too. <br>
If you have many optical components in your beam path and one is
mainly interested in the <br>
beam paramters in front of the sample NXbeam within NXsample would
be my <br>
first approach to document these parameters.<br>
<br>
regards<br>
Eugen<br>
<br>
<br>
<blockquote
cite="mid:CA+JrzyM7Mc=p=uQ+OEExC2ef8E4brZe7KCwVjkb4uQgq5R67ZA@mail.gmail.com"
type="cite">
<pre wrap="">
Pete
On May 11, 2016 6:17 AM, "Andreas Förster" <a class="moz-txt-link-rfc2396E" href="mailto:andreas.foerster@dectris.com"><andreas.foerster@dectris.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear NeXus folks,
there was a little discussion last week about possible additions to the
NeXus standard (and NXmx) to record beam information relevant for the
estimation of dose. Herbert proposed a good solution, but the outcome of
this discussion is still pending.
At DECTRIS, we're keen to tell our customers how to record additional
metadata in a NeXus-compliant way. That's why I'd like to have official
word on the fields below:
Information on the synchrotron should be recorded in an NX_Source group.
Is /entry/source the right place for that?
/entry/source *NX_SOURCE*
<a class="moz-txt-link-rfc2396E" href="http://download.nexusformat.org/sphinx/classes/base_classes/NXsource.html"><http://download.nexusformat.org/sphinx/classes/base_classes/NXsource.html></a>
o *name*: *NX_CHAR*
<a class="moz-txt-link-rfc2396E" href="http://download.nexusformat.org/sphinx/nxdl-types.html#nx-char"><http://download.nexusformat.org/sphinx/nxdl-types.html#nx-char></a>
§ Name of synchrotron
o *@short_name*: *NX_CHAR*
<a class="moz-txt-link-rfc2396E" href="http://download.nexusformat.org/sphinx/nxdl-types.html#nx-char"><http://download.nexusformat.org/sphinx/nxdl-types.html#nx-char></a>
§ short name for source, perhaps the acronym
Data describing the beam as it hits the sample should probably go the
NX_Beam group in /entry/sample/beam. None of the fields below are
currently defined. Could these definitions be adopted?
ˇ /entry/sample/beam *NX_BEAM*
<a class="moz-txt-link-rfc2396E" href="http://download.nexusformat.org/sphinx/classes/base_classes/NXbeam.html"><http://download.nexusformat.org/sphinx/classes/base_classes/NXbeam.html></a>
o *name*: *NX_CHAR*
<a class="moz-txt-link-rfc2396E" href="http://download.nexusformat.org/sphinx/nxdl-types.html#nx-char"><http://download.nexusformat.org/sphinx/nxdl-types.html#nx-char></a>
§ Name of beamline
o *total_flux/xray_flux*: *NX_FLOAT*
<a class="moz-txt-link-rfc2396E" href="http://download.nexusformat.org/sphinx/nxdl-types.html#nx-float"><http://download.nexusformat.org/sphinx/nxdl-types.html#nx-float></a> {units=
*NX_RATE* <a class="moz-txt-link-rfc2396E" href="http://download.nexusformat.org/sphinx/nxdl-types.html#nx-rate"><http://download.nexusformat.org/sphinx/nxdl-types.html#nx-rate></a>
}
§ Beam intensity (example: s-1)
o *incident_beam_size: **NX_FLOAT*
<a class="moz-txt-link-rfc2396E" href="http://download.nexusformat.org/sphinx/nxdl-types.html#nx-float"><http://download.nexusformat.org/sphinx/nxdl-types.html#nx-float></a>*[2]*
§ Two-dimensional array of FWHM (if Gaussian) or diameters (if top hat)
of beam
o *profile*: *NX_CHAR*
<a class="moz-txt-link-rfc2396E" href="http://download.nexusformat.org/sphinx/nxdl-types.html#nx-char"><http://download.nexusformat.org/sphinx/nxdl-types.html#nx-char></a>
§ Gaussian or top hat
Should the name of the beamline be recorded in beam or in source? For the
flux (as a rate - in contrast to the already existing flux density field
"flux"), either name is fine by me.
I'm happy to discuss these points during the next NeXus meeting.
Thank you and all best
Andreas
--
<a class="moz-txt-link-rfc2396E" href="https://www.dectris.com"><https://www.dectris.com></a>
Andreas Förster, Ph.D.
MX Application Scientist, Scientific Sales
Phone: +41 56 500 2100 | Direct: +41 56 500 2176 | Email:
<a class="moz-txt-link-abbreviated" href="mailto:andreas.foerster@dectris.com">andreas.foerster@dectris.com</a>
DECTRIS Ltd. | Taefernweg 1 | 5405 Baden-Daettwil | Switzerland |
<a class="moz-txt-link-abbreviated" href="http://www.dectris.com">www.dectris.com</a>
[image: LinkedIn] <a class="moz-txt-link-rfc2396E" href="https://www.linkedin.com/company/5067919"><https://www.linkedin.com/company/5067919></a>
[image: facebook]
<a class="moz-txt-link-rfc2396E" href="https://www.facebook.com/pages/Dectris-Ltd/623855944369304"><https://www.facebook.com/pages/Dectris-Ltd/623855944369304></a>
<a class="moz-txt-link-rfc2396E" href="https://twitter.com/DECTRIS_News"><https://twitter.com/DECTRIS_News></a>
Confidentiality Note: This message is intended only for the use of the
named
recipient(s) and may contain confidential and/or privileged information. If
you
are not the intended recipient, please contact the sender and delete the
message.
Any unauthorized use of the information contained in this message is
prohibited.
_______________________________________________
NeXus-committee mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NeXus-committee@nexusformat.org">NeXus-committee@nexusformat.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nexusformat.org/mailman/listinfo/nexus-committee">http://lists.nexusformat.org/mailman/listinfo/nexus-committee</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
NeXus-committee mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NeXus-committee@nexusformat.org">NeXus-committee@nexusformat.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nexusformat.org/mailman/listinfo/nexus-committee">http://lists.nexusformat.org/mailman/listinfo/nexus-committee</a>
</pre>
</blockquote>
<br>
</body>
</html>