- phenixbb - phenix-online.org

Phenix installation on macOS 14 Sonoma
by Kizziah, James 05 Oct '23

05 Oct '23

Hi all, I am having trouble getting Phenix to open on a new mac. I downloaded the latest official release of the point-and-click installer, ran xattr -c on it, and installed without issue. Initially, I can create the first project directory (or recreate it if I remove the .phenix directory), but then I get a notice that another instance of Phenix is running with the associated PID. If I continue anyway, python quits unexpectedly, and if Phenix is opened in the command line, this reply is given: “python[9678:116756] It's not legal to call -layoutSubtreeIfNeeded on a view which is already being laid out. If you are implementing the view's -layout method, you can call -[super layout] instead. Break on void _NSDetectedLayoutRecursion(void) to debug. This will be logged only once. This may break in the future. [3] segmentation fault phenix” However, the PID for this supposed other instance doesn’t exist. This occurs every time Phenix is run from Applications or in the command line, even after restarting the laptop (without resuming programs) or deleting and reinstalling Phenix. Any ideas how to solve this problem? Thanks, James

2 5

Recommendations for refining a large model against many focused maps
by Vorländer,Matthias Kopano 02 Oct '23

02 Oct '23

Hi everyone, Apologies if this has been asked before, but I would like to know what are the recommended procedures to refine a model against many (>10) cryo-EM maps from local refinement? Some of the maps have substantial overlap between them, and I manually annotated which part of the model is best resolved in which map. Very grateful for any suggestions, Best wishes, Matthias

2 1

exploding refinement
by Daniel Larsson 27 Sep '23

27 Sep '23

