One issue that came up informally during the DDD meeting at Bergen
concerns the ever‐vexed issue of image file formats, and whether the
imgCIF/CBF standard (I’ll just call it imgCIF from now on) is being
used in the best way. The issue seems to be, not with what is
NECESSARY for an image to be a valid imgCIF, but what is SUFFICIENT
for it to be fully useful in the future.
What we would like to ensure I suppose is that all the information
needed for processing the image in the future, is in fact correctly
encoded in the image header using the standard imgCIF “data
names”. Maybe we could come up with a compliance test program, perhaps
derived from already‐existing automated processing software, which has
all knowledge of specific detector types stripped out, so that it
depends strictly and solely on the CIF header.
Do we need compliance testing for imgCIF/CBF?
This is a public forum that invites community input on strategies and desirable practices in providing open and long-term access to diffraction data sets.
Moderator: Brian McMahon
Return to “Public input on diffraction data deposition”
Jump to
- Executive Committee
- ↳ Journals review committee
- ↳ IYCr steering committee
- Commissions
- ↳ Crystallographic Nomenclature
- ↳ Biological Macromolecules
- IUCr journals
- ↳ Journal Editors and Section Editors
- ↳ Acta A Co-editors
- ↳ Validation and publication
- International Tables for Crystallography
- ↳ Volume H: Powder Diffraction
- ↳ Volume H planning
- ↳ Volume B: Reciprocal Space
- ↳ Volume B/C planning
- Standing Committees and Working Groups
- ↳ Diffraction data deposition
- ↳ Consultation on diffraction data deposition
- ↳ Public input on diffraction data deposition
- ↳ Description of Nanomaterials
- ↳ Committee on Data
- ↳ Public input to CommDat
- Crystallographic Information Framework
- ↳ CIF Application Programming Interface
- ↳ CIF dictionary namespace conventions
- ↳ NeXus HDF5 CIF convergence
- ↳ Core CIF review and update
- ↳ CIF2.0
- Sandbox
- ↳ Online dictionary tests
- ↳ Testing
- ↳ test