[Nexus] Correct way to specify multiple signals

Osborn, Raymond rosborn at anl.gov
Thu Jan 11 16:45:26 GMT 2018

Just a quick comment on this. The single colon-delimited string used to be the only way to define a list of axes, partly because attribute arrays were not available in HDF4. It is now deprecated in favor of an array of strings; I don’t think the standard specifies using variable-length strings or fixed-length string arrays. NeXpy needs to be able to read much older NeXus files, so it will read both, but only writes attribute arrays.

This is an example of the kind of cruft that any reasonably long-lived standard accumulates.


On Jan 11, 2018, at 3:22 AM, V. Armando Solé <sole at esrf.fr<mailto:sole at esrf.fr>> wrote:

An additional question.

The axes attribute, is it a single string with dataset names separated
by colons  (",") or is it an array of strings? I had always understood
the former but my colleagues understand the later. I would appreciate
clarification there too because in the documentation pages I do not see
the typical [n] used to specify one is dealing with arrays and because
of that (and because for some computing languages variable length string
arrays are a problem) I was expecting a single string.



Ray Osborn, Senior Scientist
Materials Science Division
Argonne National Laboratory
Argonne, IL 60439, USA
Phone: +1 (630) 252-9011
Email: ROsborn at anl.gov<mailto:ROsborn at anl.gov>

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

More information about the NeXus mailing list