Hi developers, I'm having difficulty minimizing ribosome structures using real_space_refine. The structures are mostly fine (I think) and there are no sever close-contacts. But it seems to happen in particular with waters and/or hydrogens present. See below for an example error message. Searching the mailing list archive, I found an old thread on the same topic where Pavel explained that this can happen when the weights are set improperly. https://phenix-online.org/pipermail/phenixbb/2017-November/023588.html I suspect my problems are related to the ad hoc method of setting weights does not work well for a large structure with 150,000+ atoms. When I check the log file, the weight estimation looks like this: XYZ refinement ************** Weight determination summary: number of chunks: 2038 random chunks: chunk 1215 optimal weight: 50.0000 chunk 784 optimal weight: 5.9990 chunk 1173 optimal weight: 50.0000 chunk 591 optimal weight: 30.0000 chunk 385 optimal weight: 50.0000 chunk 380 optimal weight: 2.9990 chunk 1248 optimal weight: 50.0000 chunk 1338 optimal weight: 50.0000 chunk 971 optimal weight: 50.0000 chunk 183 optimal weight: 50.0000 chunk 1543 optimal weight: 50.0000 overall best weight: 27.7996 So there seems to be a large discrepancy for the optimal weight for different chunks. Out of a 10-macro cycle run (crashed on the last cycle), the overall best weight varied between 3.7 and 34, which I suspect contributes to the unstable minimization procedure. overall best weight: 33.9998 overall best weight: 20.5996 overall best weight: 5.0186 overall best weight: 4.6388 overall best weight: 3.7586 overall best weight: 34.1998 overall best weight: 27.7996 overall best weight: 18.1996 overall best weight: 9.1992 Do you think a constant weight could be a solution to this problem? Is it possible to set it manually? Which of the weights are set using the heuristic method? Are there different weights for e.g. bonded restraints and "extra" metal bond restraints? There are some references to weights in the .eff file and nonbonded_weight seems to be an interesting option with a default value of 100. Regards, Daniel Example run that explodes: phenix.real_space_refine resolution=2 run=minimization_global nproc=4 output.prefix=phe output.suffix=_min ignore_symmetry_conflicts=True macro_cycles=10 ligands.cif elbow.edits coot-42.pdb map.mrc Traceback (most recent call last): File "/Applications/phenix-1.20.1-4487/build/../modules/phenix/phenix/command_line/real_space_refine.py", line 8, in <module> run_program(real_space_refine.Program) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/iotbx/cli_parser.py", line 79, in run_program task.run() File "/Applications/phenix-1.20.1-4487/modules/phenix/phenix/programs/real_space_refine.py", line 207, in run log = self.logger) File "/Applications/phenix-1.20.1-4487/modules/phenix/phenix/refinement/macro_cycle_real_space.py", line 297, in __init__ self.caller(self.refine_xyz) File "/Applications/phenix-1.20.1-4487/modules/phenix/phenix/refinement/macro_cycle_real_space.py", line 312, in caller func() File "/Applications/phenix-1.20.1-4487/modules/phenix/phenix/refinement/macro_cycle_real_space.py", line 653, in refine_xyz self.minimization_no_ncs() File "/Applications/phenix-1.20.1-4487/modules/phenix/phenix/refinement/macro_cycle_real_space.py", line 716, in minimization_no_ncs log = self.log) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/mmtbx/refinement/real_space/individual_sites.py", line 51, in __init__ gradients_method = gradients_method) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/mmtbx/refinement/real_space/weight.py", line 87, in __init__ rms_angles_limit = rms_angles_limit) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/mmtbx/refinement/real_space/individual_sites.py", line 368, in refine rms_angles_limit = rms_angles_limit) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/mmtbx/refinement/real_space/individual_sites.py", line 235, in __init__ weight = weight) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/mmtbx/refinement/real_space/individual_sites.py", line 112, in refine states_collector = self.states_accumulator) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/cctbx/maptbx/real_space_refinement_simple.py", line 174, in __init__ exception_handling_params=lbfgs_exception_handling_params) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/scitbx/lbfgs/__init__.py", line 278, in run line_search) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/scitbx/lbfgs/__init__.py", line 131, in run_c_plus_plus f, g = target_evaluator.compute_functional_and_gradients() File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/cctbx/maptbx/real_space_refinement_simple.py", line 245, in compute_functional_and_gradients compute_gradients=True) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/cctbx/geometry_restraints/manager.py", line 1479, in energies_sites flags=flags, sites_cart=sites_cart, site_labels=site_labels) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/cctbx/geometry_restraints/manager.py", line 1381, in pair_proxies check_bonded_distance_cutoff(sites_frac=sites_frac) File "/Applications/phenix-1.20.1-4487/modules/cctbx_project/cctbx/geometry_restraints/manager.py", line 1262, in check_bonded_distance_cutoff raise RuntimeError(msg) RuntimeError: Bond distance > max_reasonable_bond_distance: 58.8204 > 50: distance: 19 - 25: 20.675 distance: 21 - 22: 4.594 distance: 21 - 23: 14.720 distance: 22 - 24: 27.218 distance: 25 - 26: 15.535 distance: 25 - 138: 20.583 distance: 26 - 27: 10.976 distance: 26 - 29: 9.260 distance: 27 - 28: 6.472 distance: 27 - 34: 28.251 distance: 28 - 135: 26.553 distance: 29 - 30: 30.275 distance: 30 - 31: 45.594 distance: 31 - 32: 42.003 distance: 32 - 33: 58.820 distance: 34 - 35: 15.118 distance: 34 - 40: 32.473 distance: 35 - 36: 10.126 distance: 35 - 38: 33.272 distance: 36 - 37: 36.153 distance: 36 - 41: 14.653 distance: 38 - 39: 31.110 distance: 39 - 40: 31.467 distance: 41 - 42: 36.418 distance: 42 - 43: 13.145 distance: 43 - 44: 8.206 distance: 43 - 45: 40.869 distance: 45 - 46: 12.390 distance: 46 - 47: 25.848 distance: 46 - 49: 16.457 distance: 47 - 48: 15.264 distance: 47 - 53: 38.374 distance: 49 - 50: 27.548 distance: 50 - 51: 46.020 distance: 50 - 52: 31.107 distance: 53 - 54: 25.030 distance: 54 - 55: 33.266 distance: 55 - 56: 15.731 distance: 55 - 57: 17.553 distance: 57 - 58: 8.147 distance: 58 - 59: 15.533 distance: 58 - 61: 3.968 distance: 59 - 60: 32.012 distance: 59 - 66: 13.102 distance: 60 - 143: 27.836 distance: 61 - 62: 21.904 distance: 62 - 63: 22.068 distance: 63 - 64: 40.044 distance: 64 - 65: 14.241 distance: 66 - 67: 13.162 distance: 67 - 68: 14.727 distance: 67 - 70: 18.482 distance: 68 - 69: 7.119 distance: 68 - 74: 16.874 distance: 70 - 71: 23.617 distance: 70 - 72: 26.751 distance: 71 - 73: 31.237 distance: 74 - 75: 24.016 distance: 74 - 146: 23.850 distance: 75 - 76: 10.199 distance: 75 - 78: 26.004 distance: 76 - 77: 12.111 distance: 76 - 81: 13.195 distance: 77 - 157: 10.604 distance: 78 - 79: 24.115 distance: 78 - 80: 26.622 distance: 81 - 82: 9.528 distance: 82 - 83: 10.254 distance: 82 - 85: 9.660 När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/ E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: http://www.uu.se/en/about-uu/data-protection-policy

1 0

Updating other tools to use and output in mmCIF format and option to add hydrogens in real_space_refine
by Adrián González López 21 Sep '23

21 Sep '23

Hi Phenix team, I have a couple of feature suggestions: It would be great if all the other tools within phenix would be able to have mmCIF files as both input and output. It causes a lot of problems when you are forced to switch between pdb and mmCIF, for example when using ReadySet to add hydrogens. On that note, it would also be very useful to have an option in real space refine to add hydrogens automatically before the refinement and remove them after the refinement. Thanks! Best, Adrián När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/ E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: http://www.uu.se/en/about-uu/data-protection-policy

3 2

map deposition strategy after density modification
by Daniel Larsson 20 Sep '23

20 Sep '23

Hi Phenix community, I’ve been using density modification with some success for my data and am considering the most appropriate way to do model building/refinement and then deposition of my results. Here are some questions/observations: 1) Which map should I refine against (most importantly, do the final minimization using phenix.real_space_refine)? The DM map is the most clear one, so I’m favoring to do it against this one (as long as the geometry/validation is also best for this one). 2) Which map should I deposit as my main map? Is it the autosharpened one or the DM one? Since the DM map looks the best, I want the user who only downloads one map to see this one, so again I favoring this map. 3) Which nominal resolution should I quote for my reconstruction? Since the procedure seems to introduce correlation between the two maps (see point 4 below), it does not seem to be possible to obtain a gold-standard FSC value between two truly independent half-maps. As the DM procedure supposedly actually improves the map (by leveraging knowledge about what solvent and macromolecular maps usually looks like and thereby improves the Fourier coefficients), it feels like it would be misrepresenting the data by quoting the FSC_0.143 from the original reconstruction. Should I use the FSC_0.5 estimated value that phenix.resolve_cryo_em outputs? 4) Which FSC curve should I deposit? When I calculate the FSC between the two density modified half-maps, I get a funny (or rather not so funny) looking curve with a bump at around 3Å and it does not go to zero at Nyquist (which does not agree with the map quality). This must again be due to the induced correlation between the maps, presumably during the masking of solvent and macromolecule density. Phenix.resolve_cryo_em calculates a FSC curve to calculate the FSC_0.5 value, which according to the manual page corrects for the correlation induced between the two maps: "Density modification introduces some correlations between half-maps due to solvent flattening. This can have a small effect on the resolution estimates obtained with half-map FSC. The resolution estimates provided by the program are corrected for this effect." But is this curve good enough? I think OneDeposit wants to have the gold-standard FSC curve, right? 5) Which (nowadays mandatory) half-maps should one deposit? Here I would say that the original half-maps before DM makes more sense, since these are less processed. But if one specify these as the half-maps, there will be inconsistencies during validation, since the DM map will look quite different from the average between the two original half-maps. Also the automatic FSC curve will be very different from the deposited one. So in conclusion, despite what I say above, the most conservative thing would be to deposit the conventionally sharpened map as my main map and use the original half-maps for calculating the FSC-curve and use the 0.143 threshold from this curve to estimate the resolution. The DM map can be used during rebuilding/refinement, but I think final minimization should be against the main map during deposition (with restraints if the geometry gets worse). The DM map can be deposited as an auxiliary map. Do the community and the developers agree? Regards, Daniel När du har kontakt med oss på Uppsala universitet med e-post så innebär det att vi behandlar dina personuppgifter. För att läsa mer om hur vi gör det kan du läsa här: http://www.uu.se/om-uu/dataskydd-personuppgifter/ E-mailing Uppsala University means that we will process your personal data. For more information on how this is performed, please read here: http://www.uu.se/en/about-uu/data-protection-policy

4 4

autogenerate restraint.eff from PDB for phenix.varref
by vincent Chaptal 18 Sep '23

18 Sep '23

Hi Phenix team, Before launching phenix.varref, I would like to generate a ligand restraint file so the ligand doesn't fly away from its density. It would be great if the ligand_restraints.eff file could be generated from a PDB file already containing the ligand (for example originating from refinement), that we can then edit afterwards. The ligand I'm talking about is ATP in this case, so it doesn't need external cif file for refinement. I searched but couldn't identify such a job. It would be useful if it could be added to "PDB tools" or similar. Thank Best Vincent -- Vincent Chaptal, PhD Director of GdR APPICOM Drug Resistance and Membrane Proteins Lab MMSB -UMR5086 7 passage du Vercors 69007 LYON FRANCE +33 4 37 65 29 01 http://www.appicom.cnrs.fr http://mmsb.cnrs.fr/en/

3 3

racemic ligand refinement
by Calvin N Steussy 15 Sep '23

15 Sep '23

All, I need to refine a ligand that consists of two stereoisomers in my active site. I have decent density and have created models for the r and s forms of the guest with separate cif files. They have been fit independently into the active site density. My questions are; How to show these in the pdb file. Separate chains? Separate amino acids in a given chain? How do I keep them from interacting with one another during refinement? Creating an alt-position seems obvious but I'm not certain how to apply the different stereo restraints in that case. I'm sure someone has solved this before but I can't seem to find that information. Thanks, Nic Steussy Purdue University.

3 2

Phenix workshop at 80th Pittsburgh Diffraction Conference (October 14, 2023)
by Pavel Afonine 14 Sep '23

14 Sep '23

Dear community, this is a reminder that we will be hosting a Phenix user workshop at 80th Pittsburgh Diffraction Conference on October 14, 2023 and there are still spaces available! https://web.cvent.com/event/03acbdbf-b2ae-4875-a16f-672346cf1fd1/summary This is a great opportunity to learn about latest and greatest features of Phenix, ask questions and seek expert advice on your specific problems. See you all there! All the best, Pavel

1 0

Cis/trans peptide plane restraints ?
by CUNIASSE Philippe 13 Sep '23

13 Sep '23

