Refine Reconstruction » History » Version 21
Sargis Dallakyan, 11/26/2019 05:34 PM
1 | 1 | Anke Mulder | h1. Refine Reconstruction |
---|---|---|---|
2 | |||
3 | 12 | Dmitry Lyumkis | Most initial models establish nothing more than a preliminary sense of the overall shape of the biological specimen. In order to reveal structural information that can answer specific biological questions, the model requires refining. In single particle analysis, a refinement is an iterative procedure, which sequentially aligns the raw particles, assign to them appropriate spatial orientations (Euler angles) by comparing them against the a model, and then back-projects them into 3D space to form a new model. Effectively, a full refinement takes as input a raw particle stack and an initial model and is usually carried out until no further improvement of the structure can be observed, often measured by convergence to some resolution criterion. |
4 | |||
5 | 17 | Amber Herold | |
6 | |||
7 | h2. Refinement Options Available in Appion: |
||
8 | |||
9 | # [[EMAN_Refinement|EMAN Refinement]] |
||
10 | # [[Frealign_Refinement|Frealign Refinement]] |
||
11 | # [[SPIDER_Refinement|SPIDER Refinement]] |
||
12 | # [[IMAGIC_Refinement|IMAGIC Refinement]] |
||
13 | # [[Refinement Post-processing Procedures]] |
||
14 | |||
15 | h2. Appion Sidebar Snapshot: |
||
16 | |||
17 | 21 | Sargis Dallakyan | !Picture_88.png! |
18 | 17 | Amber Herold | |
19 | h2. Notes, Comments, and Suggestions: |
||
20 | |||
21 | h3. Icosohedral conventions |
||
22 | |||
23 | 16 | David Veesler | When dealing with icosahedral particles such as viral capsids, particular attention should be given to properly orient the model (the icosahedral axes) to match specific conventions adopted by different softwares. |
24 | |||
25 | 18 | Amber Herold | * Models downloaded from ViperDB (http://viperdb.scripps.edu/) will always be orientated in the Viper convention with the icosahedral 2-fold axes aligned along the Cartesian x,y,z axes and when the positive z axis points toward the viewer: |
26 | ** in the zx plan (2352): we first hit a 3-fold and then a 5-fold icosahedral axes |
||
27 | ** in the zy plan (2532): we first hit a 5-fold and then a 3-fold icosahedral axes |
||
28 | |
||
29 | * Another frequently encountered icosahedral convention is the so-called Crowther convention in which the icosahedral 2-fold axes are aligned along the Cartesian x,y,z axes and when the positive z axis points toward the viewer: |
||
30 | ** in the zx plan (2532): we first hit a 5-fold and then a 3-fold icosahedral axes |
||
31 | ** in the zy plan (2352): we first hit a 3-fold and then a 5-fold icosahedral axes |
||
32 | |
||
33 | 16 | David Veesler | The Crowther orientation is related to the Viper one by a simple rotation of 90° along the z-axis and one can switch from Viper to Crowther using proc3d (EMAN) with the following command: |
34 | 18 | Amber Herold | <pre> |
35 | 16 | David Veesler | proc3d model_Viper.mrc model_Crowther.mrc rot=0,0,90 |
36 | 18 | Amber Herold | </pre> |
37 | * A third convention may be termed EMAN convention as it is the one required by this package. It places an icosahedral 5-fold axis along the z axis, a 2-fold axis along y and a 3-fold axis close to x when looking down the z axis. |
||
38 | 16 | David Veesler | |
39 | To convert a model from the Crowther orientation to the EMAN one, the following proc3d command is required: |
||
40 | 18 | Amber Herold | <pre> |
41 | 19 | David Veesler | proc3d model_Crowther.mrc model_EMAN.mrc icos2fTo5f |
42 | 18 | Amber Herold | </pre> |
43 | 16 | David Veesler | Please note that a box can be checked when importing a model within appion to allow converting from Viper to EMAN orientation. |
44 | |||
45 | 1 | Anke Mulder | To assess visually in which orientation a model is, the simplest way is to do it in UCSF Chimera. After opening the map, press the Orient button in the Volume viewer to orient the z axis perpendicularly to the screen. Then open a file (named axis.bild for example) containing the following lines: |
46 | 17 | Amber Herold | <pre> |
47 | 16 | David Veesler | .color red |
48 | |||
49 | .cylinder 500.0 0.0 0.0 -500.0 0.0 0.0 1 |
||
50 | 1 | Anke Mulder | |
51 | 16 | David Veesler | .color green |
52 | |||
53 | .cylinder 0.0 500.0 0.0 0.0 -500.0 0.0 1 |
||
54 | |||
55 | .color blue |
||
56 | |||
57 | 1 | Anke Mulder | .cylinder 0.0 0.0 500.0 0.0 0.0 -500.0 1” |
58 | 16 | David Veesler | </pre> |
59 | 17 | Amber Herold | This file will display the Cartesian axes x (red), y (green) and z (blue). |
60 | 16 | David Veesler | |
61 | 20 | David Veesler | Below are the conventions used by the different softwares present within appion to generate and refine reconstructions (most allow to use different conventions). |
62 | 1 | Anke Mulder | |
63 | 18 | Amber Herold | * *XMIPP* |
64 | ** I1 (Viper convention) |
||
65 | ** I2 or I (Crowther convention) |
||
66 | ** I3: alternative 52 (as given by spider), 5fold axis in z and 2-fold in y. With the positive z-axis pointing at the viewer and without taken into account the 5-fold vertex in z, there is one of the front-most 5-fold vertices in -xz plane. |
||
67 | ** I4 another 52 with the positive z-axis pointing at the viewer and without taken into account the 5-fold vertices in z, there is one of the front-most 5-fold vertices in +xz plane. |
||
68 | ** I5 alternative 52 (used by EMBL-matfb). |
||
69 | |
||
70 | * *FREALIGN* |
||
71 | ** I1 (Viper convention) |
||
72 | ** I2 (Crowther convention) |
||
73 | |
||
74 | * *EMAN* |
||
75 | ** Only uses the EMAN convention. |
||
76 | 6 | Anke Mulder | |
77 | |||
78 | 21 | Sargis Dallakyan | !Picture_83.png! |
79 | !Picture_81.png! |
||
80 | 15 | Amber Herold | |
81 | |||
82 | [[Reconstruction Parameters]] |
||
83 | |||
84 | 3 | Anke Mulder | ______ |
85 | |||
86 | 10 | Anke Mulder | [[Ab Initio Reconstruction|< Ab Initio Reconstruction]]|[[Quality_Assessment|Quality Assessment >]] |
87 | 3 | Anke Mulder | |
88 | ______ |