-
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
Linking refinements to the data sets used #344
Comments
re powder, it also depends on how you define "refinement".
|
This is absolutely an important task. There's on easy answer: one refinement must include everything that contributes to the calculation of chi^2 (or the quantity being minimised). So if multiple diffraction patterns and phases are involved, then that is one refinement. A refinement requires observations and a model. A refinement would associated with an identifier, which would come from a A model, on the other hand, is the result of a particular refinement. Perhaps we want a separate Not forgetting restraints and constraints, covered by a separate dictionary but also relevant to particular refinements. Note these thoughts are relative to cif_core, and haven't touched on powder, for which multiple structures are often refined simultaneously. |
(coming from a powder point-of-view)
It could be better described as
You could then link Other arguments: I feel that
|
That |
(Issue created so as not to forget it - this was work done as part of thinking about where
CELL
belongs. I don't think this is an urgent task).Up until now, the link between a refined structural model and the data it is based on was simply by virtue of being in the same data block. In multi-block scenarios we need to explicitly link a particular model with data. So I propose:
Create
refine.id
to identify a refinement.Create
_refine_diffrn.refine_id
and_refine_diffrn.diffrn_id
: key data names of newREFINE_DIFFRN
category, listing the datasets (_diffrn.id
) used in the refinement e.g.describing two refinements, one which used a neutron and xray dataset and one which used two xray datasets.
Open question: how would this (if at all) interact with powder diffraction, where the data set is linked to
_diffractogram.id
rather than_diffrn.id
.The text was updated successfully, but these errors were encountered: