<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jan 12, 2018, at 9:46 AM, GOTZ Andrew <<a href="mailto:andy.gotz@esrf.fr" class="">andy.gotz@esrf.fr</a>> wrote:</div>
<div class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">I do not develop applications anymore but I do NOT find your example for the 1D case confusing. I could imagine a generic application providing a plot of [‘detector’ ‘ic0’ ‘ic1’ ‘ic2’ ic3’] against 'Seconds' followed by an option to switch the X
axes to ‘Epoch’, or ’Two_Theta' with a single click.</p>
</div>
</div>
</blockquote>
<div>Hi Andy,</div>
<div>NeXpy already effectively provides this functionality, with greater flexibility than the change would allow, i.e., the user can choose whatever array they like to be the signal and whatever array they choose as axis. It just requires a double-click on
the signal, and then selecting an axis from the pull-down menu. The new proposal would restrict the user to selecting some arrays as signals and others as axes, but I quite often want to plot two signals together to see if they are linearly related, for example.
At the moment, I see every new proposal through the lens of how it would have to be implemented in a generic program like NeXpy. I have already spent many hours finding ways of parsing new NeXus features, and will gladly spend more, but only if I’m convinced
the feature is worth the effort.</div>
<blockquote type="cite" class="">
<div class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">BTW my email this morning was intended for Armando only, it got sent to the mailing list by mistake - sorry if I offended anyone ?-(<span class="" style="color: rgb(51, 51, 51); font-variant-ligatures: normal; font-weight: 700; orphans: 2; text-align: center; white-space: nowrap; widows: 2; background-color: rgb(249, 249, 249); float: none; display: inline !important;"></span>.
But it did express some frustration we feel getting the Nexus standard to integrate new features. </p>
</div>
</div>
</blockquote>
</div>
No offense taken. However, I think you are being a little unfair to say that NeXus is unwilling to integrate new features. This proposal is only a couple of days old, and I have already spent several hours exploring its implications. If it survives this kind
of scrutiny, then it will be a robust addition to the standard that I would warmly welcome. If it doesn’t survive, we will have saved ourselves the problem of documenting another feature that is soon to be deprecated.
<div class=""><br class="">
</div>
<div class="">Ray</div>
<div class="">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
-- <br class="">
Ray Osborn, Senior Scientist<br class="">
Materials Science Division<br class="">
Argonne National Laboratory<br class="">
Argonne, IL 60439, USA<br class="">
Phone: +1 (630) 252-9011<br class="">
Email: <a href="mailto:ROsborn@anl.gov" class="">ROsborn@anl.gov</a></div>
</div>
</div>
<br class="">
</div>
</body>
</html>