9.3 Coot Droppings

This describes the files and directory that coot leaves behind after it has been fed (sorry, I mean “used”). Everything except the 0-coot.state.scm state file can comfortably be deleted if needed after coot has finished.

You can stop the state and history files being written if you start coot with the --no-guano option.

• 0-coot.state.scm The most important file. This contains the state of coot when you last exited. It contains things like which molecules were read, the maps, the colours of the molecules and map, the screen centre, map size and so on. When restarting a coot session, this file should usually be used.
• 0-coot-history.scm The history of coot commands you used in your last coot session in scheme format. Incomplete history. One day this will be a complete history of the session suitable for uploading into a database describing the model modification.
• 0-coot-history.py The history of coot commands you used in your last coot session in python format.
• coot-download directory where the files downloaded from the network (e.g. from the EBI and EDS) go.
• coot-backup Each model modification generates the saving of coordinates as a pdb file in this directory.
• coot-refmac When running REFMAC using the Coot interface, the input to refmac and the output go in this directory.
• coot-molprobity When running Molprobity's Probe and Reduce using the Coot interface, the input and output go in this directory.