CryoET Training data from CryoET tilt-series of Agrobacterium jumbo phage 7-7-1 and bacterial flagella

Two raw tilt-series (in MRC format) of highly-purified jumbo bacteriophage in association with bacterial flagella. MDOC files are also provided.

Data Processing Guide


Specimen background

Jumbo bacteriophages are exceptionally large viruses that infect bacteria. They consist of a protein shell, or capsid, that encloses the phage DNA genome, along with a tail and baseplate that mediate attachment to the host cell. The Agrobacterium bacteriophage 7-1-1 is a jumbophage capable of binding to bacterial flagella, which it uses to move along the filament toward the cell body prior to infection. This dataset contains tilt-series data of bacteriophage 7-1-1 particles interacting with long bacterial flagellar filaments.

EMPIAR author information: Noteborn WEM, Hoeksma T, Rouchen OY, Briegel A

Paper DOI: https://doi.org/10.1038/s42003-025-09319-7

EMPIAR deposition: EMPIAR-13014

SBGrid CryoET ChallengeBank DOI: 10.15785/SBGRID/1263

Why this dataset is challenging:

  • The capsid fibers are small, thin and highly flexible. Segmentation must be done manually.

Time to completion: ~1.5 days (only 1 day if you choose to use the missing-wedge-corrected tomogram provided rather than compute correction yourself)

Computing required: This guide was made with the intention that an investigator will have access to 4 GPUs. More GPUs is certainly better, and less will mean processing will take longer than the time estimates provided in this guide. The estimates are just rough guides based on our workstation. Ultimately, we leave the computing power dedicated to this tutorial to the discretion of the investigator.

Storage required: 85G (after all the processing is completed).

Software suggested: Multiple software packages need to be used to complete the entire reconstruction. Investigators are welcome to complete as little or as much of the reconstruction pipeline as desired, and tomograms are available if you would prefer to skip certain steps.

For this dataset, we recommend WarpTools dev36 (5.0.0), Imod/3Dmod (4.11.25), IsoNet (0.3), mod2mrc and UCSF ChimeraX (1.1_rhel9).

Overview of the data

This dataset contains 2 tilt-series of highly-purified jumbo bacteriophage 7-1-1 and long bacterial flagella filaments. This tutorial guides the user through the reconstruction process of producing tomograms, performing missing wedge correction and manually segmenting a phage and flagella filament.

We will be following the basic steps of tomographic reconstruction:

  1. Data Pre-Processing
  2. Tilt-Series Alignment
  3. Tomogram Reconstruction
  4. Tomogram Post-Processing
  5. Manual segmentation
Processing pipeline: WarpTools, IsoNet, 3dmod, ChimeraX, and mod2mrc
Overview of the WarpTools, IsoNet, 3dmod, ChimeraX, and mod2mrc workflow used in this guide.

Download the ChallengeBank dataset

If you have not already downloaded the data, open a command terminal window and type the following command:

rsync -av rsync://challengebank.sbgrid.org/10.15785/SBGRID/1263

Check the integrity of the download by assessing if all the components are correctly downloaded to your computer. This pack should contain .tif images, .mdocs, a gain.mrc, and a copy of these instructions.

Processing bundle

Download the processing bundle

A quick note on terminology

New tomographers are often confused about the difference between a frame series, a movie, a micrograph and a tilt series. If you know these terms, skip to the next section. If you’re unsure, keep reading.

When a dataset is collected on the microscope, a short movie is taken by exposing the sample to a certain dose of electrons over a certain period of time. The dose is fractionated into frames over the time taken to collect the movie. The movie is therefore composed of a series of frames, called a frame series. The sample stage is then tilted in the microscope in preparation for collecting the next movie (or frame series). At the end of data collection, you will have a collection of movies, each taken at a different discrete angle. The whole collection of movies/frame series acquired across the tilt range constitutes the raw tilt-series data. After motion correction and summing, each frame series yields one tilt image (micrograph) because (almost) all the subframes get summed together to increase the contrast in the image.

Preparing For Data Processing

