Difference between revisions of "Averaging of subtomograms"
| Line 7: | Line 7: | ||
== Through the command line == | == Through the command line == | ||
To operate manually averages of particles (given an available [[table|metadata]]), use the {{t|daverage}} command, or its GUI version {{t|dvarage_GUI}}. {{docfunction|dynamo_average|daverage}} | To operate manually averages of particles (given an available [[table|metadata]]), use the {{t|daverage}} command, or its GUI version {{t|dvarage_GUI}}. {{docfunction|dynamo_average|daverage}} | ||
| + | The most important flags are | ||
| + | * ''fcompensate'' : if tuned to 1, a fourier compensation step will be carried. | ||
| + | * ''fmin'' : minimum number of particles that need to contribute to a given Fourier component. | ||
| + | * ''' | ||
== Inside an alignment project == | == Inside an alignment project == | ||
| Line 13: | Line 17: | ||
There are different project parameters that can be used to modify the default behaviour of the {{t|daverage}} command used inside an alignment project. | There are different project parameters that can be used to modify the default behaviour of the {{t|daverage}} command used inside an alignment project. | ||
| + | *''fCompensationSmoothingMask'' | ||
| + | *''implicitRotationMask' | ||
| + | |||
| + | === Reproducing averaging steps of a project from the command line === | ||
| + | |||
| + | It is possible to apply onto a set of particles exactly the same averaging flags that were using during the runtime of a project using the command <tt>dpkproject.pipeline.genericInput2Average</tt>. | ||
| + | |||
| + | <tt >o = dpkproject.pipeline.genericInput2Average(vpr,myTable,'ite',ite); </tt> | ||
| + | |||
| + | Here, <tt>o</tt> would be the output of the <tt>daverage</tt> command as operated with the flags passed to it by in the project <tt>vpr</tt>. These flags can be obtained explicitely with a second left hand side: | ||
| + | |||
| + | <tt> [o,flags] = dpkproject.pipeline.genericInput2Average(vpr,myTable,'ite',ite); </tt> | ||
===Parallelism=== | ===Parallelism=== | ||
Revision as of 20:41, 3 December 2017
Averaging of subtomograms means applying an available set of alignment parameters onto a set of data particles and adding them together. Because of the missing wedge, a compensation in the Fourier space is operated during this step.
From the operative point of view, the particles are stored in a data folder, which are indexed by a table.
Contents
Through the command line
To operate manually averages of particles (given an available metadata), use the daverage command, or its GUI version dvarage_GUI. daverage The most important flags are
- fcompensate : if tuned to 1, a fourier compensation step will be carried.
- fmin : minimum number of particles that need to contribute to a given Fourier component.
Inside an alignment project
At the end of each iteration, the refined table generated by Dynamo is used to produce an average, which will be used as starting template in the next iteration.
There are different project parameters that can be used to modify the default behaviour of the daverage command used inside an alignment project.
- fCompensationSmoothingMask
- implicitRotationMask'
Reproducing averaging steps of a project from the command line
It is possible to apply onto a set of particles exactly the same averaging flags that were using during the runtime of a project using the command dpkproject.pipeline.genericInput2Average.
o = dpkproject.pipeline.genericInput2Average(vpr,myTable,'ite',ite);
Here, o would be the output of the daverage command as operated with the flags passed to it by in the project vpr. These flags can be obtained explicitely with a second left hand side:
[o,flags] = dpkproject.pipeline.genericInput2Average(vpr,myTable,'ite',ite);
Parallelism
It is possible to select the number of cores that will be used during the averaging. The project parameter is called matlab_workers_average (shortform mwa), and can be modified also in dcp GUI (in the section of environment variables).
This option is available for computations on a single server with several cores. It will not work for the current MPI implementation.