Dear all, I am currently trying to refine a MDFF structure with the phenix RealSpaceRefine protocol of phenix. I am wondering if it is possible to apply systematic restraints to peptide plane (in trans when they are trans and cis when they are cis in order to avoid twisted conformations of the peptide planes at the end of the refinement. The only possibility I saw is to apply dihedral restraints defined one by one but when having thousands of residues, it seems not really convenient. Thanks in advance for your help. Best regards. Philippe. ----------------------------------------------- Philippe Cuniasse, PhD/HDR. Institut de Biologie Integrative de la cellule. UMR 9198 CNRS-CEA-Univ Paris Sud Bat 144 CE-Saclay 91191 Gif-sur-Yvette Cedex France Tel: (33) 1 69 08 56 35 Fax: (33) 1 69 08 47 12 Email: philippe.cuniasse(a)cea.fr<mailto:[email protected]> Web: http://biodev.cea.fr/rasmot3d/ [signature_863913621][signature_2053578832][signature_1816548304] -----------------------------------------------

2 1

Re: [phenixbb] Command line phenix.sculpt_ensemble
by Randy John Read 11 Sep '23

11 Sep '23

Dear Matthew, Sorry, I somehow missed this for a few days. The first thing I would say is that I’m not sure there’s much of a use case for sculptor and ensembler (or the combined application you were using) in these days of AlphaFold. Sculpted ensembles were a really powerful way to combine information from a collection of distant homologues to make a better model for molecular replacement. However, since AlphaFold became available I think the current best approach in this scenario is to take the AlphaFold model (which will integrate everything known structurally about the class of proteins far better than ensembler), run it through process_predicted_model (to downweight or trim off the less reliable parts of the model) and use that single model as your molecular replacement model. I haven’t yet seen a counter-example where the experimental structures of the distant homologues are better. Of course, if someone has a counter-example that would be very interesting to learn about! In terms of this bug, I’m wondering whether it’s a Python compatibility issue. I’m guessing that your Mac might be one of the newer ones with ARM (M1 or M2) chips. If so, are you using a build for the older Intel processors, or the native ARM build? In any case, if you’re using the ARM build then this will be built with Python 3. The easiest way to tell is to go to a terminal window with Phenix set up and type: phenix.python --version This will report whether or not you’re using Python 2.7 or Python 3.7. The sculpt_ensemble procedure has a lot of options, and I would need to know exactly which options you had set in order to try to reproduce the problem. Could you look in the project directory for a file with a name like .phenix/project_data/sculpt_ensemble_NN.eff, where “NN” is the job number? If you could send me that file, that would help. Best wishes, Randy Read > From: Whitley, Matthew (NIH/NCI) [C] <matthew.whitley(a)nih.gov> > Date: Thu, Sep 7, 2023 at 10:54 PM > Subject: [phenixbb] Command line phenix.sculpt_ensemble > To: phenixbb(a)phenix-online.org <phenixbb(a)phenix-online.org> > > > Hello all, > I am trying to use the command line tool phenix.sculpt_ensemble to process a series of PDB files in preparation for molecular replacement. > However, when I run the following on the command line: > phenix.sculpt_ensemble 2*.pdb input.target_sequence=RRAS2.fasta > I get the following errors: > Traceback (most recent call last): > File "/Applications/phenix-1.21rc1-5015/build/../modules/phaser/phaser/command_line/sculpt_ensemble.py", line 84, in <module> > sculpt_ensemble.run( phil = params.phil, logger = logger ) > File "/Applications/phenix-1.21rc1-5015/modules/phaser/phaser/sculpt_ensemble.py", line 610, in run > logger = logger, > File "/Applications/phenix-1.21rc1-5015/modules/phaser/phaser/sculpt_ensemble.py", line 259, in read_in_target_sequence_files > for ( fname, i ) in itertools.zip_longest( filenames, range( 1, nchains + 1 ) ): > AttributeError: 'module' object has no attribute 'zip_longest' > I am running phenix 1.21rc1-5015-000 on Mac OS 13.5.1. > Any ideas? > Thanks, > Matthew > _______________________________________________ > phenixbb mailing list > phenixbb(a)phenix-online.org > http://phenix-online.org/mailman/listinfo/phenixbb > Unsubscribe: phenixbb-leave(a)phenix-online.org ----- Randy J. Read Department of Haematology, University of Cambridge Cambridge Institute for Medical Research Tel: +44 1223 336500 The Keith Peters Building Hills Road E-mail: rjr27(a)cam.ac.uk Cambridge CB2 0XY, U.K. www-structmed.cimr.cam.ac.uk

1 0