-
Notifications
You must be signed in to change notification settings - Fork 9
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
Move around cell 2 #358
Move around cell 2 #358
Conversation
The CELL category parent is now DIFFRN. pressure, temperature items in CELL_MEASUREMENT deprecated in favour of similar items in DIFFRN. Pointers to _diffrn.id added to CELL etc. to allow multiple cells to be presented where multiple diffraction conditions are used. The `CELL_MEASUREMENT` category now has two `_diffrn.id` pointers, one to specify the data collection to which the cell measurement applies, and one to the conditions under which the cell was measured (`.condition_id`). Normally these coincide and the latter is not necessary, but legacy point detector experiments can sometimes involve measuring the cell under differing conditions prior to data collection.
If @vaitkus and other commenters are happy with the current version, I'd like to merge so that we can proceed with a proper release of core CIF. Please advise. |
…rements conditions.
@jamesrhester thank you for the work and sorry for not responding sooner. As discussed, I added two examples files that illustrate the new approach to recording cell measurement details based on the discussions in #299. Please check if they are ok. The single block example files currently invents a few data names (e.g. Once you are happy with these examples, it would be nice if some other stakeholders could review them as well. I will ask some of my colleagues from the COD to take a look, but maybe there are some other database/IUCr archive people who would be affected by this that you are aware of? |
I have updated the examples to clarify a few things.
This change is a logical extension of the multi-block approach that was discussed at length. What I propose doing is, as part of the release process, providing a proper description of all the changes (perhaps as a wiki page) and inviting everybody on COMCIFS/Core-DMG/cif-developers to review what has been written about those changes. Reviewers would have a few weeks to comment. |
Ok, so from your updated comment in the On a related note, I added an example that uses the deprecated items and tried to highlight the benefits of the multi-block approach. Finally, I will probably add the superfluous If you are good with these changes, I am happy to merge. |
I'm happy with those changes, so I think we are ready to merge? |
The file is no longer relevant as an example.
Great. @jamesrhester, should I merge it or will you? |
Thanks everybody for your contributions to this very complicated PR! |
This replaces #299, dealing with issue #294 . Please refer to the discussion in those places for information. This PR provides nothing new compared to #299 , it just accounts for the updates to master.
Because of the reordering of the definitions, the usual Github diff looks very messy. The semantic changes are in commit 339aaa7 , so probably best to look at that to understand the changes. The commit after that only changes the order and pretty-prints.