The CIF file contains data categories, such as audit, atom, cell, database, and refine. These categories contain information, including the CIF creation, atom type properties, cell parameters, data specified by the database managers, and data describing structure refinement parameters. Programs that open CIF files. Iotbx.filereader.anyfilefast(filename, getprocessedfile=False, validtypes='pdb', 'hkl', 'cif', 'pkl', 'seq', 'phil', 'aln', 'txt', 'xplormap', 'ccp4map. A single element character vector containing the name of the mmCIF file to be read, or the four letter PDB identifier for online file access. The maximum number of lines to read before giving up with large files. By default if will read up to the end of input on the connection. Logical, if TRUE multiple ATOM records are read for all models in.

Structure files

The structure of a to-be-analyzed material has to be provided in one of Zeo++ compatible file format: CSSR, CUC, V1, CIF, CAR, DLP and PDB. Additional requirement for the formats is that the structure file contains the complete unit cell (P1 symmetry). Therefore, any structure represented by an assymetric unit and symmetry information has to be extended to P1 symmetry (i.e. the unit cell needs to be constructed) before it can be processed with Zeo++. CIF files can contain either the entire unit cell with all atoms or an asymmetric unit with symmetric information. In the current version the latter has to be specified in terms of a list of symmetry operations in order to have Zeo++ build the full unit cell.
Moreover Zeo++ can also read structures from MOPAC's .arc output files.

Discussed file formats: CSSR | CUC | V1 | CIF |ARC and others.

CSSR file format

CSSR format is a file format used by many molecular simulation packages and therefore it was adopted in Zeo++. A CSSR file contains unit cell definition and a list of atoms with their fractional coordinates.

An example of CSSR file for IZA's EDI zeolite is provided below:

We also noticed that CSSR files generated by Open Babel have slightly different format. In order to read those into Zeo++, please change their names to .obcssr before running Zeo++.

CUC file format (subject to change)

CUC is a custom format introduced on the course of development of Zeo++. It contains the same information as the CSSR format but it has a simpler format.The first line is a comment/title line. The second line contains periodic unit cell information: lengths of a, b and c vectors and three unit cell angels. The third and following lines specify atoms and their fractional coordinates.

An example of CUC file for IZA's EDI zeolite is provided below:

Cif File Reader Chrome

V1 file format

V1 is a custom format introducted on the course of development of Zeo++. It contains periodic unit cell definition and a list of atoms. The unit cell is defined using three vectors. It is required that y and z coordinates of the first vectors as well as z coordinate of the third vector are set to zero (vectors alligned with axis of the coordinate system). The unit cell definition is followed by an integer - a number of atoms, and then a list of atoms with their Cartesian coordinates.

An example of v1 file for IZA's EDI zeolite is provided below:

Cif File Reader Download

CIF file format

CIF file format is a common format for storing crystal structure information (esp. experimental data). The CIF file reader in Zeo++ is under development: it can handle most of the files but occassionally fails on misformetted CIFs. Please contact us if it happens. Alternatively, other codes (e.g. CCTBX) can be used for converting your files into CSSR or other formats handled by Zeo++.

An example of cif file for IZA's EDI zeolite.

Cif File Reader Python

ARC and others

Cif File Reader Free

The recent versions of semiempirical electronic structure code, MOPAC, can handle periodic systems. It makes it suitable to investigate porous polymers, structure of which can be also analyzed using Zeo++.

Cif File Reader Pro

Other files formats such as .dlp, .car, .pdb can be also read by Zeo++. However, we noticed some variations in these and sometime the source code needs to be altered a bit to process a particular file.