Create a workspace. Before we begin, we need to set up a clean workspace for us to be able to work from.

  1. Make a new project directory
    1. Navigate to the appropriate location on your machine to make a new directory
    2. Type mkdir dataset_AB to make a new directory called “dataset_AB”
    3. Type cd dataset_AB to move into the new directory
  2. Make a symbolic link to your downloaded data from within that directory
    1. Type ln -s /path/to/tutorial/data ./ to create a link to your data

Processing guide

Step 1: Data Pre-Processing

1. Create a frame series settings file

WarpTools create_settings \
--output warp_frameseries.settings \
--folder_processing warp_frameseries \
--folder_data data/ \
--extension "*.mrc" \
--angpix 3.28 \
--bin 0 \
--exposure 2.05

Special note: The provided mdoc file refers to the post-aligned stack of tiltseries images and is the original document deposited to EMPIAR by the dataset authors. However, the EMPIAR deposition states that the aligned stacks were binned by 2, which means the pixel size is actually half the value reported in the mdoc files.

This script will create a file called warp_frameseries.settings that will be stored in your project directory. This file is a type of XML metadata file that supplies WarpTools with the settings you provided.

In your script:

--output
The name of the settings file describing the frameseries. In this case, warp_frameseries.settings.
--folder_processing
The folder to store the frame series metadata files. This folder does not exist yet, but WarpTools will make one for you after you run this job.
--folder_data
The path to the raw data e.g. /path/to/your/data/. If you can, you can symbolically link the data folder to your working directory.
--extension
The file extension of your raw images. In this case, we have MRC files so the extension is "*.mrc".
--angpix
The raw unbinned calibrated pixel size of the data. You can find this value in the mdoc file, although as mentioned above, this dataset is a little special.
--bin
The binning factor by which you wish to bin the pixel size. We don’t want to bin the pixel size on a dataset this small and fast, so we have opted for a binning factor of 0.
--exposure
The per-tilt electron dose exposure. This value is recorded in the mdoc file under the ExposureDose column.

Time to run (run directly in the commandline): Nearly instant.

2. Correct motion and estimate CTF

WarpTools fs_motion \
--settings warp_frameseries.settings \
--grid 1x1x12 \
--averages

WarpTools fs_ctf \
--settings warp_frameseries.settings \
--voltage 300 \
--cs 2.7 \
--amplitude 0.1 \
--defocus_min 3.0 \
--defocus_max 8.0 \
--range_min 30.0 \
--range_max 7.0 \
--use_sum \
--grid 2x2x1

This script will run the motion correction and CTF estimation job in WarpTools and output summed motion corrected averages in a folder called /averages/ inside the /warp_frameseries/ directory. These summed averages are required for the subsequent steps.

In your script:

--settings
The name of the settings file describing the frameseries.
--grid
fs_motion: The patches along the X, Y and T (temporal) dimensions to use for motion correction. A patch size of 1 would encompass the entire field of view, so the first two values of 1 x 1 (x, y) take the whole frame as a single patch. The temporal dimension value refers to the frames available which can be used to track motion through time. This is equivalent to the number of subframes present in each frame series, because subframes are collected one at a time and therefore have a sequential, temporal nature to them. There are 12 subframes in each frame series of this dataset. If you’re unsure, you can also read the mdoc file of a dataset which records the number of subframes under NumSubFrames, or you can read the header of the image with IMOD using the header command.
--grid
fs_ctf: The patches along the X, Y and T (temporal) dimensions to use for 2D CTF estimation. The developers recommend splitting the motion-corrected summed average into 4 quadrants, so the X and Y patches should be 2. Since the motion-corrected averages are already summed by this time, there is only one frame available, so T should be 1.
--range_max
The maximum CTF fit to search for in angstroms. The developers recommend 7 as higher is likely to be prone to overfitting and lower is unlikely to be helpful. In our case, we would not be able to set this lower anyway because our pixel size is 3.8, meaning the Nyquist frequency is almost 6.7 (twice the pixel size).
--defocus_max
The maximum defocus to consider, in microns.
--use_sum
Use the summed average from the motion correction job.

Time to run (on 4 GPUs): ~5 minutes

3. Generate histograms depicting data quality

WarpTools filter_quality \
--settings warp_frameseries.settings \
--histograms

