|
Size: 1487
Comment:
|
Size: 1698
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| ==== '''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. |
==== <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. While there is, of course, metadata in the image headers, THIS metadata is not stored in the header because the information, such as CTF information, is associated with multiple image files, including the micrograph itself, as well as particle stacks, etc. |
| Line 10: | Line 10: |
| ||||Parameter||||Description|||| | ||Parameter||Description|| ||boxes||The list of particle locations in the micrograph from e2boxer.py|| ||boxes_tilted||The list of particle locations in the micrograph from e2boxer.py|| ||boxes_untilted||The list of particle locations in the micrograph from e2boxer.py|| |
| Line 12: | Line 15: |
| ||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. | ||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.|| |
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. While there is, of course, metadata in the image headers, THIS metadata is not stored in the header because the information, such as CTF information, is associated with multiple image files, including the micrograph itself, as well as particle stacks, etc.
Parameter |
Description |
boxes |
The list of particle locations in the micrograph from e2boxer.py |
boxes_tilted |
The list of particle locations in the micrograph from e2boxer.py |
boxes_untilted |
The list of particle locations in the micrograph from e2boxer.py |
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 |