Difference between revisions of "Multireference alignment"
Line 19: | Line 19: | ||
== Input format == | == Input format == | ||
− | Introducing project elements (template, tables) for MRA projects is slightly different than introducing them for single reference projects. You can use a .sel file, or pass a folder, where files need to stick to a given naming convention. | + | Introducing project elements (template, tables) for MRA projects is slightly different than introducing them for single reference projects. You can use a .sel file, or pass a folder, where individuals files need to stick to a given naming convention. Each reference number is given by a three figure zero padded integer starting with zero. |
<tt> | <tt> | ||
− | + | <folder seeds>/template_initial_ref_001.em | |
− | + | <folder seeds>/fmask_initial_ref_001.em | |
− | + | <folder seeds>/table_initial_ref_001.em | |
</tt> | </tt> | ||
+ | |||
+ | Here, <tt><folder seed></tt> is the name of a folder that can be passed to a project as parameter for <tt>template</tt> instead of the name of a file. Same holds for parameters <tt>table</tt> and {{t|fmask}}. You can use different folders for different parameters. | ||
===Tables=== | ===Tables=== | ||
Line 41: | Line 43: | ||
==== Random subset averaging ==== | ==== Random subset averaging ==== | ||
− | You can use an avialable table and data folder and construct averages taking N-different subsets of particles. This can be performed with | + | You can use an avialable table and data folder and construct averages taking N-different subsets of particles. This can be performed with an order leike: |
TBI | TBI | ||
<tt> | <tt> | ||
− | dynamo_write_multireference(myTable,'table', | + | dynamo_write_multireference(myTable,'table',myFolder,'refs',1:4,'data',myData,'subset',M/4); |
</tt> | </tt> | ||
+ | will create 4 subsets of particles each containing M/4 particles (''M'' being the number of valid particles in the table), produce 4 averages, store the files in {{t|myFolder}} and format the individual file names so as to follow the [[# Input format|appropriate convention]] | ||
== Output == | == Output == | ||
You will get a different [[refined table]] and [[iteration average]] for each reference channel and iteration. | You will get a different [[refined table]] and [[iteration average]] for each reference channel and iteration. |
Revision as of 11:25, 25 April 2016
In a multireference alignment [MRA] project, each particle will be aligned against R different templates. Multireference projects are mainly used to incarnate the Multireference analysis approach for simultaneous alignment and classification.
Contents
The process of multireference alignment
If you have R references and N particles, each particle will be aligned against all the R references. The particle will produce R different cross-correlation scores and R different sets of alignment pararameters. Thus, Dynamowill produce R different refinement tables, each for one reference channel.
Each particle will have a single reference yielding the maximal cc score.
Masks
The fact that you can define alignment masks and classification masks separately in a project is specially useful when running MRA projects. Very frequently, you want to use a wide mask that includes enough signal to drive the alignment, and a smaller mask, defined on the region where you expect or want to check for structural heterogeneity.
Input format
Introducing project elements (template, tables) for MRA projects is slightly different than introducing them for single reference projects. You can use a .sel file, or pass a folder, where individuals files need to stick to a given naming convention. Each reference number is given by a three figure zero padded integer starting with zero.
<folder seeds>/template_initial_ref_001.em <folder seeds>/fmask_initial_ref_001.em <folder seeds>/table_initial_ref_001.em
Here, <folder seed> is the name of a folder that can be passed to a project as parameter for template instead of the name of a file. Same holds for parameters table and fmask. You can use different folders for different parameters.
Tables
The dcp GUI gives you the option of just cloning a previously available table.
Initial templates
There are different policies for the creation of the first templates.
A priori information
In some circumstances, you can use geometrical shapes as initial templates to drive the classification.
Adding noise to a given map
The dcp GUI gives the option of using a template already available in the GUI and producing multiple copies by adding different realizations of gaussian noise of the same amplitude.
Random subset averaging
You can use an avialable table and data folder and construct averages taking N-different subsets of particles. This can be performed with an order leike:
TBI dynamo_write_multireference(myTable,'table',myFolder,'refs',1:4,'data',myData,'subset',M/4); will create 4 subsets of particles each containing M/4 particles (M being the number of valid particles in the table), produce 4 averages, store the files in myFolder and format the individual file names so as to follow the appropriate convention
Output
You will get a different refined table and iteration average for each reference channel and iteration.