This script will print histograms to the terminal screen that will allow you to determine if the motion correction and CTF estimation completed as expected. It can be difficult to tell if the histograms are depicting something sensible, so a good rule of thumb is to look for a normal bell-shape distribution across the defocus. We know that we should expect a normal distribution because the sample was progressively tilted in the microscope. In our experience, if something has gone wrong at this stage, WarpTools tends to dump all frames into the last value of the histograms. Unlike in single-particle analysis, you are not able to assess Thon rings using the Linux version of WarpTools.

In your script:

--settings
The name of the settings file describing the frameseries.
--histograms
Compute and display the motion correction and CTF estimation job results as histograms which can be viewed in the terminal.

Time to run (run in the terminal): Nearly instant.

4. Import the tilt series

WarpTools ts_import \
--mdocs data/ \
--pattern "*mdoc" \
--frameseries warp_frameseries \
--tilt_exposure 2.05 \
--dont_invert \
--override_axis 85 \
--output tomostar

The frame series has now been motion corrected and summed into single frame micrographs, becoming a motion-corrected tilt series. WarpTools needs to import the single frame tilts using an mdoc file so that WarpTools can know what angle each summed tilt was imaged at. Mdoc files record the angle of each frame series, and since the tilt series have the same file name, WarpTools is able to determine the associated tilt angle.

In your script:

--mdocs
The absolute path to the mdoc file(s) associated with the data.
--pattern
The file extension for the mdoc file, in case they are not written out as .mdoc as they usually are. Some datasets do not come with mdoc files and the investigator has to use new tools to spoof mdoc files themselves (not recommended, it’s a pain).
--frameseries
The name of the folder where the frame series metadata is stored.
--tilt_exposure
The per-tilt exposure.
--dont_invert
Don’t invert the contrast of the image (if particles are black on a grey background, leave them black on a grey background). Black particles on a grey background are required for most template matching software titles, so if you intend to do template matching, you should not invert the tomogram contrast (unless you intend to use Dynamo).
--override_axis
Override the tilt axis angle written in the mdoc file. This is often necessary because the tilt axis angle in the mdoc file is frequently printed incorrectly by both Tomo5 and SerialEM.
--output
The name of the folder to store new metadata files related to the tilt series. These files are .tomostar files. This folder doesn’t exist yet, but WarpTools will make it for you after this job has been completed. (Here: tomostar.)

Time to run (run in the terminal): Nearly instant.

5. Create a tilt series settings file

WarpTools create_settings \
--output warp_tiltseries.settings \
--folder_processing warp_tiltseries \
--folder_data tomostar \
--extension "*.tomostar" \
--angpix 3.28 \
--bin 0 \
--exposure 2.05 \
--tomo_dimensions 5600x4200x2200

This script will create a settings file that defines the relevant parameters related to the tilt series. The settings are all the same. If you wanted to bin your pixel size, but you didn’t bin it from the start, now would be your chance to bin the pixel size to speed up processing. Tomostar files will be made for every tiltseries in the dataset and stored in the /tomostar/ folder in the working directory. When it comes time to reconstruct tomograms, WarpTools will fetch information about the tiltseries for reconstruction from the tomostar files.

In your script:

--output
The name of the settings file for the tilt series. In this case, it’ll be named warp_tiltseries.settings.
--folder_processing
The folder where you’d like to store the processing results related to the tilt series. WarpTools will make this folder for you.
--folder_data
The path to the tomostar folder.
--extension
The extension of the metadata files. The extension is "*.tomostar".
--angpix
The unbinned pixel size.
--bin
The pixel binning factor.
--exposure
The per-tilt electron dose.
--tomo_dimensions
The dimensions of the tomogram (should be set slightly larger than the dimensions of the camera).

Time to run (run in the terminal): Less than a minute.

6. Align the images using AreTomo3

WarpTools ts_aretomo3 \
--settings warp_tiltseries.settings \
--angpix 10 \
--patches 6,4 \
--axis 85

