Averaging of subtomograms
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.
Through the command line
o = daverage( data,'t',table);
in Matlab-like syntax, or
o = daverage(data,'t',table);
in Linux-like syntax. In both cases, o is an output structure which includes as flags:
- 'average_raw': the average of the particles, without any Fourier compensation.
- 'fweight': count of contributions for each Fourier coefficient.
- 'average': 'average_raw' compensated through 'fweight'.
The most important additional flags are:
- 'nmask': if a mask is provided and the norm flag is tuned to 1 (as it is by default), each particle will be normalized to have zero mean and standard deviation 1 inside this mask before adding it to the average.
- default value is empty (no normalization).
- 'implicitRotationMasking'. If tuned to 1, the contribution of the particle outside an interior sphere will be discarded to minimize rotation artifacts
- default value is 1.
Fourier compensation flags
- 'fcompensate' : if tuned to 1, a Fourier compensation step will be carried out.
default value is zero. No missing wedge compensation.
- 'fmin' : minimum number of particles that need to contribute to a given Fourier component.
- 'fminFraction : if switched to a value between 0 and 1, selects the minimum fraction of particles that should contribute to a fourier component to admit it during averaging.
- default: empty. Elimination of underrepresented fourier components is driven by the value of parameter 'fmin'.
Smooth masking for Fourier compensation
This family of flags is provided for fine tuning of the behaviour of the Fourier compensation: they drive the imposition of a mask on the raw average before computing its Fourier transform for division with the 'fweight'. Note that with the default values of the parameters, this step is not operated.
- 'fCompensationSmoothingMask'. If a file or cube is matrix, the raw average will be multiplied with this mask before Fourier compensation.
- default: no mask.
- 'fCompensationSmoothingRadius'. if a non-zero value is passed, it will generate a spherical mask that will be imposed onto the raw average.
- default: 0, no spherical mask.
- 'fCompensationSmoothingDecay'. If a spherical mask is used (i.e., if 'fCompensationSmoothingRadius' is not zero), this sphere will have a smooth gaussian decay of 'fCompensationSmoothingDecay' pixels from 1 to 0.
- default value: 4 pixels.
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.
By default, the project will use the alignment mask of the project as normalization mask during averaging (i.e., 'nmask' flag inside the internally executed 'daverage' command).
There are different project parameters that can be used to modify the default behaviour of the daverage command used inside an alignment project.
default value is zero: this will introduce sharp edges contributing to the average, but will allow checking the features outside of the spherical mask.
default value is -1: use all Fourier coefficients during missing wedge compensation.
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,'justFlags',1);
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.