Open rowlesmr opened 2 years ago
Yes
On Sep 19, 2022, at 4:11 AM, Matthew Rowles @.**@.>> wrote:
In conversation with colleagues, the recording of experimental conditions for in situ/operando data came up.
(This may be better suited for core, but I'll start here, and it can be migrated later.)
Currently, we can record the temperature, pressure, and environment (ie gas/liquid if not air) at which intensities were measured. There are many more things that can be controlled during an experiment:
Is this worth pursuing?
— Reply to this email directly, view it on GitHubhttps://github.com/COMCIFS/Powder_Dictionary/issues/22, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACH7E2A27JNAPPPTJE6C6M3V7AU3DANCNFSM6AAAAAAQP5DUNQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>
These are definitely worth developing but most of them would be more useful in a general "environment" extension dictionary as none of them are powder-specific. Given the breadth of techniques listed you'd probably want to collect together a specialist group, have monthly meetings to hash out the contents etc. COMCIFS can provide a Github workspace here to do that if you can provide the specialist group - my colleagues at ANSTO could cover quite a few of those topics but that might be a bit too geographically non-diverse.
A further note is that a lot of these techniques require providing geometric information. There is a proto-proposal soon to be presented by the high-pressure community which would give a CIF framework for doing this, so it might be worth waiting for that.
Roger. I was thinking to expand the available _diffrn data names.
I was also thinking that something like magnetic/electric field would also need some direction recorded as well, esp. with single xstal work.
I've emailed a bunch of people (including ANSTO sample environments) and have had some feedback on things to record.
This is a bit of a datadump of things so far.
all data names below also have:
_su
: Standard uncertainty of _____ at which intensities were measured._gt
: _____ above which intensities were measured. _lt can also be used to create a range._lt
: _____ below which intensities were measured. _gt can also be used to create a range._details
: A description of special aspects of _____ during data collection. New data names:
_diffrn.ambient_electric_field
_diffrn.ambient_magnetic_field
_diffrn.applied_voltage
_diffrn.applied_current
_diffrn.applied_stress
_diffrn.applied_strain
_diffrn.ambient_relative_humidity
_diffrn.ambient_illumination_intensity|brilliance|flux|luminance
_diffrn.ambient_illumination_wavelength|wavenumber|energy
Questions to answer:
_diffrn.crystal_treatment
enough?This is a good starting list I think.
_lt
and _gt
data names are usually a bad idea unless the quantity couldn't be measured and these are needed to say something like "I know it's no more than this but otherwise no idea" e.g. if a sample would have melted above a certain temperature. Generally better to use the _su
data name to indicate the accuracy of the values or variability during measurement.
Field, voltage, stress, strain would require directional information. Stress and strain are likely to need a whole separate loop or else some qualification to note that they are isotropic.
The ambient
data names (not electric or magnetic) could be created without much further consultation on the assumption that they imply isotropic conditions.
In conversation with colleagues, the recording of experimental conditions for in situ/operando data came up.
(This may be better suited for core, but I'll start here, and it can be migrated later.)
Currently, we can record the temperature, pressure, and environment (ie gas/liquid if not air) at which intensities were measured. There are many more things that can be controlled during an experiment:
Is this worth pursuing?