WarpTools has a wrapper for the alignment tool AreTomo3. This script will call AreTomo3 to compute the alignment shifts needed to create a smooth, jitter-free aligned series of tilts. Alignment files will be stored in /warp_tiltseries/tiltstack/ under a series of subdirectories with the tomoname label of each tiltseries in the dataset.

In your script:

--settings
The tilt series settings file.
--angpix
The pixel size to compute the alignments at. Computing at full resolution will take forever and will not improve the accuracy of the alignment. Usually, 10 is a good choice.
--patches
The number of patches to use for patch tracking. Too few patches and AreTomo3 will not be able to track shifts between tilts very well. Too many patches and AreTomo3 will take a long time.
--axis
The tilt axis angle to use for alignment.

Time to run (on 4 GPUs): ~5 minutes.

7. Check the defocus handedness

WarpTools ts_defocus_hand \
--settings warp_tiltseries.settings \
--check

This script will compute whether the defocus handedness of the data correlates with the expected CTF model. The result of this quick test will tell us if we need to change any settings related to the defocus handedness.

Time to run (run in the terminal): Nearly instant.

8. Set the defocus handedness settings

WarpTools ts_defocus_hand \
--settings warp_tiltseries.settings \
--set_noflip

This script will change our settings so that the defocus handedness (the sign value associated with the defocus) is not flipped.

Time to run (run in the terminal): Nearly instant.

9. Correct the CTF

WarpTools ts_ctf \
--settings warp_tiltseries.settings \
--defocus_min 3.0 --defocus_max 8.0 \
--range_low 30.0 --range_high 7.0 \
--voltage 300 --cs 2.7 --amplitude 0.1

This script performs 3D CTF correction using the 2D CTF estimation job for the frame series as an initial estimate. Here, we provide all the same values as last time.

In your script:

--settings
The tilt series settings file (not the frame series settings file).

All parameters are the same as in our previous CTF estimation job.

Time to run (run in the terminal): ~5 minutes

10. Reconstruct the tomogram

WarpTools ts_reconstruct \
--settings warp_tiltseries.settings \
--angpix 10.0 \
--dont_invert \
--deconv \
--deconv_strength 0.7 \
--deconv_falloff 0.7 \
--perdevice 2

This script will reconstruct the tomogram by direct Fourier-inversion using the alignment information from the AreTomo3 job and the settings stored in the tilt series settings file (tomogram dimensions, etc), and the tiltseries information in the tomostar files. It will output filtered and unfiltered tomograms in /warp_tiltseries/reconstruction/ and /warp_tiltseries/reconstruction/deconv/, respectively.

In your script:

--settings
The tilt series settings file.
--input_processing
The folder with the alignment files you wish to use.
--angpix
The pixel size to reconstruct the tomogram at. You will not want to reconstruct the tomogram at full resolution because it will take a long time to reconstruct and will be so low contrast, you are unlikely to be able to see anything. Usually, downstream processing software titles like IsoNet, TomoNet, MemBRAIN and others, were trained on tomograms with a pixel size of 10, so 10 is typically a good choice if you intend to use those tools later.
--deconv, --deconv_strength and --deconv_falloff
Whether to perform CTF deconvolution on the output tomograms in order to filter out high-frequency noise and improve contrast. This operation is performed by applying a Wiener-like filter to the data in order to attenuate spatial frequencies above the first zero in the CTF.
--dont_invert
Don’t invert the contrast of the tomogram.
--perdevice
How many processes to run on each GPU. If you only have 16GB of video RAM available for your GPU, then set this to 1. If you have 32 GB available, set this to 2. If you’re not familiar with the machine on your workstation, then stick to 1.

Time to run (run in the terminal): ~10 minutes

Step 2: Missing Wedge Correction with IsoNet 0.3

This step performs missing wedge correction using IsoNet. The effect of this procedure is to reverse some of the smearing effect in the tomograms along the Z-axis caused by the missing wedge of spatial frequencies in the Fourier transform of the tomogram. The missing wedge is caused by not completely imaging our specimens from all viewing directions, but rather, imaging only at a subset of discrete angles. In practice, without correcting the missing wedge, objects which are spherical (or in our case, icosahedral) become distorted relative to the Z-axis (see screenshot below). After missing wedge correction, our viral capsids will become more icosahedral as one would expect. However, it is important to maintain realistic expectations about what these missing wedge correction programs are able to achieve. In practice, these tools improve the corruption of the image caused by the missing wedge, but they do not remove the corruption completely.

