[Nexus] Correct way to specify multiple signals

[Benjamin Watts]

Hi Armando,
    Why are the NXplot1d, NXplot2d, NXplot3d, ... groups needed? The 
number of dimensions is clearly findable via the length of the array in 
the "axes" attribute, as well as from the dimensions of the dataset(s). 
Maybe I am missing something?

Cheers,
Ben


On 11/01/18 11:25, V. Armando Solé wrote:
> I think it is clear there is a need and I have opened an issue at github:
>
> https://github.com/nexusformat/NIAC/issues/25
>
> The text follows.
>
> *Typical use cases:*
>
>   * Plotting several counters at scanned positions.
>   * Fitting raw data and willing to generate a plot with the raw data
>     and the fitted data
>   * Elemental mapping where a map is generated for each element
>     ....
>
> The combination of multiple signals with the use of NXprocess would 
> solve many provenance issues.
>
> *Proposed Implementation*
>
> In the past, everything was ready for the implementation via allowing 
> to have multiple datasets with the signal attribute in an NXdata group 
> and by playing with attribute values "1", "2", "3". That approach is 
> not any longer possible.
>
>   * Proposal 1: Allow signal to be an array of string with the first
>     element of the array to be treated as it is now the case with
>     single signals.
>   * Proposal 2: Define a signals attribute being an array of strings
>     with the first element of the array to be treated as it is now the
>     case with single signals.
>   * Proposal 3: Define a new set of groups NXplot1d, NXplot2d,
>     NXplot3d, ... allowing so.
>
>
>
> _______________________________________________
> NeXus mailing list
> NeXus at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nexusformat.org/pipermail/nexus/attachments/20180111/4de1a8bf/attachment-0001.html>