Differences between revisions 9 and 10
Revision 9 as of 2011-07-06 04:00:00
Size: 1542
Editor: SteveLudtke
Comment:
Revision 10 as of 2012-07-31 12:57:21
Size: 1670
Editor: SteveLudtke
Comment:
Deletions are marked like this. Additions are marked like this.
Line 27: Line 27:
 * [[EMAN2/Eman1Transition/Workflow|I want to give the new workflow a try]]  * [[EMAN2/Eman1Transition/Workflow|I want to give the (old) workflow a try. (Note: the workflow is being replaced by e2projectmanager.py, but this portion of the documentation hasn't been updated yet)]]

Moving from EMAN1 to EMAN2

A choice of paths

EMAN2 can be used in many different ways:

  • A high-level integrated workflow interface
  • Stand-alone GUI tools (like EMAN1)
  • Command-line programs (direct analogs to EMAN1)
  • A Python library (a easy to learn scripting language)
  • A C++ library

We strongly encourage most users to use the workflow interface, as this offers an integrated solution which:

  • takes you step by step through the reconstruction process, with help along the way
  • Stores all data in a logical organization of subdirectories, and keeps track of all details at each step of the process, so the final results can be archived, used to seed an EMDatabank/PDB submission, etc.
  • shows you all of the complicated command line options in an organized fashion so you don't forget anything

However, it is also quite possible to use EMAN2 directly from the command-line very much like EMAN1.

We have separate guides depending on what you want to do:

EMAN2/Eman1Transition (last edited 2012-07-31 13:00:20 by SteveLudtke)