-
Notifications
You must be signed in to change notification settings - Fork 56
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
Create structure to incorporate PDB definitions into NeXus #553
Comments
Herbert will discuss at the ACA meeting 26th May. If there could be some idea of how we want to implement that, that would be good. |
@yayahjb : bump |
I had a look at this. Looks good for the time being. But I would like to see an example where a more completed PDB file has been mapped. Then I have a suggestion: Currently the NXpdb class s used for the main entry and for all groups underneath it. I suggest to name the top level NXpdb_container in order to mark it more clearly as a the root of a hierarchy following NeXus PDB conventions. |
We are waiting for the conversion tool that codifies the PDB <-> NeXus translation for this to be merged/closed. (#614) |
As per NIAC 2018, have added example files, in nexusformat/exampledata/nxpdb, produced using the conversion tool in CBFlib. Will extract the conversion tool, package it and put it in nexusformat by next week. |
2020 Code Camp decide to close this issue as resolved by PR #614. |
As per March 2017 HDRMX meeting in Lund, create a structure to incorporate PDB definitions into NeXus, possibly as a new NXpdb base class.
The text was updated successfully, but these errors were encountered: