Phenix version 1.8.2 released
The Phenix developers are pleased to announce that version 1.8.2 of Phenix is now available. Binary installers for Linux, Mac OSX, and Windows platforms are available at the download site: http://phenix-online.org/download/ Highlights from this version: Ensemble refinement, updated hydrogen parameters in refinement and validation, mmCIF reading and writing, LLG maps output from refinement, ligand pipeline for automated solution of protein/ligand complexes, autobuilding starting from a very accurate but very small part of a model, CC* calculation from unmerged data, maximum entropy maps, and PDB editor. Graphical interface: ==================== - New GUIs: phenix.merging_statistics, phenix.pdb_editor General: ======== - Multiple bug fixes - phenix.refine, phenix.reduce, and MolProbity updated to use consistent, revised, electron-cloud centers for hydrogen positions as default (for X-ray) - also see MolProbity website for details: http://molprobity.biochem.duke.edu - mmCIF format now supported in place of PDB format for input to many programs - new commands: phenix.ensemble_refinement, phenix.ligand_pipeline, phenix.sort_hetatms, phenix.cc_star, phenix.pdb_editor, phenix.maximum_entropy_map Refinement: =========== - phenix.refine - support for LLG map type - uses Phaser to compute residual anomalous LLG map - best when used with group_anomalous strategy, which will flatten the LLG map around existing anomalous scatterers with refined f'/f''. - alternatively, anomalous_residual map type (similar but less sensitive) - automatic linking in refinement and pdbtools for residues in the same chain - enabled with automatic_linking.intra_chain=True; this includes carbohydrate linking to protein and between sugars, and covalently bound ligands. - optional output of mmCIF format model and data files - phenix.ensemble_refinement (new command): - New method for refining ensemble models - Combines MD simulation with X-ray restraints that simultaneously account for anisotopic and anharmonic atomic distributions. - For full description see: Burnley BT, Afonine PV, Adams PD, Gros P. 2012. Modelling dynamics in protein crystal structures by ensemble refinement. eLife 1:e00311. doi: 10.7554/elife.00311. Experimental Phasing and Model Building: ======================================== - phenix.autobuild: - now uses torsion NCS parameterization when NCS is used in refinement - building starting from a very accurate but very small part of a model: You can now use the keyword rebuild_from_fragments=True to start rebuilding from fragments of a model. You might want to use this if you look for ideal helices using Phaser, then rebuild the resulting partial model, as in the Arcimboldo procedure. The special feature of finding helices is that they can be very accurately placed in some cases. This really helps the subsequent rebuilding. If you have enough computer time, then run it several or even many times with different values of i_ran_seed. Each time you'll get a slightly different result. - Base-pairing in RNA building -- phenix.autobuild will now try to guess which bases in a model are base-paired, and if there is no positive sequence match to the model, the bases that are base-paired will be chosen to be complementary. You can set the cutoff for base pairing with the keyword dist_cut_base. - waters are automatically named with the chain of the closest macromolecule if you set sort_hetatms=True. This is for the final model only. - you can supply a target position for your model with map_to_object=my_target.pdb. Then at the very end of the run your molecule will be placed as close to this as possible. The center of mass of the autobuild model will be superimposed on the center of mass of my_target.pdb using space group symmetry, taking any match closer than 15 A within 3 unit cells of the original position. The new file will be overall_best_mapped.pdb. Molecular Replacement: ====================== - phenix.mr_rosetta - You can now give commands for Rosetta in mr_rosetta, including a command to specify where disulfide bonds are located - The Rosetta models are now identified by an ID number so that they have unique names - Default number of homology models to download is now 1 (was 5) - Default number of NCS copies (if ncs_copies=Auto) is number leading to solvent content closest to 50%; if ncs_copies=None then all plausible values of ncs_copies are tested. New commands: ============= - phenix.ligand_pipeline (new command): - combines Xtriage, Phaser, eLBOW, phenix.refine, AutoBuild, and LigandFit to automatically solve protein/ligand complexes - optional integration with Coot (parameter interactive=True) allows semi-interactive operation where more rebuilding is required - phenix.cc_star (new command): - combined assessment of model and data quality, as outlined in Karplus & Diederichs (2012) Science 336:1030-3. - summary also output by phenix.model_vs_data if additional unmerged_data keyword is specified - phenix.maximum_entropy_map (new command): - tool to compute maximum entropy map from map coefficients. The program reads input Fourier map coefficients and modifies corresponding synthesis using Maximum-Entropy Method (MEM). The MEM modified map is everywhere positive, smooth and is of higher resolution. The method uses is a modification of Gull & Daniell (1978) algorithm. - phenix.sort_hetatms (new command): - rearranges heteroatoms (ligands, waters, etc.) in a model so they are paired with the nearest macromolecule chain, similar to the PDB's processing of models - phenix.pdb_editor (new command): - graphical editor for PDB files, based on tree view of model hierarchy - perform common operations such as chain renaming, renumbering, manipulation of atomic properties, add/remove atoms Ligands: ======== - phenix.ready_set: - methyl rotations now automatic when adding explicit hydrogens (also in phenix.reduce) - more options adding deuteriums to a model have been introduced Miscellaneous: ============== - phenix.xtriage: - include merging statistics if unmerged intensities are used as input - phenix.maps: - added wavelength parameter and support for anomalous residual and Phaser LLG map coefficients For a full list of changes see: http://www.phenix-online.org/documentation/CHANGES Please note that this publication should be used to cite use of Phenix: PHENIX: a comprehensive Python-based system for macromolecular structure solution. P. D. Adams, P. V. Afonine, G. Bunkóczi, V. B. Chen, I. W. Davis, N. Echols, J. J. Headd, L.-W. Hung, G. J. Kapral, R. W. Grosse-Kunstleve, A. J. McCoy, N. W. Moriarty, R. Oeffner, R. J. Read, D. C. Richardson, J. S. Richardson, T. C. Terwilliger and P. H. Zwart. Acta Cryst. D66, 213-221 (2010). Full documentation is available here: http://www.phenix-online.org/documentation/ There is a Phenix bulletin board: http://www.phenix-online.org/mailman/listinfo/phenixbb/ Please consult the installer README file or online documentation for installation instructions. Direct questions and problem reports to the bulletin board or: [email protected] and [email protected] Commercial users interested in obtaining access to Phenix should visit the Phenix website for information about the Phenix Industrial Consortium. The development of Phenix is principally funded by the National Institute of General Medical Sciences (NIH) under grant P01-GM063210. We also acknowledge the generous support of the members of the Phenix Industrial Consortium. -- Paul Adams Deputy Division Director, Physical Biosciences Division, Lawrence Berkeley Lab Division Deputy for Biosciences, Advanced Light Source, Lawrence Berkeley Lab Adjunct Professor, Department of Bioengineering, U.C. Berkeley Vice President for Technology, the Joint BioEnergy Institute Laboratory Research Manager, ENIGMA Science Focus Area Building 64, Room 248 Tel: 1-510-486-4225, Fax: 1-510-486-5909 http://cci.lbl.gov/paul Lawrence Berkeley Laboratory 1 Cyclotron Road BLDG 64R0121 Berkeley, CA 94720, USA. Executive Assistant: Louise Benvenue [ [email protected] ][ 1-510-495-2506 ] --
Hi, I have a 3.5 angstrom Os SAD phased map from AutoSol that looks real good (~50% fitted as poly ALA) and a 1.5 Angstrom set of native data. I would like to try phase extension in steps to see if the map improves enough for AutoBuild to fit the sequence. What AutoSol files/flags do I need for AutoBuild in addition to the high res data to get the best results. Thanks, John
Hi John,
Tom Terwilliger will have to answer the question of whether there's a better way to extend to the high resolution data set than the defaults in AutoSol/AutoBuild. If there is, then I imagine he'll want to change those defaults!
I just thought I would check whether you're confident that the Os and native data sets are truly isomorphous. It doesn't take a lot of non-isomorphism before you run into problems transferring the phase information from one crystal to another.
If there is significant lack of isomorphism (e.g. a cell dimension change as big as 1A or more) then it might be worth using cross-crystal averaging to transfer the phase information. We've used this for a recent structure solution, where we cut out the density for the protein from the SAD-phased map, then used the density as a molecular replacement model where rigid-body refinement was enough to determine the small shift in rotation and translation required to place that density correctly in the native cell. Cutting out the density and preparing a corresponding MTZ file for Phaser can be accomplished fairly easily using Tom's phenix.cut_out_density tool, if you have a PDB file that can be used to define the envelope for the protein density. Once you've phased the native data with that map, then you can use Tom's phenix.multi_crystal_average to average between the two forms. You'd probably want to follow that up by phase extension of the native crystal, but now starting from the phases obtained from the multi-crystal averaging.
Best wishes,
Randy Read
On 26 Jun 2013, at 03:58, John Rose
Hi,
I have a 3.5 angstrom Os SAD phased map from AutoSol that looks real good (~50% fitted as poly ALA) and a 1.5 Angstrom set of native data. I would like to try phase extension in steps to see if the map improves enough for AutoBuild to fit the sequence.
What AutoSol files/flags do I need for AutoBuild in addition to the high res data to get the best results.
Thanks,
John
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
------ Randy J. Read Department of Haematology, University of Cambridge Cambridge Institute for Medical Research Tel: + 44 1223 336500 Wellcome Trust/MRC Building Fax: + 44 1223 336827 Hills Road E-mail: [email protected] Cambridge CB2 0XY, U.K. www-structmed.cimr.cam.ac.uk
Can't you just refine the poly-Ala model against the 1.5A native data? (Perhaps after rigid body refinement or even molecular replacement if the data is too non-isomorphous). And then run Autobuild with these phases? Mark J van Raaij Lab 20B Dpto de Estructura de Macromoleculas Centro Nacional de Biotecnologia - CSIC c/Darwin 3 E-28049 Madrid, Spain tel. (+34) 91 585 4616 http://www.cnb.csic.es/~mjvanraaij On 26 Jun 2013, at 10:44, Randy Read wrote:
Hi John,
Tom Terwilliger will have to answer the question of whether there's a better way to extend to the high resolution data set than the defaults in AutoSol/AutoBuild. If there is, then I imagine he'll want to change those defaults!
I just thought I would check whether you're confident that the Os and native data sets are truly isomorphous. It doesn't take a lot of non-isomorphism before you run into problems transferring the phase information from one crystal to another.
If there is significant lack of isomorphism (e.g. a cell dimension change as big as 1A or more) then it might be worth using cross-crystal averaging to transfer the phase information. We've used this for a recent structure solution, where we cut out the density for the protein from the SAD-phased map, then used the density as a molecular replacement model where rigid-body refinement was enough to determine the small shift in rotation and translation required to place that density correctly in the native cell. Cutting out the density and preparing a corresponding MTZ file for Phaser can be accomplished fairly easily using Tom's phenix.cut_out_density tool, if you have a PDB file that can be used to define the envelope for the protein density. Once you've phased the native data with that map, then you can use Tom's phenix.multi_crystal_average to average between the two forms. You'd probably want to follow that up by phase extension of the native crystal, but now starting from the phases obtained from the multi-crystal averaging.
Best wishes,
Randy Read
On 26 Jun 2013, at 03:58, John Rose
wrote: Hi,
I have a 3.5 angstrom Os SAD phased map from AutoSol that looks real good (~50% fitted as poly ALA) and a 1.5 Angstrom set of native data. I would like to try phase extension in steps to see if the map improves enough for AutoBuild to fit the sequence.
What AutoSol files/flags do I need for AutoBuild in addition to the high res data to get the best results.
Thanks,
John
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
------ Randy J. Read Department of Haematology, University of Cambridge Cambridge Institute for Medical Research Tel: + 44 1223 336500 Wellcome Trust/MRC Building Fax: + 44 1223 336827 Hills Road E-mail: [email protected] Cambridge CB2 0XY, U.K. www-structmed.cimr.cam.ac.uk
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
I would just run autobuild with the experimental data and hl coeffs as "data" and the high resolution data as "hires" data and your current model and sequence file. Specify "rebuild_in_place=False" and that should work well. You might cut off the resolution at 1.8 A to speed it up and slightly improve the model-building but I expect that wouldn't make too much difference. The phase extension should automatically be carried out in steps in autobuild density modification. All the best, -Tom T On Jun 26, 2013, at 3:05 AM, Mark J van Raaij wrote:
Can't you just refine the poly-Ala model against the 1.5A native data? (Perhaps after rigid body refinement or even molecular replacement if the data is too non-isomorphous). And then run Autobuild with these phases?
Mark J van Raaij Lab 20B Dpto de Estructura de Macromoleculas Centro Nacional de Biotecnologia - CSIC c/Darwin 3 E-28049 Madrid, Spain tel. (+34) 91 585 4616 http://www.cnb.csic.es/~mjvanraaij
On 26 Jun 2013, at 10:44, Randy Read wrote:
Hi John,
Tom Terwilliger will have to answer the question of whether there's a better way to extend to the high resolution data set than the defaults in AutoSol/AutoBuild. If there is, then I imagine he'll want to change those defaults!
I just thought I would check whether you're confident that the Os and native data sets are truly isomorphous. It doesn't take a lot of non-isomorphism before you run into problems transferring the phase information from one crystal to another.
If there is significant lack of isomorphism (e.g. a cell dimension change as big as 1A or more) then it might be worth using cross-crystal averaging to transfer the phase information. We've used this for a recent structure solution, where we cut out the density for the protein from the SAD-phased map, then used the density as a molecular replacement model where rigid-body refinement was enough to determine the small shift in rotation and translation required to place that density correctly in the native cell. Cutting out the density and preparing a corresponding MTZ file for Phaser can be accomplished fairly easily using Tom's phenix.cut_out_density tool, if you have a PDB file that can be used to define the envelope for the protein density. Once you've phased the native data with that map, then you can use Tom's phenix.multi_crystal_average to average between the two forms. You'd probably want to follow that up by phase extension of the native crystal, but now starting
from the phases obtained from the multi-crystal averaging.
Best wishes,
Randy Read
On 26 Jun 2013, at 03:58, John Rose
wrote: Hi,
I have a 3.5 angstrom Os SAD phased map from AutoSol that looks real good (~50% fitted as poly ALA) and a 1.5 Angstrom set of native data. I would like to try phase extension in steps to see if the map improves enough for AutoBuild to fit the sequence.
What AutoSol files/flags do I need for AutoBuild in addition to the high res data to get the best results.
Thanks,
John
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
------ Randy J. Read Department of Haematology, University of Cambridge Cambridge Institute for Medical Research Tel: + 44 1223 336500 Wellcome Trust/MRC Building Fax: + 44 1223 336827 Hills Road E-mail: [email protected] Cambridge CB2 0XY, U.K. www-structmed.cimr.cam.ac.uk
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
On Wed, Jun 26, 2013 at 2:05 AM, Mark J van Raaij
Can't you just refine the poly-Ala model against the 1.5A native data? (Perhaps after rigid body refinement or even molecular replacement if the data is too non-isomorphous). And then run Autobuild with these phases?
If the model only contains around 50% of residues, and no sidechains, the phases from refinement are going to be fairly poor. I've never had much luck trying to autobuild starting such low completeness, even with very good data. -Nat
Hi Nat, I suggest that the phase extension plus the availability of experimental phases at low resolution is key here. The poor model will get refined (yes, not very good phases there), combined with experimental phases (still a bit weak), but then extended gradually to high resolution (possibly greatly improving the phases), and then model-building is done. I think it could work. All the best, Tom T On Jun 26, 2013, at 9:20 AM, Nathaniel Echols wrote:
On Wed, Jun 26, 2013 at 2:05 AM, Mark J van Raaij
wrote: Can't you just refine the poly-Ala model against the 1.5A native data? (Perhaps after rigid body refinement or even molecular replacement if the data is too non-isomorphous). And then run Autobuild with these phases?
If the model only contains around 50% of residues, and no sidechains, the phases from refinement are going to be fairly poor. I've never had much luck trying to autobuild starting such low completeness, even with very good data.
-Nat _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
Hi,
I think a reasonable possibility would be to follow Mark's suggestion to do rigid-body refinement of the polyAla model, but only use the result from that to decide whether or not the two crystals are significantly non-isomorphous. If the polyAla model moves during the rigid-body refinement and gives a significantly better agreement with the data (preferably measured by the likelihood score of the refinement program), then it will be worthwhile worrying about the non-isomorphism and finding a way to use the density itself as the model, not the very incomplete polyAla model. If things don't move in the polyAla rigid-body refinement, then the standard approach of combining the HL coefficients from the derivative with the high resolution native data should be very good.
Randy
On 26 Jun 2013, at 16:24, "Terwilliger, Thomas C"
Hi Nat, I suggest that the phase extension plus the availability of experimental phases at low resolution is key here. The poor model will get refined (yes, not very good phases there), combined with experimental phases (still a bit weak), but then extended gradually to high resolution (possibly greatly improving the phases), and then model-building is done. I think it could work. All the best, Tom T
On Jun 26, 2013, at 9:20 AM, Nathaniel Echols wrote:
On Wed, Jun 26, 2013 at 2:05 AM, Mark J van Raaij
wrote: Can't you just refine the poly-Ala model against the 1.5A native data? (Perhaps after rigid body refinement or even molecular replacement if the data is too non-isomorphous). And then run Autobuild with these phases?
If the model only contains around 50% of residues, and no sidechains, the phases from refinement are going to be fairly poor. I've never had much luck trying to autobuild starting such low completeness, even with very good data.
-Nat _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
------ Randy J. Read Department of Haematology, University of Cambridge Cambridge Institute for Medical Research Tel: + 44 1223 336500 Wellcome Trust/MRC Building Fax: + 44 1223 336827 Hills Road E-mail: [email protected] Cambridge CB2 0XY, U.K. www-structmed.cimr.cam.ac.uk
participants (6)
-
John Rose
-
Mark J van Raaij
-
Nathaniel Echols
-
Paul Adams
-
Randy Read
-
Terwilliger, Thomas C