Register New User | Download | Documentation | Tutorials | FAQ | Top Tips | Bugs | Publications | Developers |
Phaser is crystallographic software for phasing macromolecular crystal structures with maximum likelihood techniques. It is available through the Phenix and CCP4 software suites, and directly from the authors.
Most people will not need to read this documentation to solve their structure! To solve a structure by molecular replacement go to Automated Molecular Replacement and copy and edit the command script. Similarly, for SAD phasing, go to Automated Experimental Phasing and copy and edit the command script.
Other good sources of information are found in Frequently Asked Questions and Top Tips
This is the documentation for Phaser2.1. There are some changes between this version and previous versions so input scripts may need editing.
Phaser runs in different modes, which perform Phaser's different functionalities. Modes can either be basic modes or modes that combine the functionality of basic modes.
The mode of operation is controlled with the MODE keyword
Functionality | Mode | Description |
Anisotropy Correction | ANO | Corrects data for anisotropic diffraction, and makes the intensity distribution isotropic |
Cell Content Analysis | CCA | Calculates the expected number of molecular assemblies of given molecular weight in the unit cell using the Matthews coefficient |
Normal Mode Analysis | NMA | Perturbs a structure in rms deviation steps along combinations of normal modes |
Automated Molecular Replacement | MR_AUTO | Combines anisotropy correction, cell content analysis, fast rotation and translation functions, and refinement and phasing to automatically solve a structure by molecular replacement |
Fast Rotation Function | MR_FRF | Anisotropy correction and likelihood-enhanced fast rotation function calculated with Fast Fourier Transform |
Fast Translation Function | MR_FTF | Anisotropy correction and likelihood-enhanced fast translation function calculated with Fast Fourier Transform |
Brute Rotation Function | MR_BRF | Anisotropy correction and full likelihood rotation function calculated in a brute-force search of angles |
Brute Translation Function | MR_BTF | Anisotropy correction and full likelihood translation function calculated in a brute-force search of positions |
Packing | MR_PAK | Tests molecular replacement solutions to see whether they pack into the unit cell without overlap |
Log-Likelihood Gain | MR_LLG | Anisotropy correction and re-scoring of molecular replacement solutions with the full likelihood target function |
Refinement and Phasing | MR_RNP | Anisotropy correction and optimization of the orientation and position of molecular replacement models with the full likelihood target function |
Automated Experimental Phasing | EP_AUTO | Combines anisotropy correction, cell content analysis, and SAD phasing to automatically solve a structure by experimental phasing |
SAD Phasing | EP_SAD | Refines atoms using the SAD likelihood function, and completes the structure with log-Likelihood gradient maps |
The example scripts all refer to the tutorial test cases. The pdb, sequence and mtz files required to run the tutorials are distributed with Phaser.
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) and your models (How to Define Models), tell Phaser what to search for (use SEARch keyword), and a list of possible spacegroups (in the same point group - use the SGALternative keyword). The flow diagram for the automated molecular replacement mode is shown below. If this doesn't work (see "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"). See "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.
MODE MR_AUTO 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.
Example command script for finding BETA and BLIP. This is the minimum input, using all defaults (except the ROOT filename).
beta_blip_auto.comExample command script for finding BETA and BLIP. The spacegroup recorded on the mtz file is P3221 but the other hand is also a possibility. Both search orders (BETA first, BLIP second and BLIP first, BETA second) are tried, using the PERMutations ON keyword. We would not normally recommend using the PERMutations ON keyword for this case, as it is obvious that the larger molecule should be easier to find first. To speed up the calculation only the top peak after the translation function is taken into refinement. As one of a number of alternatives to providing sequence files to specify the composition, the molecular weights of the two components are given in this example.
beta_blip_auto_sg.comCompulsory Keywords
Optional Keywords
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.
TF Z-score |
Have I solved it? |
less than 5 |
no |
5 - 6 |
unlikely |
6 - 7 |
possibly |
7 - 8 |
probably |
more than 8 |
definitely* |
*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 P21, or space groups with one rotation axis like P43), 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.
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 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.
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 ROT SELEct PERCent 65. If that fails, try turning off the clustering feature in the save step (FINAL ROT STEP 2 CLUSter 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 & Jaroszewski, Acta Cryst. D60, 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.
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.
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!
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.
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
Sigma(A) = SQRT{fp*[1-fsol*exp(-Bsol*(sin(theta)/lambda)2)]}
* exp{-(8 Pi2/3)*RMS2*(sin(theta)/lambda)2}
where fsol(default=0.95) and Bsol(default=300Å2) 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!
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. 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.
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Å |
--> limit 0% |
2.60Å |
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.
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 density as a model
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.
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.
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.
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.
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.
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.
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).
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)
To include the files you should use the preprocessor command @
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
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. Examples are:
When more than one (potential) molecular replacement solution is present, the solutions are separated with the SOLUTION SET keywords. For example, if the rotation function and translation function for mol1 were very clear, then there will only be one type of 6DIM solution for mol1. If the rotation and translation functions for mol2 were then not clear, there will be a series of possible 6DIM solutions for mol2.
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 this pdb file to define an ensemble (named "mol1" in this example). Then manually create a .sol file of the following form and include it in the Phaser command script with the @filename preprocessor command (or include it directly in the script)
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.
The output of Phaser can be controlled with the following 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.
Optional Keywords
Where HKLOut ON 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.
MTZ Column Labels | Description | |
FWT | PHWT | Amplitude and phase for 2m|Fobs|-D|Fcalc| exp(i alpha-calc) map |
DELFWT | PHDELWT | Amplitude and phase for m|Fobs|-D|Fcalc| exp(i alpha-calc) map |
FOM | m, analogous to the "Sim" weight, to estimate the reliability of alpha-calc |
The selection of peaks for the fast rotation and fast translation function with rescoring of the top peaks with the full likelihood target (default RESCORE ON), is done in three steps, controlled by the keyword FINAL
For automated molecular replacement, specifying [ROT|TRA] after the keyword determines which of the rotation or translation function the selection criteria apply to. If neither is specified, the selection criteria apply to both.
Keyword | Applies |
FINAL [ROT|TRA] STEP 1 | Controls the selection of peaks from the fast search that will be rescored with the full likelihood target |
FINAL [ROT|TRA] STEP 2 | Controls the selection of peaks from the rescoring to be combined with other searches (e.g translation functions of different rotations, or rotation functions with different fixed components present) |
FINAL [ROT|TRA] STEP 3 | Controls the selection of peaks from the merged list for final output |
If RESCORE OFF is requested (no rescoring of the fast search peaks is performed), or if the brute rotation or translation searches are carried out, then there are only two stages to selection: selection of peaks from the individual searches, and selection of peaks from the combined list of solutions. Selection of peaks at each stage is controlled, respectively, by the keywords FINAL [ROT|TRA] STEP 2 and FINAL [ROT|TRA] STEP 3.
The selection of peaks saved for output in the rotation and translation functions can be done in four different ways.
Sub-Keyword | Description | Use |
FINAL [ROT|TRA] STEP [1|2|3] SELEct PERCent <CUTOFF> | 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). |
FINAL [ROT|TRA] STEP [1|2|3] SELEct SIGma <CUTOFF> | 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). |
FINAL [ROT|TRA] STEP [1|2|3] SELEct NUMber <CUTOFF> | 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. |
FINAL [ROT|TRA] STEP [1|2|3] SELEct ALL | None: 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. |
Peaks can also be clustered or not clustered prior to selection in steps 1 and 2.
Sub-Keyword | Description | Use |
FINAL [ROT|TRA] STEP [1|2] CLUSTER OFF | All high peaks on the search grid are selected | Default for STEP 1, because the position of the maximum may be different when the fast score and the full likelihood function are used. |
FINAL [ROT|TRA] STEP [1|2] CLUSTER ON | Points on the search grid with higher neighboring points are removed from the selection | Default for STEP 2. |
MODE MR_FRF combines the anisotropy correction and likelihood-enhanced fast rotation function (2), optionally rescored with the full rotation likelihood function (1), to find the orientation of a model in molecular replacement. Top rotation solutions are output to the file FILEROOT.rlist for input to a translation function. Top rotation solutions are also output to the file FILEROOT.sol.
Example command script for fast rotation function to find the orientation of BETA.
beta_frf.comExample command script for fast rotation function to find the orientation of BLIP knowing the position and orientation of BETA, with the position and orientation of BETA input from the command line.
blip_frf_with_beta.comExample command script for fast rotation function to find the orientation of BLIP knowing only the orientation of BETA, with the orientation of BETA input using the output solution file from the beta_frf.com job above.
blip_frf_with_beta_rot.comCompulsory Keywords
Optional Keywords
MODE MR_BRF combines the anisotropy correction and brute force likelihood rotation function (1) to find the orientation of a model in molecular replacement. Top rotation solutions are output to the file FILEROOT.rlist for input to a translation function. Top rotation solutions are also output to the file FILEROOT.sol.
Example command script for brute rotation function to find the orientation of BETA
beta_brf.comExample command script for brute rotation function to find the optimal orientation of BETA in a restricted search range and on a fine grid around the position from the fast rotation search.
beta_brf_around.comCompulsory Keywords
Optional Keywords
MODE MR_FTF combines the anisotropy correction and likelihood-enhanced fast translation function (3), optionally rescored by the full likelihood translation function (1), to find the position of a previously oriented model in molecular replacement. Top translation solutions are output to the file FILEROOT.sol.
Example command script for finding the position of BETA after the rotation function has been run and the results output to the file beta_frf.rlist
beta_ftf.comExample command script for finding the position of BLIP after the rotation function has been run and the results output to the file blip_frf_with_beta.rlist, which has the SOLUtion 6DIM keyword input for BETA and the SOLUtion TRIAL keyword input for the orientations to try for BLIP with the translation function.
blip_ftf_with_beta.comCompulsory Keywords
Optional Keywords
MODE MR_BTF combines the anisotropy correction and brute force likelihood translation function (1) to find the position of a previously oriented model in molecular replacement. Top translation solutions are output to the file FILEROOT.sol.
Example command script for brute Translation function to find the position of BETA after the rotation function has been run
beta_btf.comExample command script for brute Translation function to find the position of BETA degenerate in X after the rotation function has been run
beta_btf_degen_x.comCompulsory Keywords
Optional Keywords
MODE MR_RNP combines the anisotropy correction and refinement against the likelihood function (1) to optimize full or partial molecular replacement solutions and phase the data. At the end of refinement, the list of solutions is checked for duplicates, which are pruned. Refined solutions are output to the file FILEROOT.sol.
Example command script to refine a set of solutions
beta_blip_rnp.comCompulsory Keywords
Optional Keywords
MODE MR_LLG combines the anisotropy correction and the likelihood function (1) to calculate the log-likelihood gain for full or partial molecular replacement solutions. Solutions are output to the file FILEROOT.sol.
Example command script to rescore the solutions using a different resolution range of data and a different spacegroup
beta_blip_llg.comCompulsory Keywords
Optional Keywords
MODE MR_PAK determines whether molecular replacement solutions pack in the unit cell. Solutions that pack are output to the file FILEROOT.sol.
Example command script for determining whether a set of molecular replacement solutions pack in the unit cell.
beta_blip_pak.comCompulsory Keywords
Optional Keywords
Phaser performs SAD phasing in two modes. In the Automated Experimental Phasing mode, Phaser corrects for anisotropy, puts the data on absolute scale, does a cell content analysis, refines heavy atom sites to optimize phasing, and completes the model from log-likelihood gradient maps. Alternatively, the SAD Phasing mode can be used, which only refines heavy atom sites to optimize phasing, and completes the model from log-likelihood gradient maps. For this mode, the data should be pre-corrected for anisotropy and put on an absolute scale. This mode should only be used as part of automation pipelines, where the correct preparation of the data can be guaranteed and it saves cpu time.
MODE EP_AUTO combines the anisotropy correction, cell content analysis, and SAD Phasing modes to automatically solve a structure by experimental phasing. The final solution is output to the files FILEROOT.sol, FILEROOT.mtz and FILEROOT.pdb. Many structures can be solved by running an automated experimental phasing job with defaults.
Do SAD phasing of insulin. This is the minimum input, using all defaults (except the ROOT filename and explicitly specifying the wavelength).
insulin_auto.comCompulsory Keywords
Optional Keywords
You need to tell Phaser the name of the mtz file containing your data and the columns in the mtz file to be used. For SAD phasing, a single CRYSTAL and DATASET with anomalous data (F(+), SIGF(+), F(-) and SIGF(-)) must be given. The columns must have the correct CCP4 column type: 'G' for F(+) and F(-) and 'L' for SIGF(+) and SIGF(-). If the columns on your mtz file have somehow acquired the incorrect column type, you should change the column type with an mtz editing programme (e.g. sftools).
CRYStal insulin DATAset sad &Compulsory Keywords
Optional Keywords
Atom sites are defined with the ATOM keyword. Atoms sites may be entered one at a time specifying fractional or orthogonal coordinates, occupancy and B-factor, or from a PDB file, or from a mlphare-style HA file. The crystal to which the atoms correspond must be specified in the input.
A partial structure, for example a partial and poor MR solution (which may or may not contain anomalous scatterers) can be used to start the phasing, either alone or in addition to some anomalous scattering sites entered with the ATOM keyword. The partial structure is entered with the PART keyword.
If you do not have a partial MR structure, anomalous scatterers must be found using Patterson methods, Direct methods or Dual Space methods (e.g. phenix.hyss, SHELXD, SnB, Rantan) prior to running Phaser. Note that SHELXD outputs a pdb file with the scatterers labelled sulphur (S) regardless of the correct scattering type: you need to change the pdb so that it contains the correct scattering type prior to using it in Phaser.
The output of Phaser can be controlled with the following keywords:
Optional Keywords
MODE EP_SAD phases SAD data and completes the structure from log-likelihood gradient maps. The final solution is output to the files FILEROOT.sol, FILEROOT.mtz and FILEROOT.pdb .
Do SAD phasing of insulin. This is the minimum input, using all defaults (except the ROOT filename and explicitly specifying the wavelength)
insulin_sad.comCompulsory Keywords
Optional Keywords
MODE EP_SAD when used with the PART keyword phases SAD data and completes the structure from log-likelihood gradient maps using a partial structure as (at least part of) the initial atomic substructure. Only the real (i.e. non-anomalous) signal from the partial structure is used. The final solution is output to the files FILEROOT.sol, FILEROOT.mtz and FILEROOT.pdb. If the partial structure is relatively poor or incomplete (e.g. a low-homology molecular replacement model), it is best to search for the actual anomalous scatterer atom types. However, if you are using this option to identify anomalous scatterers from a final refined structure, it is best to search for purely anomalous scatterers to complete the real scatterer model with the missing imaginary component.
Do SAD phasing of insulin starting from partial model of one helix only. This is the minimum input, using all defaults (except the ROOT filename and explicitly specifying the wavelength)
insulin_sad.comCompulsory Keywords
Optional Keywords
Phaser produces map coefficients that reduce the model bias coming from the real contribution of the anomalous scatterers, and there is a small but significant improvement by starting density modification from these FWT/PHWT coefficients rather than FP, PHIB and FOM.
The FWT/PHWT coefficients should be used when running Resolve. If you run Phaser then Resolve from the AutoSol wizard of phenix, FWT/PHWT are picked up automatically.
If you're using DM from ccp4i, you have to provide PHIB, FOM and the HL coefficients in the interface, then use the "Run&View Com File" option to add "FDM=FWT PHIDM=PHWT" to the LABIN line of the DM input.
MODE ANO corrects the experimental data for anisotropy. Data (amplitude and associated sigma) are corrected for anisotropy and output to FILEROOT.mtz with column label set to the input column label with the addition of _ISO.
Example command script to correct BETA-BLIP data for anisotropy
beta_blip_ano.comCompulsory Keywords
Optional Keywords
MODE CCA determines the composition of the crystals using the "new" Matthews coefficients of Kantardjieff & Rupp (2003) "Matthews coefficient probabilities: Improved estimates for unit cell contents of proteins, DNA and protein-nucleic acid complex crystals". Protein Science 12:1865-1871. The molecular weight of ONE complex or assembly to be packed into the asymmetric unit is given with the COMPosition keyword, and the possible Z values (number of copies of the complex or assembly) that will fit in the asymmetric unit and the relative frequency of their corresponding VM values is reported. RESOlution should be set to the maximum resolution that has been observed for the crystal.
Example script for cell content analysis for BETA-BLIP
beta_cca.comCompulsory Keywords
Optional Keywords
MODE NMA writes out pdb files that have been perturbed along normal modes, in a procedure similar to that described by Suhre & Sanejouand (Acta Cryst. D60, 796-799, 2004). Each run of the program writes out a matrix FILEROOT.mat that contains the eigenvectors and eigenvalues of the atomic Hessian, and can be read into subsequent runs of the same job, to speed up the analysis.
Do normal mode analysis, write out eigenfile and coordinates perturbed by default movements along mode 7 only. (If you only wanted to prepare the eigenfile but not coordinates, you could include the command "XYZOut OFF".)
beta_nma.comThis example shows the use of several infrequently used options. Read in previous eigenfile and write out pdb files perturbed in 0.5 Ångstrom rms intervals in "forward" (positive dq values) direction only along modes 7 and 10 (and combinations of 7 and 10), up to a maximum rms shift of 1.2Å. Normally you would want to perturb the structure in both directions, and modes 8 and 9 are more likely to be of interest than mode 10, but something like this might be useful as part of a larger, more exhaustive exploration.
beta_nma_pdb.comCompulsory Keywords
Optional Keywords
Phaser can be controlled using keyword input. Not all keywords are relevant for all modes of operation (the list of relevant keywords for each mode is given with each mode above). Some keywords are only for single use, others have meaning when used more than once. The input values of many parameters are constrained to physically meaningful values. All non-compulsory parameters have defaults.
Preprocessor commands may be used in the keyword input to incorporate files, add comments or allow line continuation.
Most keywords only refer to a single parameter, and if used multiple times, the parameter will take the last value input. Some keywords are meaningful when entered multiple times. The order may or may not be important.