Why does nxvalidate report errors for NXazint1d and NXazint2d example files generated by nxdl_to_hdf5.py?

[meghdadyazdi]

Hi

To test the application definitionsNXazint1d and NXazint2d, I ran nxdl_to_hdf5.py to produce the corresponding example files nx_azint1d.h5 and nx_azint2d.h5

Both files contain:

/entry annotated as NX_class="NXentry"

/entry/data annotated as NX_class="NXdata"

However, when I run nxvalidate for nx_azint1d.h5 and nx_azint1d.h5, I always receive the following messages:

...

definition=NXazint2d.nxdl.xml message="Required group missing"
... nxdlPath=/NXentry/NXdata
... sev=error dataPath=/entry dataFile=nx_azint2d.h5

definition=NXazint2d.nxdl.xml message="Additional base class group data of type NXdata found"
... nxdlPath=/NXentry
... sev=warnbase dataPath=/entry/data dataFile=nx_azint2d.h5

I see the same validation errors with output files produced by our azint_writer, which follows the NXazint1d and NXazint2d structure.

I’m trying to understand whether the validator is interpreting the NXazint1d and NXazint2d layout differently than the files produced by nxdl_to_hdf5.py or I am doing something wrong?

Any suggestions would be appreciated.

Thanks.

[rayosborn]

I was not involved in developing cnxvalidate, but there is a Python alternative, available if you install the nexusformat API.] with a GUI interface in NeXpy since v2.0.0.

$ pip install nexusformat
$ nxcheck -a NXazint2d NXazint2d.hdf5 


Filename: NXazint2d.hdf5
Path: /entry
Definitions: nexusformat/definitions
Application Definition: NXazint2d
NXDL File: ...ormat/definitions/contributed_definitions/NXazint2d.nxdl.xml


Group: NXdata
    Field: /entry/data/I
        Using "signal" as a field attribute is no longer valid. Use the group attribute "signal"

Total number of warnings: 1
Total number of errors: 0

This does not appear to throw any errors, although using the signal attribute on a field is now deprecated.

Note that the current version of nexusformat on PyPI also issues warnings about array dimensions. However, the latest development version is issuing those messages as "informational" because I believe that dimension warnings are currently unreliable.

[meghdadyazdi]

Thanks for the suggestion that’s very helpful. I tried nxcheck and indeed it validates the file against NXazint1d and NXazint2d without errors.