From Phaserwiki
Revision as of 11:14, 24 April 2012 by Airlie (talk | contribs)
If I manage to solve my structure using Phaser, what paper should I cite?
J. Appl. Cryst. (2007). 40, 658-674. Phaser crystallographic software. A. J. McCoy, R. W. Grosse-Kunstleve, P. D. Adams, M. D. Winn, L.C. Storoni and R.J. Read.
What can I do if Phaser fails to solve my structure with default parameters?
Try some of the suggestions for difficult cases.
Where do I report bugs and make suggestions?
Email the Phaser development team at cimr-phaser@lists.cam.ac.uk.
What does LLG stand for?
LLG stands for Log Likelihood Gain. The likelihood is the probability that the data would have been measured, given the model, so it allows us to compare how well different models agree with the data. (In the case of molecular replacement, the model consists of the atomic coordinates plus rotation and/or translation operators applied to those coordinates.) The LLG is the difference between the likelihood of the model and the likelihood calculated from a Wilson distribution, so it measures how much better the data can be predicted with your model than with a random distribution of the same atoms. The LLG allows us to compare different models against the same data set, but the LLG values for different data sets should not be compared with each other. See our publications for more details.
What does it mean if the best LLG is negative?
This means that your model is worse than a collection of random atoms! The LLG should always be positive, and it should increase as the solution progresses. If the LLG is negative (or if it decreases, say, when carrying out a translation search after a rotation search), that tells you that you are being too optimistic about how well your model can predict the data. Check whether you might have underestimated the content of the asymmetric unit, so that your model is less complete than you thought it was. If you're certain about the content, then your molecular replacement model is not as accurate as Phaser was assuming. Look at the model (or better yet a series of related models) to see whether there might be any domain movements. If there are, either search with separate domains or with a series of models with different hinge angles. If hinge movements don't explain the problem, try increasing the RMS error that Phaser has estimated from the sequence identity. If none of this works, think about other possibilities: do you have the wrong space group? have you crystallised the wrong protein?
How can I use electron density as a model?
The procedure to prepare structure factors representing a masked region of electron density is discussed here. You will need to remember both the extent of the mask and the location of its centre to supply as input to Phaser.
My input space group, as specified in the mtz-file, is X. The space group reported in phaser is Y.
The important thing for Phaser is the set of symmetry operators in the MTZ header, which defines the space group uniquely, not the name of the space group recorded in the header, which can be ambiguous if people use non-standard settings. Phaser uses Ralf Grosse-Kunstleve's cctbx library to look up the space group from the symmetry operations, and then reports the space group name from cctbx.

I have installed a recent version of Phaser with Phenix. How do I make sure that the ccp4i interface finds the Phenix version of Phaser?
Phenix wraps phaser as phenix.phaser.
By default, ccp4i uses the program name as a command, and leaves it to the $PATH variable (at least in Unix) to find the executable.
To change the version of phaser called by ccp4i from the default CCP4 executable (phaser) to the Phenix executable (called with phenix.phaser)
  1. Start ccp4i.
  2. Choose "System Administration"->"Configure Interface".
  3. At the bottom of the section labelled "External Programs", under "Give full path name for CCP4 programs to overcome name conflicts" choose "Add a program".
  4. Enter "phaser" in the left box (for the program name) and the name you want ccp4i to use (phenix.phaser) in the right box.
  5. Choose "Save"->"Save to installation file" if you have permission to change that file, or "Save"->"Save to user's home directory" if you do not.
I have installed Phaser and the ccp4i interface, but when I try to run Phaser from the interface I get the error message "couldn't execute "phaser": no such file or directory". How can I fix this?
The problem is that the phaser executable is not in your path. You either need to put it in your path (which you do either by putting the phaser executable in a directory that is already in your path, or by changing the definition of the $PATH environment variable in your setup files, e.g. .cshrc or .bashrc), or you need to tell the ccp4i interface where to find it, as in the answer to the question just above.
I am using Phaser to solve the structure of a nucleic acid, but it fails to detect serious clashes in the packing. What is going wrong?
The most likely problem is that Phaser is not recognising the residues as belonging to a nucleic acid. The residue name should be right-justified in the residue name field of ATOM records in a PDB file. So whereas 3-letter residue names for amino acids are in columns 18-20, 1-letter residue names for nucleic acids should be in column 20. If they are in column 18 or 19, they will not be recognised, and the trace atoms to detect clashes will not be picked up. A second possibility is that the atom names differ from those expected for the trace atoms.
The recent remediation of the PDB files to version 3 has created a problem for older versions of Phaser. Versions of Phaser up to 2.1.4 expect the pre-remediation residue names (e.g. A for the adenine residue in RNA, +A for modified versions such as deoxy in DNA). In the version 3 remediation of the PDB, a "D" was added to the standard names for the deoxy residues, so a new PDB file would now have DA for the adenine residue of DNA. To work around this, you can rename the residues to use the old convention (e.g. A or +A instead of DA) and Phaser will find the trace atoms for the clash detection. Newer versions of Phaser will recognise the new nomenclature.
Phaser runs out of memory. What can I do?
  1. Large problems consume a lot of memory, and we sometimes need more than 256Mb.
  2. The easiest way to reduce memory requirements is to reduce the resolution. By default Phaser uses data to 2.5Å resolution, but we've only had a very small number of cases that could be solved at 2.5Å but not at 3Å. So the resolution can probably be reduced in typical cases to 3Å, which will reduce many arrays by a factor of (2.5/3)3, i.e. reduced by nearly half, if you did have data to 2.5Å. If your molecule is very large, you can probably reduce the resolution even further, as the strength of the signal will depend to a great extent on the number of structure factors accepted.
  3. Phaser interpolates structure factors from a finely-sampled molecular transform--the sampling can be reduced by changing the BOXSCALE parameter from its default of 4 to something greater than 2.4.
  4. If it fails during the fast rotation function, the requirements there can be reduced by changing CLMN SPHERE from its default of twice the geometric mean radius of the model to something less.
  5. You might also want to check that the model contains only the atoms you want, and, if there are several models in an ensemble, that the models are properly superimposed.
  6. Phaser uses memory to keep track of potential partial solutions in the search tree, so you should not allow the search to become too large. In particular, we do not recommend increasing the allowed number of clashes to more than a very small number. Clashes arise in correct solutions only because of unconserved surface loops, so it is much better to trim such loops out from the model. As well, it is not a good idea to relax the criteria to save potential solutions too much from the defaults. For instance, for a difficult problem you may wish to keep rotations above 65% of the maximum (instead of the default of 75%), but reducing the threshold to 50% will increase the size of the search dramatically without giving much improvement in the chance of finding a solution.
  7. If you wish to ensure that Phaser's memory usage does not grow to the extent that other processes are hindered, you may be able to limit its memory usage, at least under some flavours of Unix. We have not tested this ourselves, but are told that you can use the "limit" command in the csh or tcsh shells, or the "ulimit" command in the bash shell.