Save: Difference between revisions

From PyMOLWiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
Line 9: Line 9:
   
   
===USAGE===
===USAGE===
<pre>
<source lang="python">
save file [,(selection) [,state [,format]] ]
save file [,(selection) [,state [,format]] ]
</pre>
</source>
===PYMOL API===
===PYMOL API===
<source lang="python">
<source lang="python">
cmd.save(file, selection, state, format)
cmd.save(file, selection, state, format)
</source>
</source>
 
===NOTES===
===NOTES===
* When saving a session file, then "state" has no effect.
* When saving a session file, then "state" has no effect.
* When state = 0 (default), only the current state is written.
* When state = 0 (default), only the current state is written.
* When state = -1, then a multi-state output file is written (PDB only).
* When state = -1, then a multi-state output file is written (PDB only).
 
 
===SEE ALSO===
===SEE ALSO===
   [[Cmd load]], [[Cmd get_model]]
   [[Cmd load]], [[Cmd get_model]]


[[Category:Commands|save]]
[[Category:Commands|save]]

Revision as of 12:08, 29 June 2005

DESCRIPTION

save writes selected atoms to a file. The file format is autodetected if the extesion is ".pdb", ".pse", ".mol", ".mmod", or ".pkl"

Note that if the file extension ends in ".pse" (PyMOL Session), the complete PyMOL state is always saved to the file (the selection and state parameters are thus ignored).

USAGE

save file [,(selection) [,state [,format]] ]

PYMOL API

cmd.save(file, selection, state, format)

NOTES

  • When saving a session file, then "state" has no effect.
  • When state = 0 (default), only the current state is written.
  • When state = -1, then a multi-state output file is written (PDB only).

SEE ALSO

  Cmd load, Cmd get_model