August 2014 - phenixbb - phenix-online.org

labelit distl_minimum_number_spots_for_indexing
by Christian Roth 22 Sep '15

22 Sep '15

Dear Phenix-Team I installed the latest nightly build 1.8-1069. I tried to index some diffraction images and to overwrite the minimum usable spots for indesing I tried the suggested command. However If I try this command, it seems that it does not exist. At least in the list of the possible distl commands it does not show up. Do I have to install some additional stuff or change some preferences to get this command? Best Regards Christian

6 8

Refinement with new mtz.file
by Aleksandar Bijelic 14 Jul '15

14 Jul '15

Dear CCP4 user and experts, I refined (with PHENIX) a 3.0 A dataset obtaining Rfree of about 0.24 (with good geometry according to Ramachandran, Beta Outliers, etc.) .... Everything seems to be ok (especially in relation to the resolution) .... because the mtz.file I used was quite old and I cannot find my xscale.hkl file, I processed the data set again (this time with optimizng and polishing) and received a "better" file according to almost everything (resolution limit, I/sigma, CC(1/2), Rmeas), thus I used this new mtz.file and put it in my last refinement step (the refinement which led to the above mentioned Rfree = 0.24). Suprisingly, the refinement starts at Rwork = 0.18 and Rfree = 0.19 but ending up with 0.20 and 0.22, respectively. So I wanted to know if this is usual? I was expecting my data to become slightlly better but what is irritating me is the starting R-values of the refinement and that it get worse during refinement. Maybe I did something wrong? Is it reasonable to replace the mtz.file with a new one in the last refinement step or should I start the refinement from the scratch? In the sake of completeness, I deleted the header of the used pdb.file because of the R-flag error which occurs, since Phenix reconizes that the pdb.file was already used with other Rflags. Sorry, but I am still a beginner in this field, so I would be very grateful if somebody could explain me this situation and my mistake and if I need to start refinement from the beginning. Thank you in advance! Best Regards. Aleksandar -- ------------------------------------------- Aleksandar Bijelic, MSc. Institut für Biophysikalische Chemie Universität Wien Althanstrasse 14 A-1090 Wien Tel: +43 1 4277 52536 e-Mail: aleksandar.bijelic(a)univie.ac.at --------------------------------------------

7 10

help on MIR dataset
by Ni, Fengyun 25 Oct '14

25 Oct '14

Hi everyone, I am working on a MIR dataset: one native data, three EMTS soaked data at different concentration, one PbAc2 data. My initial trial with phenix autosol did not give positive solutions. I hope I could get some information from all of you. I index and integrate the data in Mosflm and possible group is P3, though the Pointless said the most possible is P3121. But for now, I only tried P3 at different resolutions for the reason that a potential MR solution (below 20% identities, TFZ=7.1) was found in P31 space group. If P3121 is the real space group, the space is too crowed to fit my molecules unless they have some unexpected symmetry. For the difference among dataset in P3 space group, the output from SCALEIT of CCP4 gives as follows, RMS differences|RMSiso RMSano ---------------------------------------- FP-hg |172.30 22.50 FP-hg2 |159.20 24.07 FP-hg3 |85.08 27.92 FP-pb |31.15 24.55 The native data's resolution cutoff is 3.2 A, and 3.2/3.8/3.5 for different EMTS data, 3.5 for Pb data.I did notice some radiation damage for EMTS (Hg) data (large negative B-factors in SCALA), but not for Pb data. And the anomalous signal only extend to 5.6 and 4.5 A for EMTS and Pb data, respectively, as indicated by phenix.xtriage. These are all the possible heavy atom data we could obtain. So i tried all of them in phenix.autosol. The input is like follows, autosol { seq_file = ../seq.dat crystal_info { solvent_fraction = 0.62 #determined from matthews coefficient to assure "reasonable" content in asymmetric unit. } native { data = nat.mtz } deriv { data = hg1.mtz atom_type = Hg inano = noinano *inano anoonly lambda = 1.00394 } deriv { data = hg2.mtz atom_type = Hg inano = noinano *inano anoonly lambda = 1.00394 } deriv { data = hg3.mtz atom_type = Hg inano = noinano *inano anoonly lambda = 1.00394 } deriv { data = pb.mtz atom_type = Pb inano = noinano *inano anoonly lambda = 0.94640 } model_building { build = False #my structure is DNA/protein complex, so i choose to stop the building process. } } I tried at different resolutions, 3.6/4.0/4.4/4.8/5.2/5.6/6.0 A. One solution was given based on Pb data at 4.8 A with following statistics, Solution # 6 BAYES-CC: 59.7 +/- 17.2 (2SD) Dataset #4 FOM: 0.24 Score type: SKEW CORR_RMS NCS_OVERLAP Raw scores: 0.31 0.69 0.00 100x EST OF CC: 59.74 17.55 31.25 Refined heavy atom sites (fractional): X Y Z xyz 0.033 0.020 0.538 xyz 0.417 0.217 0.113 xyz 0.041 0.010 0.721 The statistics is almost the same for its inverse, and i read from the output that the statistics for phasing other Hg datasets are very low (BAYES-CC is lower than 20) based on the above solution. The resulting map does not make much sense yet. Sorry for the long post. Any suggestion is welcome. Thank you very much! Fengyun

