[Nexus] Correct way to specify multiple signals

[V. Armando Sole]

Hi Ray,

Thank you for your very positive feedback.

I have to admit the use case of common axes probably covers more than 
95% of my use case applications.

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.

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).

Best regards,

Armando

On 20.01.2018 14:23, Osborn, Raymond wrote:
> Hi Armando,
> I had no problem opening the file with the nexusformat API. It’s
> already been very helpful in focusing my thinking on the subject. If
> we restrict the auxiliary signals to having a common axis, then I
> think something like this could be workable.
> 
> It turns out that overplotting multiple signals was a bit more
> cumbersome than I would have liked in NeXpy, so at the very least, I
> will be modifying my code to make it easier with this kind of data.
> 
> Have a good weekend,
> Ray
> 
>> On Jan 20, 2018, at 6:58 AM, V. Armando Sole <sole at esrf.fr> wrote:
>> 
>> If you have troubles with previous file, you can try this one:
>> 
>> https://cloud.esrf.fr/index.php/s/B1Sq04iJCCWyp1I
>> 
>> As I said, it is a work in progress (I find some differences between
>> Python2 and Python3 when generating the file)
>> 
>> Armando
>> 
>> On 20.01.2018 13:31, V. Armando Sole wrote:
>> 
>>> Dear colleagues,
>>> It has been a difficult week and I am still working on it, but you
>>> can
>>> download a tentative example (still needs improvements) for one of
>>> the
>>> acquisition use cases I foresee (the link will expire at the end
>>> of
>>> the month):
>>> https://cloud.esrf.fr/index.php/s/N4zbr1dzCDDKbWg
>>> As I said, one of our objectives is that the end user can recover
>>> as
>>> default plot the plot shown during the acquisition. For those
>>> using
>>> SPEC, the idea is to be able to map the plotselect to the NeXus
>>> file.
>>> Those scans correspond to energy scans with a multielement
>>> detector
>>> and the goal is to visualize the contents of all the Ni Ka ROIs
>>> corresponding to what the user was interested on during the
>>> experiment.
>>> The intention is to have the signal in the NXdata group
>>> corresponding
>>> to the central element and the auxiliary_signals to the rest of
>>> elements.
>>> As I said, it is still a work in progress but I hope you get the
>>> idea.
>>> Hopefully next week I can provide example and viewer.
>>> See you,
>>> Armando
>>> _______________________________________________
>>> NeXus mailing list
>>> NeXus at nexusformat.org
>>> http://lists.nexusformat.org/mailman/listinfo/nexus
>> _______________________________________________
>> NeXus mailing list
>> NeXus at nexusformat.org
>> http://lists.nexusformat.org/mailman/listinfo/nexus
> 
>  --
> Ray Osborn, Senior Scientist
> Materials Science Division
> Argonne National Laboratory
> Argonne, IL 60439, USA
> Phone: +1 (630) 252-9011
> Email: ROsborn at anl.gov
> _______________________________________________
> NeXus mailing list
> NeXus at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus