|
Size: 1201
Comment:
|
Size: 1487
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| ==== ctf_parm.js ==== This file stores the CTF parameters for all images in the project as EMAN2CTF objects, keyed by '''basename'''. CTF objects are stored in ''.js'' files in a human-readable form as a dictionary, so individual values can be easily read and, if necessary, edited. |
==== '''basename'''_info.js ==== Per micorgraph information is stored in one file for each micrograph. This allows easy copying of micrographs with their metadata between projects. The data is not stored in the image file header because the information, such as CTF information, is associated with multiple image files, including the micrograph itself, as well as particle stacks, etc. Specific metdadata will also be stored in the header of appropriate image files. |
| Line 10: | Line 10: |
| ==== quality.js ==== This file stores user-assigned quality values per-micrograph. The key is the ''basename'' of the image file. Quality values run from 0-9 and may be used in any way the user prefers. They have no absolute meaning to any of the processing software, though there are places where higher will be assumed to indicate ''better'' images by whatever standard. |
||||Parameter||||Description|||| ||ctf||A list of CTF related objects: [EMAN2CTF instance, || ||quality||A single integer from 0-9. No predefined meaning, though 5 is the default value, and larger should be interpreted as better. This is to permit qualitative assessement by the user at various stages of analysis. ||select_bad||A list of integer particle numbers which have been determined to be 'bad'. The 'bad' particles may optionally be excluded when building sets|| |
Metadata Stored in the ''info'' Folder
The info folder is a replacement for the BDB-based EMAN2DB folder in the project directory. All information is stored in human-readable and editable JSON files with a .js extension.
For each micrograph in the project a basename is assigned, to avoid confusion as the data goes from raw micrograph to particles, etc. That is, a file named micrographs/jj1234.mrc would use the basename jj1234. particles/jj1234.hdf would use the same basename.
'''basename'''_info.js
Per micorgraph information is stored in one file for each micrograph. This allows easy copying of micrographs with their metadata between projects. The data is not stored in the image file header because the information, such as CTF information, is associated with multiple image files, including the micrograph itself, as well as particle stacks, etc. Specific metdadata will also be stored in the header of appropriate image files.
Parameter |
Description |
|||
ctf |
A list of CTF related objects: [EMAN2CTF instance, |
|||
||quality||A single integer from 0-9. No predefined meaning, though 5 is the default value, and larger should be interpreted as better. This is to permit qualitative assessement by the user at various stages of analysis.
select_bad |
A list of integer particle numbers which have been determined to be 'bad'. The 'bad' particles may optionally be excluded when building sets |