2 8

how to refine everything except n residues in phenix.refine?
by Murpholino Peligro 22 Oct '14

22 Oct '14

Hi everybody! Everytime when I (within coot) do "real space refine" two arginines that have two alternate conformations ..(interacting by hydrogen bonds); and then phenix.refine everything, both conformers move away. Therefore, when I open my mtz and pdb files from phenix.refine in coot, I'll have green blobs where there should be guanidium groups. Can I tell phenix.refine not to move only those two residues? It should be something like the following lines in the eff file? sites { individual = None torsion_angles = None rigid_body = None remove_selection=resid 45 remove_selection=resid 68 } Thank you very much

4 8

phenix.refine and R free values
by PC 03 Sep '14

03 Sep '14

3 4

Phasing using CryoEM Map
by Alexander Kintzer 02 Sep '14

02 Sep '14

Hello All, I trying to phase my 4Å data with low resolution cryoEM maps (various 12-18Å). There is some documentation, but not really for dealing with EM data. I am having trouble converting the EM data from mrc to suitable F's for phaser. One would want to try different density contours of the cryoEM map, but I haven't found a good way to accomplish this. I also have been unable to search for Ta6Br12 clusters using Autosol even though the documentation seems to suggest that it is possible using the "TX" or "XX" designation for heavy atom search. Any guidance would be extremely helpful. best, Alex

4 3

Re: [phenixbb] following on the anomalous map
by Kay Diederichs 29 Aug '14

29 Aug '14

Hi Charles, > Date: Thu, 28 Aug 2014 09:59:30 -0400 > From: CPMAS Chen <cpmasmit(a)gmail.com> > To: Gabor Bunkoczi <gb360(a)cam.ac.uk> > Cc: "PHENIX user mailing list \(phenixbb(a)phenix-online.org\)" > <phenixbb(a)phenix-online.org> > Subject: Re: [phenixbb] following on the anomalous map > Message-ID: > <CAAU4GKbzA37j=51X4jMOJjq3t4rKW7Jz9+CQrPxO-HN1kFOOiQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > HI, Gabor, > > Thanks for you suggestion. > > I tried this method, it did not give out NO sites for Br. > > why there is apparent anomalous signal and I cannot identify any Br sites? are you sure that your data processing used the correct parameters? E.g. in XDS you should definitively be using "FRIEDEL'S_LAW=FALSE". If you use XSCALE after XDS, it automagically picks up this setting from XDS_ASCII.HKL i.e. you don't have to specify this again. If you, by mistake, use FRIEDEL'S_LAW=TRUE, then the large intensity differences of Friedel pairs will be judged as outliers by XDS, and these reflections will be rejected - that might lead to featureless maps. If the anomalous signal is very strong, and the multiplicity is high, and the Chi^2 values are >1.5, you may also want to use (additionally) "STRICT_ABSORPTION_CORRECTION=TRUE" . But this is rarely necessary. There are similar options in other data processing programs. If you mix and match data processing programs (e.g. XDS integration and aimless scaling) you have to be careful to have the right settings in all programs. best, Kay > > As Nat pointed out, other atoms should have very weak anomalous signal > diffracted at Br absorption peak (3.8e- for Br, versus 0.2e- for the > sulfurs). In the difference map, I can clearly see some peaks at high sigma > (> 6), but the anomalous difference map(they are all generated by > phenix.refine or phenix.maps) is almost featureless, or the peaks has > no overlaps. The anomalous difference gives the possible place of Br while > the difference map gives the possible place of the whole ligand, and I > assume there should be some overlaps between them. Am I right? > > Charles >

