<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="">
<span class="" style="float: none; display: inline !important;">Hi Armando,</span>
<div class="">I have been experimenting with the auxiliary signal idea and seeing whether it really does allow improved functionality, and I am warming to the idea. As long as they all share the same axes, then it does make a combined plot easier to produce.
It has required a little tinkering with NeXpy, but I now have an experimental feature that adds a “Plot All Signals” contextual menu to any NXdata group that has the ‘auxiliary_signals’ attribute, producing a plot with a legend automatically added.</div>
<div class=""><br class="">
</div>
<div class="">I’ll release this in the next couple of days as v0.10.9, after I have confirmed that we have fixed the external link issue that your colleague raised. I think it makes sense to let people experiment with new features before they finally get ratified
by NIAC. It’s easy to tweak things in NeXpy if people suggest improvements.</div>
<div class=""><br class="">
</div>
<div class="">Ray</div>
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Jan 20, 2018, at 10:25 AM, V. Armando Sole <<a href="mailto:sole@esrf.fr" class="">sole@esrf.fr</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi Ray,<br class="">
<br class="">
Thank you for your very positive feedback.<br class="">
<br class="">
I have to admit the use case of common axes probably covers more than 95% of my use case applications.<br class="">
<br class="">
I think now the question to be answered is if the case of not having common axes is ever to be considered of generic interest or not because, unlike the implementation of auxiliary_signals, the implementation of auxiliary_axes would potentially allow signals
with different lengths and that would break code supporting auxiliary_signals and not checking for the presence of auxiliary_axes.<br class="">
<br class="">
At this point there is no code supporting the auxiliary_signals feature and my opinion would be to leave the door open but I will understand (and respect the decision) if this forum votes against it because we are talking about a small number of use cases (basically
at this point I can only think about a) the fit with the fitted curve at higher resolution, b) a picture with partial maps on top of it c) a discontinuous region covered by several raster scans).<br class="">
<br class="">
Best regards,<br class="">
<br class="">
Armando</div>
</div>
</blockquote>
</div>
</div>
<br class="">
-- <br class="">
<div class="">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
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 class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<img apple-inline="yes" id="1EF68879-37F6-4664-8150-BC1F582FD332" src="cid:A8C67EEE-1518-40D7-8B77-ADDF180BE81A@hsd1.il.comcast.net." class=""></div>
</div>
</body>
</html>