Differences between revisions 12 and 13
Revision 12 as of 2015-08-14 15:59:26
Size: 3358
Editor: SteveLudtke
Comment:
Revision 13 as of 2015-08-14 16:01:25
Size: 3414
Editor: SteveLudtke
Comment:
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
 * files specified via --input, --model for e2refine_easy
 * files specified via --input and --model or --models
 * strucfac.txt should normally be present in the project directory. This is a text file containing the ideal 1-D structure factor expected for the final map. Intensity as a function of spatial frequency.
 * '''files specified via ''--input'', ''--model'' for ''e2refine_easy'' '''
 * '''files specified via ''--input'' and ''--model'' or ''--models'' '''
 * '''strucfac.txt should normally be present in the project directory''' - This is a text file containing the ideal 1-D structure factor expected for the final map. Intensity as a function of spatial frequency.
Line 30: Line 30:
 * file specified via --input  * '''file specified via ''--input'' '''

EMAN2 Output Files

This page documents all of the various files produced by various tasks and workflows in EMAN2. While the format of the actual files will be one of the standard EMAN2 supported image formats in most cases, these pages will explain the contents of files with specific standard names.

General File Information

Information on specific input/output files in 3-D single particle refinement runs (e2refine_easy.py and e2refinemulti.py)

Input files:

  • files specified via --input, --model for e2refine_easy

  • files specified via --input and --model or --models

  • strucfac.txt should normally be present in the project directory - This is a text file containing the ideal 1-D structure factor expected for the final map. Intensity as a function of spatial frequency.

Output files (in temporal order of creation), _xx denotes the iteration number:

If you are struggling with a failed refinement, look at the produced files in this order until you find something unexpected, and that may give some clues as to what went wrong.

Information on specific input/output files from 2-D reference-free class-averaging (e2refine2d.py)

You may also wish to look at: e2refine2d Input files:

  • file specified via --input

Output files:

  • input_fp - rotational/translational invariants for each particle

  • input_fp_basis - MSA basis vectors (images) from input_fp

  • input_fp_basis_proj - MSA subspace projections of the input_fp invariants

  • classmx_00 - Initial classification of particles, same format as classmx above

  • classes_init - Initial set of class-averages from invariant method (not very good usually)

  • allrefs_XX - All of the references (sorted and aligned) to be used for the current iteration. Other than sorting/alingment, same as classes_XX files

  • basis_XX - MSA basis from allrefs_xx

  • aliref_XX - Subset of allrefs used for alignment of raw particles

  • simmx_XX - Similarity matrix in same format as simmx above

  • input_XX_proj - Aligned particles projected into basis_XX subspace

  • classmx_XX - Classification matrix for the current iteration (as above)

  • classes_XX - Class averages at the end of the iteration. The highest numbered classes_XX file is the final output of the program

EMAN2/ProgramFiles (last edited 2023-09-29 12:45:12 by SteveLudtke)