-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend cnxvalidate to validate any NeXus file #13
Comments
…ition. As implemented now, validation happens against a minimal application definition containing just an NXentry. Refs #13
I added support for validating NeXus files without an application definition to cnxvalidate. |
Still to do:
|
It may be that MXML may be able to pull in default attributes for definitions from the mxdl.xsd |
With the ignored* attribute it may still make sense to report this as an informational message. |
There are two ways to implement this:
There is probably little value in this: we can only find names which are not allowed. |
Currently cnxvalidate balks if there is no application definition. There is a desire to continue validating against the base classes then, with a hard coded empty application definition. Thus cnxvalidates scope is extended to a general NeXus file validation tool. There may be changes required to the recursion to support that.
The text was updated successfully, but these errors were encountered: