GSAS-II can write both results and imported data. There are many types of exports that GSAS-II can make, and in most cases there are a variety of supported export formats. As mentioned earlier, it is often a simple task to add support for additional formats.
A GSAS-II project contains one or more phases and one or more histograms. All of this is bundled into a binary .gpx (project) file when the File/“Save project” menu command. Good luck trying to read that file, other than to read it into GSAS-II, unless you are pretty comfortable with Python programming and even then it will take some work to find where different things are stored. (There is some is some documentation on this in the Programmer’s manual in the “GSASII Data object & variable organization” chapter, https://gsas-ii.readthedocs.io/en/latest/objvarorg.html).
The exports in this menu provide access to the entire contents of the GSAS-II project. The most valuable of these is the Full CIF, which provides a customizeable CIF appropriate for deposition with a publication. The Chapter on 22 discusses this in depth. The “ASCII Json dump” will create a very large file that contains the entire contents of the .gpx file in the Json format. This file can be read into editors or listed, but the file will be several times larger. This export has no routine use, but may be of value for code development, debugging or just learning about how GSAS-II works. The two CSV export menu commands, which were provided by users, create spreadsheet files with a tabulation of many GSAS-II parameters. In the case of “Bracket notation,” this is a reference for crystallographic notation for uncertainties [such as -1.021(2), see §7.6.2.0] and this export will have quantities listed with their uncertainties.
Note that this menu is disabled with sequential refinements. Use the “Sequential project as CIF” menu command. The same command is also available in the “Seq Export” menu in the “Sequential results” data tree entry, which does offer additional options.
The export options for phases are typically used to bring coordinates into other software for structural analysis, including graphics. The “Quick CIF” option provides a phase-only CIF that does not include crystallographic uncertainties. This is very helpful as a way to use an external program for a task such as visualization, but the CIFs produced here are not recommended to document a project. Use the Project-based CIF export, which does include uncertainties on fitted quantities.
Note that this menu is disabled with sequential refinements. Use the commands in “Sequential phases” submenu command. The same commands are also available in the “Seq Export” menu in the “Sequential results” data tree entry.
When the powder data export menu command is used, you will be asked which powder diffraction histogram(s) should be exported, unless there is a single powder histogram, in which case that question does not need to be asked. The data file formats used for experimental data will include only the measured diffraction intensities, but most of the other formats will include the calculated pattern as well and some will provide separate values for the background values. It is also possible here to export the reflection list. Those options will not include the powder diffraction intensities, but instead report the values seen in the histogram’s “Reflection Lists” data tree entry.
Note that this menu is disabled with sequential refinements. Use the commands in “Sequential histograms” submenu command. The same commands are also available in the “Seq Export” menu in the “Sequential results” data tree entry.
Fourier maps (discussed in §20.2) can be exported for viewing in external software. At this time, only the CCP4 map format (primarily used for macromolecular crystallography) and and the format used in FOX and DrawXTL are supported.