[Nexus] Correct way to specify multiple signals
V. Armando Solé
sole at esrf.fr
Thu Jan 11 14:40:17 GMT 2018
On 11/01/2018 15:36, Osborn, Raymond wrote:
> I saw the Github issue and responded before I realized there was
> already a lengthy correspondence here. I will have to read more
> carefully what has already been contributed here, but I wanted to
> quickly summarize what I wrote there
> “In my view, it is the role of the NeXus standard to provide a way to
> offer a default plot for each NXdata group, but I don't think it is
> necessary for NeXus to then specify all other possible non-default
> plots. Any program is free to provide that option within the current
> standard as NeXpy does.”
> Please see the issue for my reasoning - basically, you can do what
> Armando requests, i.e., plot multiple signals, now without adding
> extra complexity to the standard.
The goal is not to foresee any possible plot. It is to provide a default
plot. I post the answer I sent to github here too:
On 11/01/2018 15:04, Ray Osborn wrote:
> To summarize - in my view, it is the role of the NeXus standard to
> provide a way to offer a default plot for each NXdata group,
Exact, but to me the default plot for a fit is the raw_data, the used
uncertainties and the fitted curve.
NeXus provides everything for it except the possibility to put the
> but I don't think it is necessary for NeXus to then specify all other
> possible non-default plots.
Nobody is asking for it.
> Any program is free to provide that option within the current standard
> as NeXpy does.
PyMca does it too, so that is not the problem. However, consider the
marvellous opportunity NeXus offers to provide the output of a fit (or
other treatments), with uncertainties, axis labels, and fitted curve at
the cost of defining two group attributes.
If NIAC tells me that Peter Chang's solution is not going to be
considered at all, it is fine with me too. We'll implement those two
attributes at our side and they will not conflict with any other
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NeXus