Capsid contours of jumbo phage 7-1-1 without missing wedge correction
Figure 1. Capsid contours of jumbo phage 7-1-1 without missing wedge correction, looking along the y-axis (i.e. looking at the “side” of the capsid). This capsid was segmented from a tomogram prior to missing wedge correction in IMOD. As one can see, the contours are drawn every few slices. The capsid is very egg-shaped due to the effects of the missing wedge, when it should be much more icosahedral in reality.

Preliminary housekeeping

1. Set up a working directory

(This is optional, but it’s a good idea to keep results from different programs separated.)

Make a new directory:

mkdir isonet

Move into the directory:

cd isonet

2. Make a copy of the deconvolved version of tomogram grid1_phage711_006 in this directory

cp ../warp_tiltseries/reconstruction/deconv/grid1_phage711_006_10.00Apx.mrc .

This will copy the deconvolved tomogram (006) from the deconv folder into the current directory.

3. Rename the tomogram to remove the pixel size suffix

mv grid1_phage711_006_10.00Apx.mrc grid1_phage711_006_10_00Apx.mrc

The refine step in IsoNet is unable to parse tomogram names which have two dots in them (i.e. _10.00Apx.mrc). In fact, there are several cryoET tools which are not compatible with the standard naming conventions of tomograms produced in WarpTools. Luckily, the pixel size suffix is easy enough to rename. If you have a very large dataset, you may want to script a little Python script to manage renaming large numbers of tomograms.

4. Confirm renaming is successful

ls

Step 3: Manual Segmentation in 3DMOD

Segmentation is the process of delineating a structure within a tomogram to produce a binary volume. There are many automated segmentation tools available, like MemBRAIN-seg, TARDIS and Easymode. However, they can only segment things the neural networks were trained on. In many cases, when segmenting something niche, the only solution is to manually segment a structure because you may be researching a structure which a) does not belong to the limited number of things that segmentation tools were trained on, or b) is not being adequately segmented by those tools. In this case, phages are not included in these segmentation tool datasets. Further, the capsid fibers that bind to the flagella are long, thin and highly flexible.

In this module, we will take you through how to manually segment a structure in 3DMOD. Once you know how to do it, you will realize it is relatively straight forward and you should be able to segment literally anything in your own tomograms using 3DMOD (i.e. IMOD). As long as you (the human) can see the structure, you can segment it. For this tutorial, we will use 3DMOD to segment the phage capsids, tails, fibers and flagella. This tool is free, reliable and relatively simple. To view this module in action, we have made a YouTube video tutorial to pair with this written guide. (link)

Special note: Manual segmentation involves a lot of clicking and dragging over a prolonged period of time. We recommend regular rest breaks for your wrist, and if possible, an ergonomic mouse.

Concept: Create manual contour lines around objects in the tomogram to segment them. Contours can then be meshed to apply a skin over the top and viewed in ChimeraX as one would with an automated segmentation.

1. Opening your tomogram in 3DMOD

  • Step 1: First, make a new working directory to contain your 3DMOD files.
    mkdir segmentation
  • Step 2: Move into that folder.
    cd segmentation
  • Step 3: Launch 3DMod by opening one of your tomograms in 3DMOD.
    3dmod ../isonet/corrected_tomos/l40t05_5_10_00Apx_corrected.mrc

The tomogram will open with an info box and a ZAP window. To get started, we need to check that your mouse settings are correct.

3dmod mouse preferences
  • Step 1: Click on the Edit tab in the info window.
  • Step 2: In the Edit drop down menu, click on Options.
  • Step 3: In the 3dmod: Set Preferences window, select Mouse from the side menu.
  • Step 4: In the First, Second, Third Buttons menu, select Right, Left, Middle.
  • Step 5: Close the 3dmod: Set Preferences window.

Making sure that the mouse settings are on Right, Left, Middle is strictly so that your mouse settings match those in this instruction guide.

