Differences between revisions 6 and 10 (spanning 4 versions)
Revision 6 as of 2013-05-23 14:30:36
Size: 1726
Editor: SteveLudtke
Comment:
Revision 10 as of 2013-06-27 01:58:55
Size: 2065
Editor: SteveLudtke
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
==== project.js =====
This file contains overall project parameters, such as A/pix, voltage, mass, etc.

==== notebook.js ====
This is where the projectmanager stores the text entered in the 'lab notebook'.
Line 8: Line 13:
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. 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 14: Line 19:
||ctf||A list of CTF related objects: [EMAN2CTF instance, || ||ctf||A list of CTF related objects: [EMAN2CTF instance,signal 1D,background 1D,signal 2D, background 2D] computed from particles, not the overall frame ||
Line 16: Line 21:
||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|| ||sets||A dicitionary containing lists of integers keyed by set name||
|| * bad_particles||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. ==== project.js ===== This file contains overall project parameters, such as A/pix, voltage, mass, etc.

notebook.js

This is where the projectmanager stores the text entered in the 'lab notebook'.

<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,signal 1D,background 1D,signal 2D, background 2D] computed from particles, not the overall frame

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.

sets

A dicitionary containing lists of integers keyed by set name

* bad_particles

Particle numbers which have been determined to be 'bad'. The 'bad' particles may optionally be excluded when building sets

Eman2InfoMetadata (last edited 2019-07-31 22:17:45 by MuyuanChen)