Difference between revisions of "Particle extraction"
| Line 4: | Line 4: | ||
==Using the catalogue== | ==Using the catalogue== | ||
| − | Select the tomograms in which you have models containing particles and click on the menu tab ''Crop particles''. A new GUI will popup, with a list of models. You can then select the models that already contain ''crop points''). Then click on ''Create list''. This will | + | Select the tomograms in which you have models containing particles and click on the menu tab ''Crop particles''. A new GUI will popup, with a list of models. You can then select the models that already contain ''crop points''). Then click on ''Create list''. This will show you an automatically created [[volume list file]]. This is just for information, no need to do anything on it. Click then on ''-> Crop particles'', getting a GUI where you can select the sidelength in pixels, and start the actual cropping. |
| + | |||
| + | It will produce a [[data folder]] which will contain the cropped particles and two additional files | ||
| + | * a [[table]] file called <tt>crop.tbl</tt>. Column 20 assigns the particle to a particular tomogram in the [[volume list]]file. | ||
| + | * a doc file with the full name of each tomogram coded by an integer in column 20 of <tt>crop.tbl</tt> | ||
==From the command line== | ==From the command line== | ||
| − | + | In order to have a direct insight on how the cropping is performed, you can ignore the catalogue framework and just use the command line order <tt>dtcrop</tt> . | |
Help on command: [http://{{SERVERNAME}}/w/doc/functions/dynamo_table_crop.html dtcrop] | Help on command: [http://{{SERVERNAME}}/w/doc/functions/dynamo_table_crop.html dtcrop] | ||
==On a single tomogram== | ==On a single tomogram== | ||
| − | ==On several tomograms | + | |
| + | |||
| + | ==On several tomograms== | ||
| + | |||
| + | In this case, the first argument of <tt>dtcrop</tt> is the name of a [[volume list file]], the second is the code word <tt>reorder</tt>. | ||
==On each model separately== | ==On each model separately== | ||
When you are manually creating a model in one of the browsers, the real workflow in an actual project involving many tomograms and modeles would be to just click the necessary points to define the user input of the model, store it in the catalogue, and move to the next model. | When you are manually creating a model in one of the browsers, the real workflow in an actual project involving many tomograms and modeles would be to just click the necessary points to define the user input of the model, store it in the catalogue, and move to the next model. | ||
Revision as of 15:57, 21 March 2016
Particle extraction is the process of using a set of positions (and possibly orientations) defined on a set of tomograms to create a set of subtomograms files. This set is represented by a data folder containing one file for each cropped subtomogram, and possibly a table retaining the metadata. Data folder and table can directly be used for subtomogram alignment
Contents
Using the catalogue
Select the tomograms in which you have models containing particles and click on the menu tab Crop particles. A new GUI will popup, with a list of models. You can then select the models that already contain crop points). Then click on Create list. This will show you an automatically created volume list file. This is just for information, no need to do anything on it. Click then on -> Crop particles, getting a GUI where you can select the sidelength in pixels, and start the actual cropping.
It will produce a data folder which will contain the cropped particles and two additional files
- a table file called crop.tbl. Column 20 assigns the particle to a particular tomogram in the volume listfile.
- a doc file with the full name of each tomogram coded by an integer in column 20 of crop.tbl
From the command line
In order to have a direct insight on how the cropping is performed, you can ignore the catalogue framework and just use the command line order dtcrop . Help on command: dtcrop
On a single tomogram
On several tomograms
In this case, the first argument of dtcrop is the name of a volume list file, the second is the code word reorder.
On each model separately
When you are manually creating a model in one of the browsers, the real workflow in an actual project involving many tomograms and modeles would be to just click the necessary points to define the user input of the model, store it in the catalogue, and move to the next model.
