<i>checkCIF</i> validation ALERTS: what they mean and how to respond.
Spek AL. · 2020
Read <i>checkCIF</i> validation ALERTS: what they mean and how to respond. by Spek AL. (2020) in the Tower of Babel, a free online library of public-domain works preserved in clean, searchable text. No sign-up. The full text is served as a plain-text file at a predictable URL, where text is present: https://antarctic-labs.com/tower-of-babel/europmc-pmc6944088.txt.
Introduction
Spek explains how to read and answer checkCIF alerts, the warnings raised when crystal structures are validated. His paper appeared in Acta Crystallographica Section E. Modern instruments and software make collecting X-ray diffraction data fast and routine. Solving a structure is often a black-box step. The real bottleneck is final analysis, validation, and proper reporting.
Less trained authors can miss warning signs that seasoned crystallographers spot at once, such as oddly short contacts between molecules. Pitfalls include pseudo-symmetry, disorder, and twinning. Spek gives background on the validation procedure and details many specific alerts. For each, he sets out options for how to respond. The goal is simple: readers should be able to trust the chemistry a structure claims to show.
Catalog record
| CREATOR | Spek AL. |
|---|---|
| YEAR | 2020 |
| COLLECTION | PAPERS |
| FORMAT | TXT |
| FILE SIZE | 54 KB |
| LICENSE | CC BY 4.0 |
| RIGHTS | CC BY |
| SOURCE | Europe PMC |
Browse the full library · About the Tower of Babel
Full text
The opening of the work, from the library's hosted text:
checkCIF validation ALERTS: what they mean and how to respond By Anthony L. Spek Published in: Acta Crystallographica Section E: Crystallographic Communications DOI: 10.1107/S2056989019016244 ABSTRACT This paper provides additional background information on the checkCIF procedure and additional details for a number of ALERTS along with options for how to act on them. INTRODUCTION Developments in diffractometer technology and software have made the collection of X-ray diffraction data on single crystals rapid and routine. The same applies in most cases for the preliminary structure-solution phase, given diffraction data of reasonable quality. Current structure-solution programs such as SHELXT (Sheldrick, 2015a ▸), SUPERFLIP (Palatinus & Chapuis, 2007 ▸) and SIR (Burla et al., 2003 ▸) have made the preliminary solution of the phase problem in most cases a trivial black-box operation. The bottleneck to a publishable report is often the final analysis, validation, reporting and proper archiving of the experimental data and refinement results. The large volume of automated ‘routine’ crystal-structure determinations often leaves less time available for a detailed analysis of the results. Unfortunately, it is easy for less crystallographically trained authors, depending on the automated procedures, to fall into one of the well-known pitfalls such as pseudo-symmetry (Clegg, 2019 ▸). The reported chemistry may be wrong when signals such as short intermolecular contacts, that are clear for experienced investigators, are misunderstood or ignored. Not all published crystal-structure studies are based on the best attainable diffraction data, but rather on data that are considered to be suitable for the purpose of the study (Thompson, 2019 ▸). A good-looking ‘ORTEP’ illustration in a chemical journal is often considered as sufficient proof of the reported chemistry. Crystal structures are not always ‘well-behaved’, often related to sub-optimal crystal quality, experimental issues, or disorder or twinning. Structural disorder can be pursued in great detail with constraints and restraints or handled in a way sufficient for the study of the main species of interest, for example using tools such as PLATON/SQUEEZE (Spek, 2015 ▸) for handling disordered solvents as part of the structure refinement. Readers need to know whether reported geometrical details, such as inter-molecular contacts or bond distances, involve restrained or constrained parameters. All this and residual issues should be clearly documented in the structure report. Reported crystal structures end up in the Cambridge Structural Database (CSD; Groom et al., 2016 ▸) as curated but otherwise largely unqualified database entries. It is therefore of the utmost importance that all experimental data, data reduction and refinement details are archived as well. In that way, users of those data can do their own evaluation of the reported crystal structures or use the experimental data for more detailed studies in a different context. Those data may be hard to obtain again, either because of the involved synthesis of the compound of interest or the difficulty in obtaining a particular polymorph again. During the 1980s, with the growth in the number of structure reports, the need for a standard computer-readable format for the exchange and archival of crystallographic data became clear. Obviously, that would avoid the error-prone retyping of numerical information, such as the refined parameter values, into the desired format from typo-prone manuscripts. It would also make the diffraction data more accessible for processing. Such a standard, called CIF, was proposed by Hall et al. (1991 ▸). One of the early adopters of that format was George Sheldrick with his new and popular 1997 version of the SHELXL (Sheldrick, 2008 ▸) structure-refinement program, making CIF widely accepted as a data-archival format, along with the CIF-style structured FCF file with observed and calculated reflection data. Those data were previously available only as printed F obs, F calc and σ(F obs) tables. Interestingly, SHELXL does not read and write CIFs for its own input and output. For efficiency, it uses for its calculations the non-CIF-structured RES and HKL computer- and human-readable files for the input and storage of refinement details and reflection data, respectively. Those files have also become a de facto exchange standard for a number of applications and programs such as the CSD utilities (Groom et al., 2016 ▸). Today, the archived material is expected to include not only the structural results, but also the unmerged reflection data (either as a CIF-structured reflection-data loop or as embedded SHELXL-style name.hkl file) and details of the data reduction and non-standard refinement details (CIF-structured or as an embedded SHELXL-style name.res file). Those files can easily be extracted from the CIF with the shredcif utility and used for alternative refinements. Most current structure-refinement packages include that information in the CIF file. The introduction of the CIF standard also opened the way for the automated checking of the archived data for their internal consistency and completeness, which was needed to handle the exploding number of structure reports. The International Union of Crystallography (IUCr) journal Acta Crystallographica Section C pioneered automated structure validation as a tool for authors, referees and readers. This project started with flagging missing data and inconsistencies and testing numerical data against expected values. The result was a report consisting of a list of ALERTS, with associated A, B and C levels of importance, for issues that needed to be addressed. It should be clear that ALERTS are not necessarily errors. They might also point to interesting features in a crystal structure. G-level ALERTS, which were introduced later, are mostly informative but are not to be neglected. All ALERTS should be checked by the authors: a set of lower-level ALERTS may in combination point to a serious issue that needs to be addressed. Currently, IUCr/checkCIF includes, in addition to the above-mentioned ALERTS, PLATON/checkCIF (Spek, 2003 ▸) based ALERTS (starting with ‘PLAT’ followed by a number) implementing some 500 additional tests for issues such as missed symmetry, missed twinning and missed solvent-accessible voids in the crystal structure. This paper is a follow-up to earlier papers on the validation issue and checkCIF (Spek, 2003 ▸, 2009 ▸, 2018 ▸). It offers additional background details for a number of more commonly issued ALERTS along with suggestions on how to address them. Three types of archived information should be available: (a) crystal data such as cell parameters, symmetry, refined model parameters, derived geometry and R values – those data (name.cif) are checked for completeness, internal consistency and expected parameter values; (b) the final ‘FCF’ file (name.fcf) with calculated and observed intensities and associated σ(I)/weight to check the reported final R and S values along with an analysis-of-variance analysis of the refinement results; (c) the unmerged h, k, l, I obs, σ(I obs) reflection data [CIFs created using SHELXL (Sheldrick, 2015b ▸) include this ‘HKL’ file (name.hkl) along with the final refinement instruction ‘RES’ file (name.res) as embedded data as values of the _shelx_hkl_file and _shelx_res_file CIF datanames along with associated checksums reported as values of the datanames _shelx_hkl_checksum and _shelx_res_checksum, respectively]. No archival of the final FCF file is needed in the case of matching calculated and reported checksums for the name.res and name.hkl files. In the case where a final name.fcf is recreated with SHELXL from the embedded name.hkl and name.res files and recalculated, the final R and S values are compared with those reported in the CIF for consistency. Otherwise the final name.fcf file