This tab generally helps with managing the manual annotation of your particles with Imod.

Specifically, this tab served for picking the ‘seeds’ particles needed for the later “expand” process. In addition, this tab can also be used for the initial reference generation if you don’t have a template yet.

The entire picking principle is based on the *stalkInit* program in PEET. If you are not familiar with what this is, check this example or https://bio3d.colorado.edu/RML_2017/2017_IMOD_PEET_Workshop/Lectures/ModelingAids.pdf

Untitled

In conclusion, this tab can be used for the following scenarios/applications:

  1. Lattice-like particles: picking ‘seed’ particles
  2. scattered particles (ribosomes or glycoproteins, etc.)

Our tutorial will only focus on the 1st applications (lattice-like particles).

Inputs needed before running:

  1. A user-created folder containing the reconstructed tomograms that will be used for the sub-tomogram average.

    For examples:

Output you will get:

Root directory

— ManualPick:

— stalkInit_prep: (*.mrc/rec, *_side.mod, *_top.mod, *_bottom.mod) Directory storing particle picking results required for stalkInit. All the operations resulting from the “Top”, “Bottom”, “Side” and “Combine All” functions will be saved here.

— initParams: The directory will store 4 new initial alignment files per tomogram from stalkInit results.

  1. One *.mod that stores the coordinates of the center for each particle.
  2. One *_initMOTL.csv that stores the corresponding initial translation and rotation information.
  3. One *_RotAxes.csv that stores the particle Y-axis information.
  4. One .mrc/.rec file will be used for the STA. (Note: If you want to use other maps to replace the one you used for initial picking, then just delete this link file and make the new link file)

Below is the GUI used for manual particle picking.

Fig. 4: Particle picking GUI

Fig. 4: Particle picking GUI

Click on the browser button for the “Map for Pick” folder. Choose the Manual/tomograms folder and the cells should populate like in Fig. 4.