<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">A while back, Anders Glans, Dylan McReynolds and I proposed the NXmultixas to address this (as a gentler path compared to updating the existing NXxas). There is a draft definition online although it might be in a private repository. I have not contributed to it since last year when I changed jobs.<div><br></div><div>-Padraic<br><div><br></div><div><div><br></div><div><div style="display: block;"><div style="-webkit-user-select: all; -webkit-user-drag: element; display: inline-block;" class="apple-rich-link" draggable="true" role="link" data-url="https://github.com/nexusformat/definitions/issues/1011"><a style="border-radius:10px;font-family:-apple-system, Helvetica, Arial, sans-serif;display:block;-webkit-user-select:none;width:300px;user-select:none;-webkit-user-modify:read-only;user-modify:read-only;overflow:hidden;text-decoration:none;" class="lp-rich-link" rel="nofollow" href="https://github.com/nexusformat/definitions/issues/1011" dir="ltr" role="button" draggable="false" width="300"><table style="table-layout:fixed;border-collapse:collapse;width:300px;background-color:#E5E6E9;font-family:-apple-system, Helvetica, Arial, sans-serif;" class="lp-rich-link-emailBaseTable" cellpadding="0" cellspacing="0" border="0" width="300"><tbody><tr><td vertical-align="center" align="center"><img style="width:300px;filter:brightness(0.97);height:150px;" width="300" height="150" draggable="false" class="lp-rich-link-mediaImage" alt="1011.png" src="cid:49DDA42F-B1EB-4094-9F04-6D3D4634A99F"></td></tr><tr><td vertical-align="center"><table bgcolor="#E5E6E9" cellpadding="0" cellspacing="0" width="300" style="font-family:-apple-system, Helvetica, Arial, sans-serif;table-layout:fixed;background-color:rgba(229, 230, 233, 1);" class="lp-rich-link-captionBar"><tbody><tr><td style="padding:8px 0px 8px 0px;" class="lp-rich-link-captionBar-textStackItem"><div style="max-width:100%;margin:0px 16px 0px 16px;overflow:hidden;" class="lp-rich-link-captionBar-textStack"><div style="word-wrap:break-word;font-weight:500;font-size:12px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-topCaption-leading"><a rel="nofollow" href="https://github.com/nexusformat/definitions/issues/1011" style="text-decoration: none" draggable="false"><font color="#272727" style="color: rgba(0, 0, 0, 0.847059);">Add multi-detector support for NXxas · Issue #1011 · nexusformat/definitions</font></a></div><div style="word-wrap:break-word;font-weight:400;font-size:11px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-bottomCaption-leading"><a rel="nofollow" href="https://github.com/nexusformat/definitions/issues/1011" style="text-decoration: none" draggable="false"><font color="#808080" style="color: rgba(0, 0, 0, 0.498039);">github.com</font></a></div></div></td></tr></tbody></table></td></tr></tbody></table></a></div></div><br><div><br><blockquote type="cite"><div>On Mar 13, 2024, at 5:05 AM, Smith, William via NeXus <nexus@shadow.nd.rl.ac.uk> wrote:</div><br class="Apple-interchange-newline"><div><div>Dear NeXus community,<br><br>I would like to know how other people are approaching the following situation.<br><br>In an XAS measurement there are a minimum of two detectors. In the application definition these are named "incoming_beam" and "absorbed_beam".<br><br>In practice is it not uncommon to have many detectors measuring the absorbed beam. For example TEY (Total Electron Yield), TFY (Total Florescence Yield), and then N PFY (partial florescence yield) signals.<br><br>In the XAS application definition (and other similar app defs) there is only a single absorbed_beam entry under NXinstrument. https://manual.nexusformat.org/classes/applications/NXxas.html<br><br>Under the entry for DATA:NXdata is a field "mode" specifying which mode of detection is being used (TEY, TFY, PFY, Transmission etc)<br><br>I could make multiple NXentry in one file, which were each almost identical except with different entries for the NXdata which would connect to TFY or PFY or TEY signal etc,<br><br>Or<br><br>I could us NXsubentry to do the same<br><br>Or<br><br>I could use multiple NXdetector groups named something like absorbed_beam_TEY, absorbed_beam_TFY (this is my preference but doesn't comply with the application definition)<br><br>Thanks in advance for your help,<br><br>Will<br><br><br>_______________________________________________<br>NeXus mailing list<br>NeXus@nexusformat.org<br>https://lists.nexusformat.org/mailman/listinfo/nexus<br></div></div></blockquote></div><br></div></div></div></body></html>