2. Setting up the contour settings

Next, we will edit the settings for our first “Object,” which represents the structure we will segment first. Each structure—the phage capsid, fibers, tail, and flagella—will be segmented as a separate “Object,” so a new object will be created for each structure later. For now, we will focus on Object 1, which is opened by default in 3DMOD.

3dmod Object Type settings
  • Step 1: Click the Edit tab.
  • Step 2: In the Edit drop down menu, click the Object option.
  • Step 3: In the Object drop down menu, click the Type option.
  • Step 4: In the Object Type box, we will give this Object a name. We will name it “capsid”. Each Object will receive a unique name (more on this later).
  • Step 5: In the Filled Contours In Zap setting, set a transparency level. Our contours will be filled with a colour that is slightly transparent. If set to 100%, you won’t see any fill colour. If set to 0%, the fill colour will be totally opaque and you won’t see the tomogram image behind the contour. Anywhere between 60 and 80% is usually fine. When segmenting something extremely dark, setting the transparency to lower number will help you be able to see contour better. When ready, click Set As Defaults at the bottom of the box.

3. Setting up the drawing tools

Next, we will open up the drawing tools we need to get started with drawing contours on slices of our tomogram. Once we have the tools set up, we will be ready to start segmenting.

3dmod Drawing Tools and Interpolator windows
  • Step 1: Click the Special tab.
  • Step 2: In the Special tab drop down menu, click the Drawing Tools option. A Drawing Tools dialogue box will appear.
  • Step 3: In the Special tab drop down menu, click the Interpolator option. An Interpolator dialogue box will appear.
  • Step 4: In the Interpolator dialogue box, make sure the Interpolation Type is set to Linear.
  • Step 5: In the Drawing Tools box, make sure that the Drawing Mode is set to Normal [1]. This can be changed later to make sure of the Sculpt tool, but for now, we will draw in Normal Mode.

4. Segmenting a structure

To begin segmenting, you may wish to first zoom in and center a virus in the center of the ZAP window. If you are having trouble distinguishing the boundaries between a structure and the background, it can be helpful to zoom in and zoom out and back in again to allow the human eye to determine edges.

3dmod ZAP window with phage centered
  • Step 1: Click the up arrow on the ZAP window to Zoom in. You can Zoom in as far as you like.
  • Step 2: Use the Z-slicer to slab through the height of the tomogram by dragging the bar to the left and right.
  • Step 3: Recenter a phage into the center of the ZAP window by clicking and dragging with the right mouse button.

To begin drawing, it’s always easiest to start segmenting from the center of the structure because it’s clearest. Since we are segmenting a capsid, we should slab through the tomogram along the Z (by using the Z slider at the top of the ZAP window) until we roughly locate the center of the capsid. We will then use our left mouse button, and while holding the button down, we will draw a line around the capsid edge.

Tracing carefully around the outside of the capsid, make sure not to fully close the contour by bringing the mouse slightly short of the starting position. If you close the contour, sometimes 3DMOD thinks you were trying to segment everything outside the lines instead of inside the lines. If you make a mistake, you can erase the contour with the ERASE tool in the Interpolator window.

Tracing a contour around the phage capsid
  • Step 4: Left click and hold to trace around the phage capsid.
  • Step 5: Continue all the way until just before where you started.
  • Step 6: Let go of the left mouse button.
  • Step 7: Tap the letter “V” on your keyboard. This will open the model window and will allow you to see your contour as a plain line. This will be helpful later.
  • Step 8: Tap on the PAGE UP or PAGE DOWN key on your keyboard to slab one slice up or down. Tap several times to slab several slices up or down.
  • Step 9: Draw a contour line every couple of slices or so. We will use the interpolator in the next step to fill in the slices we haven’t drawn on.
Interpolated contours in 3dmod model view
  • Step 10: Make sure the interpolator is set to Linear.
  • Step 11: Select a contour. You can do this by changing the mode in the Drawing Tools window to Sculpt and then gently nudging the edge of a contour with the Sculpt tool and click the left mouse button. The contour should have a small yellow circle which indicates that the contour has been selected.
  • Step 12: Tap the Enter or Return button on your keyboard.
  • Step 13: Check the model window. It should show a number of contours between this slice and the next segmented slice, in dashed line view. These contours have been interpolated.
  • Step 14: Page Up or Down to view the next slice. If you agree with the contour, tap Enter or Return. If you don’t, use the Sculpt tool to correct the contour.
  • Step 15: Continue in this manner until the structure has been segmented.

