View source for Molecular Replacement

<div style="margin-left: 25px; float: right;">__TOC__</div>

Phaser should be able to solve most structures with the Automated Molecular Replacement mode, and this is the first mode that you should try.  Give Phaser your data ([[#How to Define Data|How to Define Data]]) and your models ([[#How to Define Models|How to Define Models]]), tell Phaser what to search for, and a list of possible spacegroups (in the same point group).

If this doesn't work (see [[#Has Phaser Solved It?| Has Phaser Solved It?]]), you can try selecting peaks of lower significance in the rotation function in case the real orientation was not within the selection criteria. By default peaks above 75% of the top peak are selected (see [[#How to Select Peaks| How to Select Peaks]]). See [[#What to do in Difficult Cases| What to do in Difficult Cases]] for more hints and tips. If the automated molecular replacement mode doesn't work even with non-default input you need to run the modes of Phaser separately. The possibilities are endless - you can even try exhaustive searches (translations of all orientations) if you want - but experience has shown that most structures that can be solved by Phaser can be solved by relatively simple strategies.

==Automated Molecular Replacement==
Example Keyword Script: [[Phaser-2.2: Keyword Example Scripts#Automated Molecular Replacement| Automated Molecular Replacement]]

Example Python Script: [[Phaser-2.2: Python Example Scripts#Automated Molecular Replacement| Automated Molecular Replacement]]

Automated Molecular Replacement combines the anisotropy correction, likelihood enhanced fast rotation function, likelihood enhanced fast translation function, packing and refinement modes for multiple search models and a set of possible spacegroups to automatically solve a structure by molecular replacement. Top solutions are output to the files FILEROOT.sol, FILEROOT.#.mtz and FILEROOT.#.pdb (where "#" refers to the sorted solution number, 1 being the best, and only 1 is output by default). Many structures can be solved by running an automated molecular replacement search with defaults, giving the ensembles that you expect to be easiest to find first.



[[Image:Phaser_MR_auto.gif|thumb|100px|none|Flow Diagram for Automated MR]]

==Has Phaser Solved It?==
{| class="wikitable" style="text-align:center" align="right"
|-
! TF Z-score !! Have I solved it?
|-
| less than 5 || no
|-
| 5 - 6 || unlikely
|-
| 6 - 7 || possibly
|-
| 7 - 8  || probably
|-
| more than 8 ||definitely
|} 
Ideally, only the number of solutions you are expecting should be found.  However if the signal-to-noise of your search is low, there will be noise peaks in the final selection also.    Signal-to-noise is judged using the Z-score, which is computed by comparing the LLG values from the rotation or translation search with LLG values for a set of random rotations or translations. The mean and the RMS deviation from the mean are computed from the random set, then the Z-score for a search peak is defined as its LLG minus the mean, all divided by the RMS deviation, ''i.e. ''the number of  standard deviations above the mean. 

A highly compact summary of the history of a solution is given in the annotation of a solution in the .sol file.  This is a good place to start your analysis of the output. The annotation gives the Z-score of the solution at each rotation and translation function, the number of clashes in the packing, and the refined LLG. You should see the TFZ (the translation function Z-score) is high at least for the final components of the solution, and that the LLG (log-likelihood gain) increases as each component of the solution is added. For example, in the case of beta-blip the annotation for the single solution output in the .sol file shows these features

  SOLU SET RFZ=11.0 TFZ=22.6 PAK=0 LLG=434 RFZ=6.2 TFZ=28.9 PAK=0 LLG=986 LLG=986
  SOLU 6DIM ENSE beta EULER  200.920   41.240  183.776 FRAC -0.49641 -0.15752 -0.28125
  SOLU 6DIM ENSE blip EULER   43.873   80.949  117.141 FRAC -0.12290  0.29306 -0.09193

For a rotation function, the correct solution may be in the list with a Z-score under 4, and will not be found until a translation function is performed and picks out the correct solution.

For a translation function the correct solution will generally have a Z-score (number of standard deviations above the mean value) over 5 and be well separated from the rest of the solutions.  Of course, there will always be exceptions! The following table gives a very rough guide to interpreting TF Z-scores.
     
Note, in particular, that in the presence of translational NCS, pairs of similarly-oriented molecules separated by the correct translation vector will give large Z-scores, even if they are incorrect, because they explain the systematic variation in intensities caused by the translational NCS. On the other hand, we have noticed that in the search for the first molecule in polar space groups (''e.g.'' monoclinic space groups like P2<sub>1</sub>, or space groups with one rotation axis like P4<sub>3</sub>), where the translation search covers only a plane, the TF Z-score for correct solutions can be low.

You should always at least glance through the summary of the logfile. One thing to look for, in particular, is whether any translation solutions with a high Z-score have been rejected by the packing step. By default up to 10 clashes are allowed. Such a solution may be correct, and the clashes may arise only because of differences in small surface loops.  If this happens, repeat the run allowing a suitable number of clashes.  Note that, unless there is specific evidence in the logfile that a high TF-function Z-score solution is being rejected with a few clashes, it is much better to edit the model to remove the loops than to increase the number of allowed clashes. Packing criteria are a very powerful constraint on the translation function, and increasing the number of allowed clashes beyond the default will increase the search time enormously without the possibility of generating any correct solutions that would not have otherwise been found.

==What to do in Difficult Cases==

Not every structure can be solved by molecular replacement, but the right strategy can push the limits. What to do when the default jobs fail depends on why your structure is difficult.
*'''Flexible Structure'''
*:The relative orientations of the domains may be different in your crystal than in the model. If that may be the case, break the model into separate PDB files containing rigid-body units, enter these as separate ensembles, and search for them separately. If you find a convincing solution for one domain, but fail to find a solution for the next domain, you can take advantage of the knowledge that its orientation is likely to be similar to that of the first domain. The ROTAte&nbsp;AROUnd option of the brute rotation search can be used to restrict the search to orientations within, say, 30 degrees of that of the known domain. Allow for close approach of the domains by increasing the allowed clashes with the PACK keyword by, say, 1 for each domain break that you introduce.  Alternatively, you could try generating a series of models perturbed by normal modes, with the NMAPdb keyword. One of these may duplicate the hinge motion and provide a good single model.
*'''Poor or Incomplete Model'''
*:Signal-to-noise is reduced by coordinate errors or incompleteness of the model. Since the rotation search has lower signal to begin with than the translation search, it is usually more severely affected. For this reason, it can be very useful to use the subsequent translation search as a way to choose among many (say 1000) orientations. Try increasing the number of clustered orientations in an AUTO job using the keyword FINAL, ''e.g''.  FINAL&nbsp;ROT&nbsp;SELEct&nbsp;PERCent&nbsp;65.  If that fails, try turning off the clustering feature in the save step (FINAL&nbsp;ROT&nbsp;STEP 2 CLUSter&nbsp;OFF), because the correct orientation may sit on the shoulder of a peak in the rotation function.  
*:As shown convincingly by Schwarzenbacher ''et al.'' (Schwarzenbacher, Godzik, Grzechnik &amp; Jaroszewski, ''Acta Cryst.'' D'''60''', 1229-1236, 2004), judicious editing can make a significant difference in the quality of a distant model. In a number of tests with their data on models below 30% sequence identity, we have found that Phaser works best with a "mixed model" (non-identical sidechains longer than Ser replaced by Ser).  In agreement with their results, the best models are generally derived using more sophisticated alignment protocols, such as their FFAS protocol.
*'''High Degree of Non-crystallographic Symmetry'''
*:If there are clear peaks in the self-rotation function, you can expect orientations to be related by this known NCS. Methods to automatically use such information will be implemented in a future version of Phaser. In the meantime, you can work out for yourself the orientations that would be consistent with NCS and use the  ROTAte&nbsp;AROUnd option to sample similar orientations. Alternatively, you may have an oligomeric model and expect similar NCS in the crystal. First search with the oligomeric model; if this fails, search with a monomer. If that succeeds, you can again use the ROTAte&nbsp;AROUnd option to force a subsequent monomer to adopt an orientation similar to the one you expect.
*'''Pseudo-translational Non-crystallographic Symmetry'''
*:It is frequently the case that crystallographic and non-crystallographic rotational symmetry axes are parallel. The combination generates translational NCS, in which more than one unique copy of the molecule is found in the same orientation in the crystal. This can be recognized by the presence of large non-origin peaks in the native Patterson map. If one copy of the search model can be found, then the translational NCS tells you where to place another copy. Unfortunately, the presence of translational NCS can make it difficult to solve a structure using Phaser, because the current likelihood targets do not account for the statistical effects of NCS. If there is a small difference in the orientation of the two molecules (which will show up as a reduction in the height of the non-origin Patterson peak as the resolution is increased), it may help to use data to higher resolution than the default, because the translational NCS is partially broken.
*'''What <u>not</u> to do'''
*:The automated mode of Phaser is fast when Phaser finds a high Z-score solution to your problem. When Phaser cannot find a solution with a significant Z-score, it "thrashes", meaning it maintains a list of 100-1000's of low Z-score potential solutions and tries to improve them. This can lead to exceptionally long Phaser runs (over a week of CPU time). Such runs are possible because the highly automated script allows many consecutive MR jobs to be run without you having to manually set 100-1000's of jobs running and keep track of the results.  "Thrashing" generally does not produce a solution: solutions generally appear relatively quickly or not at all. It is more useful to go back and analyse your models and your data to see where improvements can be made. Your system manager will appreciate you terminating these jobs.
*:It is also not a good idea to effectively remove the packing test.  Unless there is specific evidence in the logfile that a high TF-function Z-score solution is being rejected with a few clashes, it is much better to edit the model to remove the loops than to increase the number of allowed clashes. Packing criteria are a very powerful constraint on the translation function, and increasing the number of allowed clashes beyond a few (e.g. 1-5) will increase the search time enormously without the possibility of generating any correct solutions that would not have otherwise been found.
*'''Other suggestions'''
*:Phaser has powerful input, output and scripting facilities that allow a large number of possibilities for altering default behaviour and forcing Phaser to do what you think it should. However, you will need to read the information in the manual below to take advantage of these facilities!

==How to Define Data==
You need to tell Phaser the name of the mtz file containing your data and the columns in the mtz file to be used using the HKLIn and LABIn keywords. Additional keywords (BINS CELL OUTLier RESOlution SPACegroup) define how the data are used.

==How to Define Models==
Phaser must be given the models that it will use for molecular replacement. A model in Phaser is referred to as an "ensemble", even when it is described by a single file. This is because it is possible to provide a set of aligned structures as an ensemble, from which a statistically-weighted averaged model is calculated. A molecular replacement model is provided either as one or more aligned pdb files, or as an electron density map, entered as structure factors in an mtz file. Each ensemble is treated as a separate type of rigid body to be placed in the molecular replacement solution. An ensemble should only be defined once, even if there are several copies of the molecule in the asymmetric unit.

Fundamental to the way in which Phaser uses MR models (either from coordinates or maps) is to estimate how the accuracy of the model falls off as a function of resolution, represented by the Sigma(A) curve.  To generate the Sigma(A) curve, Phaser needs to know the RMS coordinate error expected for the model and the fraction of the scattering power in the asymmetric unit that this model contributes.

If fp is the fraction scattering and RMS is the rms coordinate error, then<br>
<math>\sigma_A = \sqrt{f_p*[1-f_{sol}*e^{-B_{sol}*(sin\theta/\lambda)^2}]}* e^{-(8\pi ^2/3)*RMS^2*(sin\theta/\lambda)^2}</math><br>
where <math>f_{sol}</math>(default=0.95) and <math>B_{sol}</math>(default=300Å<sup>2</sup>) account for the effects of disordered solvent on the completeness of the model at low resolution.


Molecular replacement models are defined with the ENSEmble keyword and the COMPosition keyword.  The ENSEmble keyword gives (amongst other things) the  RMS deviation for the Sigma(A) curve.  The COMPosition keyword is used to deduce the fraction of the scattering power in the asymmetric unit that each ensemble contributes. The composition of the asymmetric unit is defined either by entering the molecular weights or sequences of the components in the asymmetric unit, and giving the number of copies of each. Expert users can also enter the fraction of the scattering of each component directly, although the composition must still be entered for the absolute scale calculation. Please note that the composition supplied to Phaser has to include everything in the asymmetric unit, not just what is being looked for in the current search!

===Building an Ensemble from Coordinates===
Example Scripts: [[Phaser-2.2: Keyword Example Scripts#Building an Ensemble from Coordinates | Building an Ensemble from Coordinates]]

The RMS deviation is determined directly from RMS or indirectly from IDENtity in the ENSEmble
keyword using the formula
 
RMS= max(0.8,0.4*exp(1.87*(1.0-ID)))

where ID is the fraction identity.

{| class="wikitable" style="text-align:center" align=right
|-
! Sequence ID !! RMS deviation
|-
| 100% || 0.80Å
|-
| 64% || 0.80Å
|-
| 63% || 0.799Å
|-
| 50%  || 1.02Å
|-
| 40% || 1.23Å
|-
| 30% || 1.48Å
|-
| 20% || 1.78Å
|-
| --&gt; limit 0% || 2.60Å
|} 

The RMS deviation estimated from ID may be an underestimate of the true value if there is a slight conformational change between the model and target structures. To find a solution in these cases it may be necessary to increase the RMS from the default value generated from the ID, by say 0.5 Ångstroms. On the other hand, when Phaser succeeds in solving a structure from a model with sequence identity much below 30%, it is often found that the fold is preserved better than the average for that level of sequence identity. So it may be worth submitting a run in which the RMS error is set at, say, 1.5, even if the sequence identity is low. The table below can be used as a guide as to the default RMS value corresponding to ID.

If you construct a model by homology modelling, remember that the RMS error you expect is essentially the error you expect from the template structure (if not worse!).  So specify the sequence identity of the template, not of the homology model.

Only the model with the highest sequence identity is reported in the output pdb file. Also, HETATM cards in the input pdb file are ignored in the calculation of the structure factors for the ensemble, but are carried through to the output pdb file. Thus, the phases on the output mtz file (which come from the structure factors of the ensemble) do not correspond to those that would be calculated from the output pdb file, when there is more than one pdb file in an ensemble and/or the pdbfile(s) have HETATM records.

===Building an Ensemble from Electron Density===
Example Scripts: [[Phaser-2.2: Keyword Example Scripts#Building an Ensemble from a Map | Building an Ensemble from a Map]]

When using density as a model, it is necessary to specify both the extent (x,y,z limits) of the cut-out region of density, and the centre of this region. With coordinates, Phaser can work this out by itself. This information is needed, for instance, to decide how large rotational steps can be in the rotation search and to carry out the molecular transform interpolation correctly. In the case of electron density, the RMS value does not have the same physical meaning that it has when the model is specified by atomic coordinates, but it is used to judge how the accuracy of the calculated structure factors drops off with resolution. A suitable value for RMS can be obtained, in the case of density from an experimentally-phased map, by choosing a value that makes the SigmaA curve fall off with resolution similarly to the mean figures-of-merit. In the case of density from an EM image reconstruction, the RMS value should make the SigmaA curve fall off similarly to a Fourier correlation curve used to judge the resolution of the EM image.

For detailed information, including a tutorial with example scripts, see
[[Using Electron Density as a Model| Using density as a model]]

==How to Define Composition==
The composition defines the total amount of protein and nucleic acid that you have in the asymmetric unit not the fraction of the asymmetric unit that you are searching for.

===Default Composition===
For convenience, the composition defaults to 50% protein scattering by volume (the average for protein crystals). It is better to enter it explicitly, even if only to check that you have correctly deduced the probable content of your crystal. If your crystal has higher or lower solvent content than this, or contains nucleic acid, then the composition should be entered explicitly.
===Composition by Solvent Content===
Scattering is determined from the solvent content of the crystal, assuming that the crystal contains protein only, and the average distribution of amino acids in protein. If your crystal contains nucleic acid or your protein has an unusual amino acid distribution then the composition should be entered explicitly using the MW or sequence options.
===Composition by Number of Residues in ASU===
Scattering is determined from the number of residues in the asymmetric unit, assuming that the crystal contains protein only or nucleic acid only, and assuming an average distribution of residues for either. If your crystal contains a mixture then the composition should be entered explicitly using the MW or sequence options.  If your crystal has an unusual residue distribution then the composition should be entered explicitly using the sequence options.
===Composition by Molecular Weight===
The composition is calculated from the molecular weight of the protein and nucleic acid assuming the protein and nucleic acid have the average distribution of amino acids and bases. If your protein or nucleic acid has an unusual amino acid or base distribution the composition should be entered by sequence. You can mix compositions entered by molecular weight with those entered by sequence.
===Composition by Sequence===
The composition is calculated from the amino acid sequence of the protein and the base sequence of the nucleic acid in fasta format. You can mix compositions entered by molecular weight with those entered by sequence. Individual atoms can be added to the composition with the COMPOSITION ATOM keyword. This allows the explicit addition of heavy atoms in the structure e.g. Fe atoms.
===Composition by Percentage Scattering===
The fraction scattering of each ensemble can be entered directly.  The fraction scattering of each ensemble is normally automatically worked out from the average scattering from each ensemble (calculated from the pdb files if entered as coordinates, or from the protein and nucleic acid molecular weights if entered as a map) divided by the total scattering given by the composition, but entering the fraction scattering directly overrides this calculation. This option is for use when the pdb files of the models in the ensemble are unusual e.g.  consist only of C-alpha atoms, or only of hydrogen atoms (as in the CLOUDS method for NMR).

==How to Define Solutions==
Phaser writes out files ending in ".sol" and ".rlist" that contain the solution information from the job. The root of the files is given by the ROOT keyword. By default, the root filename is PHASER. These files can be read back into subsequent runs of Phaser to build up solutions containing more than one molecule in the asymmetric unit.

"PHASER.sol"  files are generated by all modes (rotation function modes with VERBOSE output), and contain the current idea of potential molecular replacement solutions.

"PHASER.rlist"  files are generated by the rotation function modes, and are used as input for performing translation functions. (They are also produced by degenerate (2D) translation functions, for performing a translation function to find the third dimension)

For simple MR cases you don't really need to know how to define molecular replacement solutions.  However, for difficult cases you might need to edit the files "PHASER.sol" and "PHASER.rlist" files manually

=== "sol" Files===
At different stages of molecular replacement, an Ensemble will be oriented but not positioned (after the rotation search), or oriented and positioned (after the translation search), or, rarely, oriented and the position in 2 of 3 dimensions known. These three states correspond to solutions defined by the keywords SOLUtion 3DIM, SOLUtion 6DIM, and SOLUtion 5DIM. Each Ensemble in the asymmetric unit has its own SOLUtion keyword. Solutions of the type 3DIM are given by the rotation function, solutions of the type 6DIM are given by the translation function, and solutions of the type 5DIM are given by the degenerate translation function.

When more than one (potential) molecular replacement solution is present, the solutions are separated with the SOLUTION SET keywords.

==="rlist" Files===
These files define a rotation function list. The peak list is given with a series of SOLUtion TRIAl keywords.

If a partial solution is already known, then the information for the currently "known" parts of the asymmetric unit is given in the form used for the PHASER.sol file, followed by the list of trial orientations for which a translation function is to be performed.

If a degenerate translation function is performed, then a SOLUtion TRIAl line is produced with the degenerate translation information present, ready for performing the translation function on the third dimension.

===Fixed partial structure===
If you have the coordinates of a partial solution with the pdb coordinates of the known structure in the correct orientation and position, then you can force Phaser to use these coordinates. Use the SOLUTION keyword to fix a rotation of 0 0 0 and a position of 0 0 0 for these coordinates.

==How to Select Peaks==



The selection of peaks saved for output in the rotation and translation functions can be done in four different ways.
*'''Select by Percentage'''
*: Percentage of the top peak, where the value of the top peak is defined as 100% and the value of the mean is defined as 0%.
*: Default, cutoff=75%. This criteria has the advantange that at least one peak (the top peak) always survives the selection. If the top solution is clear, then only the one solution will be output, but if the distribution of peaks is rather flat, then many peaks will be output for testing in the next part of the MR procedure (e.g. many peaks selected from the rotation function for testing with a translation function).   
*'''Select by Z-score'''
*: Number of standard deviations (sigmas) over the mean (the Z-score). 
*: Absolute significance test. Not all searches will produce output if the cutoff value is too high (e.g. 5 sigma).   
*'''Select by Number'''
*: Number of top peaks to select. 
*: If the distribution is very flat then it might be better to select a fixed large number (e.g. 1000) of top rotation peaks for testing in the translation function.
*'''No selection'''
*: All peaks are selected. 
*: Enables full 6 dimensional searches, where all the solutions from the rotation function are output for testing in the translation function. This should never be necessary; it would be much faster and probably just as likely to work if the top 1000 peaks were used in this way.

[[Image:Phaser_selection.gif |thumb|100px|none|  Selection criteria]]

See [[Expert Peak Selection]] for more information about how to select peaks

==How to Control Output==
The output of Phaser can be controlled with optional keywords. 

The ROOT keyword is not compulsory (the default root filename is "PHASER"), but should always be given, so that your jobs have separate and meaningful output filenames.

The TOPFiles keyword controls the number of potential MR solutions for which PDB and (in the appropriate modes) MTZ files are produced.

For the MR_AUTO, MR_RNP and MR_LLG modes, unless HKLOut OFF is given as an optional keyword, Phaser produces an MTZ file with "SigmaA" type weighted Fourier map coefficients for producing electron density maps for rebuilding.

{| class="wikitable" style="text-align:left" 
|-
! MTZ Column Labels !! Description
|-
| FWT/PHWT || Amplitude and phase for 2''m''&#124;F<sub>obs</sub>&#124;-''D''&#124;F<sub>calc</sub>&#124; exp(''i''&alpha;<sub>calc</sub>) map
|-
| DELFWT/PHDELWT || Amplitude and phase for ''m''&#124;F<sub>obs</sub>&#124;-''D''&#124;F<sub>calc</sub>&#124; exp(''i''&alpha;<sub>calc</sub>) map
|-
| FOM || ''m'', analogous to the "Sim" weight, to estimate the reliability of &alpha;<sub>calc</sub>
|-
| HLA/HLB/HLC/HLD || Hendrickson-Lattman coefficients encoding the phase probability distribution
|}