nxdl_to_hdf5.py generates NXazint1d and NXazint2d examples that fail nxvalidate

[meghdadyazdi]

Dear @woutdenolf, @PeterC-DLS

Using the nxdl_to_hdf5.py, I generated the example files nx_azint1d.h5 and nx_azint2d.h5 from the application definitions NXazint1d and NXazint2d.

Both files contain:

/entry annotated as NX_class="NXentry"

/entry/data annotated as NX_class="NXdata"

However, when validating nx_azint1d.h5 and nx_azint1d.h5 with nxvalidate, I consistently get:

...

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

The same validation errors appear for 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 hints on what I might be missing would help.

Thanks.

[PeterC-DLS]

Maybe it's an issue with nxvalidate as the NXazint1d definition specifies at least one NXdata (of arbitrary name) in NXentry and that NXdata in the generated file is correctly referenced by @default attributes.