To segment another structure (i.e. the tail, or the flagella), you can create a new Object. You can create as many Objects as you’d like to segment. In theory, you can make them all at the start, and segment all the structures together on each slice as you move through the tomogram, but for the purposes of teaching you the simplest methods, we will create Objects one at a time here. To create a new Object:

  • Step 16: Click on the Edit tab of the Info Window.
  • Step 17: In the drop down menu for the Edit tab, click on the Object option.
  • Step 18: In the Object option, click on the New option.
  • Step 19: In the New Object box which options, name the new Object. You can name it “tail” if you intend to segment the tail, for example.
  • Step 20: When ready, close the tab.
  • Step 21: Ensure that the object type in the Info window is selected to Object 2.
  • Step 22: Return to Step 5.1 and continue until the latest object has been segmented.

Once you have enough contours drawn, you can place a mesh skin over the contour to view the model easier.

  • Step 23: In the 3dmod Model View window, click the Edit tab.
  • Step 24: In the drop down menu for the Edit tab, click the Objects option.
  • Step 25: In the Edit Objects menu that opens, make sure that Meshing is selected from the left hand option menu.
  • Step 26: Tick the CAP box.
  • Step 27: Click MESH ALL.
  • Step 28: Select the next Object at the top of the Edit Objects window and continue to click CAP and then MESH ALL.
Meshed objects in 3dmod model view

5. File conversion from .mod model to .mrc model

Next, we need to save the model file. We will save it as a .mod file, which IMODs default model file format. To view the .mod file in ChimeraX, we will need to convert it from .mod to .mrc.

To convert from .mod to .mrc, we will use a publicly available mod2mrc script on GitHub: https://github.com/seanhatton/mod2mrc

  • Step 1: In the terminal, and from within the project working directory, clone the github repo with the following command: git clone https://github.com/seanhatton/mod2mrc.git. This will download the script you need into a newly created folder called /mod2mrc/.
  • Step 2: Confirm that the clone worked by typing ls to ensure that the /mod2mrc/ folder is there.
  • Step 3: Copy both the tomogram and the .mod contour model into the newly created mod2mrc folder; cp manually_segmented_phage711.mod /mod2mrc/ followed by cp phage711.mrc /mod2mrc/.
  • Step 4: Move into the folder and confirm that everything was copied correctly; cd /mod2mrc/ followed by ls. You should see mod2mrc.bash, readme.txt and the files you copied.
  • Step 5: Open the script in a text editor and edit lines 7, 8 and 11 as follows:
    input_mrc="phage711.mrc"
    input_mod="manually_segmented_phage711.mod"
    object_list=(phage711_capsid tail capsid_fibers flagella)

    *Make sure there are no spaces in the object list name.

  • Step 6: Change the local permissions settings for the bash script so that we can run it, by typing: chmod +x mod2mrc.bash.
  • Step 7: Run the script by simply typing ./mod2mrc.bash.

Step 4: View Segmentations

To view segmentations and assess their quality, we can open them in UCSF ChimeraX. Since we have converted to an .mrc format, you can make figures using whatever your preferred rendering software tool is in the usual manner (including Blender and other 3D render applications). To open a segmentation:

chimerax phage711_capsid.mrc

When UCSF ChimeraX opens, it may load the segmentation as a plane. You will need to adjust the segmentation to be rendered in the Surface representation by clicking the render setting drop down box. You will also need to set the contour level to a value below 1. You can set the render steps to 1. View the YouTube video for more information.

Congratulations on processing the dataset to completion!

This is one way of many potential ways that a dataset of this nature could be processed. New cryoET tools are emerging all the time. You can visit sbgrid.org to view our most updated collection of software titles.

If you have any questions, please contact eruera@hkl.hms.harvard.edu with DATASET AB as the subject line.