1 0

Re: [phenixbb] following on the anomalous map
by CPMAS Chen 29 Aug '14

29 Aug '14

HI, Gabor, Thanks for you suggestion. I tried this method, it did not give out NO sites for Br. why there is apparent anomalous signal and I cannot identify any Br sites? As Nat pointed out, other atoms should have very weak anomalous signal diffracted at Br absorption peak (3.8e- for Br, versus 0.2e- for the sulfurs). In the difference map, I can clearly see some peaks at high sigma (> 6), but the anomalous difference map(they are all generated by phenix.refine or phenix.maps) is almost featureless, or the peaks has no overlaps. The anomalous difference gives the possible place of Br while the difference map gives the possible place of the whole ligand, and I assume there should be some overlaps between them. Am I right? Charles On Wed, Aug 27, 2014 at 6:28 AM, Gabor Bunkoczi <gb360(a)cam.ac.uk> wrote: > Hi Charles, > > I could be totally misunderstanding what you are trying to achieve, but I > think what you need to do is an MR-SAD calculation. First, solve the > structure with MR (use the macromolecule from the non-Br structure, or use > your current model if you have done refinement on it), and use the > Phaser-EP GUI, and select "SAD starting from MR model". This should > highlight any Br you may have, and gives you a PDB-file with all the peaks > (you can also get a proper anomalous map, but this is only useful for > visualization - the peak search will identify any peaks you may have). > > Let me know if you need more details! > > BW, Gabor > > > On 2014-08-26 14:49, CPMAS Chen wrote: > >> Thanks. Nat. >> >> Since I have some MET and CYT in the protein, could I try to supply >> their sulfur as the initial anomalous scatters? >> >> As for the anomalous isomorphous difference map, would it be useful I >> compare the datasets acquired at 1A wavelength and at the Br >> absorption peak (~0.92A)? >> >> Appreciate your help >> >> Charles >> >> On Mon, Aug 25, 2014 at 5:08 PM, Nathaniel Echols <nechols(a)lbl.gov> >> wrote: >> >> On Sun, Aug 24, 2014 at 6:46 AM, CPMAS Chen <cpmasmit(a)gmail.com> >>> wrote: >>> >>> Here is the point I am not clear. If I am using phenix.refine to >>>> generate LLG map, how do I pick the anomalous group since I have >>>> not placed them in the model yet? >>>> >>> >>> You can't. The LLG map only becomes really useful once you have >>> some anomalous scatterers placed and refined - this is how Phaser >>> substructure completion works. If your molecules have no other >>> significant anomalous scatterers other than the expected Br, the LLG >>> map won't do you much good. >>> >>> By the way, when I choose ion_placement and specify Br, the result >>>> comes with no Br. >>>> >>> >>> Not too surprising, since the code is tuned to look for ions, not >>> part of a covalent molecule, and halides also tend to bond >>> non-specifically and we haven't figured out how to deal with that >>> yet. >>> >>> I want to find whether the Br-containing ligand is seen in my >>>> protein which I have a high resolution structure available. >>>> >>>> I have data collected at Br wavelength, peak or higher position. >>>> Phenix.xtriage reported that the anomalous signal is present to >>>> about 4A. However, both AutoSol or MR-SAD cannot identify the Br >>>> position. Simply say, AutoSol or MR-SAD can not generate any >>>> solution. Well, of course, the simple answer would be that there >>>> is no such ligand cocrystallized. >>>> >>> >>> The simplest explanation is that you just don't have enough >>> anomalous signal to determine the substructure, which can be true >>> even if your ligand is bound. Running experimental phasing to >>> figure this out is unnecessary and time-consuming. >>> >>> Anyway, I am trying to see if the anomalous difference map or >>>> LLG(generated by phenix.maps, this would be the initial one I >>>> assume) can tell me anything more useful. >>>> >>>> So, my question on this topic would be what is a better way you >>>> guys would recommend to identify these Br-ligands? By the way, I >>>> did have the native datasets for the same protein with ligand. >>>> >>> >>> I think in this case I would start with the simple anomalous >>> difference map. If you run phenix.find_peaks_holes (it's in the >>> GUI, of course) and give anomalous data as input, it can pick out >>> the highest peaks in the anomalous map. If the ligand really is >>> bound and the Br site is ordered I would expect this to be >>> detectable. Another alternative is to compute an anomalous >>> isomorphous difference map between a dataset collected at or above >>> (in eV) the Br peak, and a dataset collected below the peak. This >>> will allow you to visualize the wavelength-dependent difference in >>> anomalous scattering, and it's going to be specific for elements >>> with absorption edges within that energy range. But I really don't >>> think this should be necessary to answer your question. >>> >>> -Nat >>> >> >> -- >> >> *************************************************** >> >> Charles Chen >> >> Research Associate >> >> University of Pittsburgh School of Medicine >> >> Department of Anesthesiology >> >> ****************************************************** >> >> >> _______________________________________________ >> phenixbb mailing list >> phenixbb(a)phenix-online.org >> http://phenix-online.org/mailman/listinfo/phenixbb >> > > -- > ################################################## > > Dr Gabor Bunkoczi > > Cambridge Institute for Medical Research > Wellcome Trust/MRC Building > Addenbrooke's Hospital > Hills Road > Cambridge CB2 0XY > ################################################## > -- *************************************************** Charles Chen Research Associate University of Pittsburgh School of Medicine Department of Anesthesiology ******************************************************

4 3

How to tighten ligand geometry in phenix.refine?
by Blankenfeldt, Wulf 28 Aug '14

28 Aug '14

Dear all, I am currently trying to refine a cacodylate ion that partially occupies the phosphate binding site of a PLP cofactor – partially meaning ~90%, in fact I am leaving the PLP out altogether. When I am refining this in phenix. refine, the cacodylate becomes “ugly”: the tetraeder gets slightly squashed and the atoms are flying apart a bit such that they are not automatically connected in Coot any more. I am now wondering if I can tighten the geometry just for the cacodylate to prevent this from happening, either by sending a magical command or by fiddling with the dictionary. Can anyone advise me, please? Regards, Wulf ________________________________ Helmholtz-Zentrum für Infektionsforschung GmbH | Inhoffenstraße 7 | 38124 Braunschweig | www.helmholtz-hzi.de Das HZI ist seit 2007 zertifiziertes Mitglied im "audit berufundfamilie" Vorsitzende des Aufsichtsrates: MinDir’in Bärbel Brumme-Bothe, Bundesministerium für Bildung und Forschung Stellvertreter: MinDirig Rüdiger Eichel, Niedersächsisches Ministerium für Wissenschaft und Kultur Geschäftsführung: Prof. Dr. Dirk Heinz; Franziska Broer Gesellschaft mit beschränkter Haftung (GmbH) Sitz der Gesellschaft: Braunschweig Handelsregister: Amtsgericht Braunschweig, HRB 477

2 1

phenix.refine abort
by sujata halder 27 Aug '14

27 Aug '14

Hi, I am trying to refine a protein with 60 chains (a T=1 virus; 5-3-2 symmetry) and each chain has 520 amino acids. I am using version 1.9 (Release tag: 1692). The job stopped midway and gave the error below followed by "Cannot allocate memory". I have run a similar job (i.e using a similar sized protein) before on an older version (version 1.7) and that had worked. Looking at the error I can't really figure out if the problem is related to installation or a missing module or something different about the code. I can share my files off-list. Here is the error: ====================== XYZ individual (reciprocal space) ====================== R-FACTORS RMSD CLASH RAMA ROTA CBET WEIGHT TARGETS work free delta bonds angl data restr 28.80 29.29 0.49 0.016 1.6 11.9 0.8 7.4 60 none 0.093 160.8996 Traceback (most recent call last): File "/usr/local/phenix-1.9-1692/build/intel-linux-2.6-x86_64/../../phenix/phenix/command_line/refine.py", line 11, in <module> command_line.run(command_name="phenix.refine", args=sys.argv[1:]) File "/usr/local/phenix-1.9-1692/phenix/phenix/refinement/command_line.py", line 163, in run call_back_handler=call_back_handler) File "/usr/local/phenix-1.9-1692/phenix/phenix/refinement/driver.py", line 1577, in run reference_model_manager = self.reference_model_manager).result File "/usr/local/phenix-1.9-1692/phenix/phenix/refinement/strategies.py", line 183, in __init__ ion_placement_manager = ion_placement_manager) File "/usr/local/phenix-1.9-1692/phenix/phenix/refinement/macro_cycle.py", line 114, in __init__ self.call(self.xyzrec, "XYZ individual (reciprocal space)") File "/usr/local/phenix-1.9-1692/phenix/phenix/refinement/macro_cycle.py", line 142, in call func(prefix = prefix) File "/usr/local/phenix-1.9-1692/phenix/phenix/refinement/macro_cycle.py", line 374, in xyzrec prefix = prefix) File "/usr/local/phenix-1.9-1692/phenix/phenix/refinement/xyz_reciprocal_space.py", line 204, in __init__ call_back=(len(trial_weights)==1)) File "/usr/local/phenix-1.9-1692/phenix/phenix/refinement/xyz_reciprocal_space.py", line 314, in try_weight result = self.show(weight=wt, print_stats=print_stats, call_back=call_back) File "/usr/local/phenix-1.9-1692/phenix/phenix/refinement/xyz_reciprocal_space.py", line 365, in show molprobity_scores = self.main.use_molprobity) File "/usr/local/phenix-1.9-1692/cctbx_project/mmtbx/model.py", line 1341, in geometry_statistics molprobity_scores = molprobity_scores) File "/usr/local/phenix-1.9-1692/cctbx_project/mmtbx/model_statistics.py", line 99, in __init__ self.clashscore = clashscore(pdb_hierarchy=pdb_hierarchy).get_clashscore() File "/usr/local/phenix-1.9-1692/cctbx_project/mmtbx/validation/clashscore.py", line 133, in __init__ verbose=verbose) File "/usr/local/phenix-1.9-1692/cctbx_project/mmtbx/validation/clashscore.py", line 257, in __init__ self.run_probe_clashscore(self.h_pdb_string) File "/usr/local/phenix-1.9-1692/cctbx_project/mmtbx/validation/clashscore.py", line 341, in run_probe_clashscore stdin_lines=pdb_string).raise_if_errors().stdout_lines File "/usr/local/phenix-1.9-1692/cctbx_project/libtbx/easy_run.py", line 158, in __init__ close_fds=not subprocess.mswindows) File "/usr/local/phenix-1.9-1692/build/intel-linux-2.6-x86_64/base/lib/python2.7/subprocess.py", line 709, in __init__ errread, errwrite) File "/usr/local/phenix-1.9-1692/build/intel-linux-2.6-x86_64/base/lib/python2.7/subprocess.py", line 1222, in _execute_child self.pid = os.fork() OSError: [Errno 12] Cannot allocate memory ------------------------------------------------------------------------------------------------------------- Thanks, Sujata

2 1