[Nexus] Correct way to specify multiple signals
V. Armando Solé
sole at esrf.fr
Thu Jan 11 09:28:01 GMT 2018
On 11/01/2018 10:24, Tobias Richter wrote:
> Hi Armando,
> First of all: With the new scheme where the attributes belong to the NXdata group there are no “,” separated lists. That scheme uses attribute arrays (for axes). I’ve just made that yet a bit clearer in the NXdata base class documentation. Hope that helps.
Thanks. That has already answered a second question I have just asked :-)
> Otherwise there is currently no provision for plotting multiple things out of a single NXdata. If the axes of multiple NXdata groups coincide, an application would be free to plot them into the same coordinate system.
> For signals with 2 or more dimensions it is not obvious what should be done. Keeping the generic case simple and clean makes sense to me.
Well, for 2 or more dimensions the simplest way is to use a "signal"
browser but any application could implement whatever approach convenient
for the application (for instance playing with transparency could be
My colleagues suggest that for compatibility issues perhaps to define a
new NXdata group attribute signals (instead of signal) would avoid any
confusion at programs expecting to find signal as a string and not as an
array of strings.
More information about the NeXus