- phenixbb - phenix-online.org

Xtriage problem
by Abhinav Kumar 02 May '12

02 May '12

Hi, When I try to do R vs R analysis for calculated data using xtriage, it has a problem accepting calc labels. source /home/sw/rhel5/x86_64/phenix/phenix-1.7.3-928/phenix_env phenix.xtriage_1.7.3-928 junk.mtz calc_labels=FC ==> Sorry: No matching array: scaling.input.xray_data.calc_labels=FC Howevere, it works fine with an earlier version: source /home/sw/rhel5/x86_64/phenix/phenix-1.6.4-486/phenix_env phenix.xtriage_1.6.4-486 junk.mtz calc_labels=FC Thanks, Abhinav JCSG@SSRL, SLAC (650) 926-2992 -------- Original Message -------- Subject: RE: SP16569N-180314 Date: Tue, 1 May 2012 15:09:00 -0700 From: Miller, Mitchell D. <mmiller(a)slac.stanford.edu> To: Kumar, Abhinav <abhinavk(a)slac.stanford.edu> Hmm, it seems like it may be a bug introduced into phenix. (or else they changed they syntax and did not update the documentation) Can you report it? I get it to do the RvR analysis for calculated data if I use source /home/sw/rhel5/x86_64/phenix/phenix-1.6.4-486/phenix_env phenix.xtriage_1.6.4-486 junk.mtz calc_labels=FC but if I use source /home/sw/rhel5/x86_64/phenix/phenix-1.7.1-743/phenix_env phenix.xtriage_1.7.1-743 junk.mtz calc_labels=FC or source /home/sw/rhel5/x86_64/phenix/phenix-1.7.3-928/phenix_env phenix.xtriage_1.7.3-928 junk.mtz calc_labels=FC then I get the error Sorry: No matching array: scaling.input.xray_data.calc_labels=FC Thanks, Mitch P.S. the results I got were: R vs R statistic: R_abs_twin =<|I1-I2|>/<|I1+I2|> Lebedev, Vagin, Murshudov. Acta Cryst. (2006). D62, 83-95 R_abs_twin observed data : 0.451 R_abs_twin calculated data : 0.502 R_sq_twin =<(I1-I2)^2>/<(I1+I2)^2> R_sq_twin observed data : 0.279 R_sq_twin calculated data : 0.335 The analyses of the Patterson function reveals a significant off-origin peak that is 44.82 % of the origin peak, indicating pseudo translational symmetry. The chance of finding a peak of this or larger height by random in a structure without pseudo translational symmetry is equal to the 1.4447e-04. See the relevant section of the logfile for more details. The results of the L-test indicate that the intensity statistics behave as expected. No twinning is suspected. Even though no twinning is suspected, it might be worthwhile carrying out a refinement using a dedicated twin target anyway, as twinned structures with low twin fractions are difficult to distinguish from non-twinned structures. -----Original Message----- From: Kumar, Abhinav Sent: Tuesday, May 01, 2012 1:30 PM To: Miller, Mitchell D. Subject: Re: SP16569N-180314 I am having trouble inputting Calc labels to xtriage: My mtz file has the following columns: FreeR_flag FP SIGFP FC PHIC FC_ALL PHIC_ALL FWT PHWT DELFWT PHDELWT FOM PHCOMB I tried "FC,PHIC" and "FC" for calc labels but xtriage does not like it. It writes: No matching array: scaling.input.xray_data.calc_labels=FC Possible choices: /mnt/exdsstaff/abhinavk/Refine/SP16569N-180314/RESULTS/current.mtz:FP,SIGFP /mnt/exdsstaff/abhinavk/Refine/SP16569N-180314/RESULTS/current.mtz:FOM /mnt/exdsstaff/abhinavk/Refine/SP16569N-180314/RESULTS/current.mtz:PHCOMB Thanks, Abhinav JCSG@SSRL, SLAC (650) 926-2992 On 05/01/2012 12:51 PM, Miller, Mitchell D. wrote: Also, you could try running xtriage with FC's from the untwined refinement to look at the R vs R stats for Fc vs Fobs.

2 2

Re: [phenixbb] Geometry Restraints - Anisotropic truncation
by Frank von Delft 01 May '12

01 May '12

Hi Pavel > we discussed this with Randy the other day.. A couple of copy-pasts from > that discussion: > > In general, given highly anisotropic data set: > > 1) maps calculated using all (unmodified) data by phenix.refine, > phenix.maps and similar tools are better than maps calculated using > anisotropy truncated data. So, yes, for the purpose of map calculation > there is no need to do anything: Phenix map calculation tools deal with > anisotropy very well. How did you define "better"? If there are a lot of reflections without signal, that makes them essentially missing, so by including them, you're effectively filling in for those reflections with only DFc. If anisotropy is very strong (i.e. many missing reflections), does that not introduce very significant model bias? The maps would look cleaner, though. (I haven't tested myself, btw; I'm genuinely wondering.) > 2) phenix.refine refinement may fail if one uses original anisotropic > data set. This is probably because the ML target does not use > experimental sigmas (and anisotropy correction by UCLA server is nothing > but Miller index dependent removing the data by sigma criterion - yeah, > that old well criticized practice of throwing away the data that you > worked hard to measure!). May be using sigmas in ML calculation could > solve the problem but that has to be proved. If there are large swathes of reciprocal space without signal - I don't see why shouldn't that be excluded? Tossing out individual reflections is of course silly, but what's wrong with trimming down the edges of the elipsoid? Cheers phx

4 4

Inputting DNA for Phenix MR and/or Autobuild
by Charles Allerston 01 May '12

01 May '12

Dear all, I can't find much in the way of documentation for this. Can someone point me to some please? I basically want to know the correct format for entering DNA into the search for MR and inputting into Autobuild. If I have a double stranded DNA do I enter it as >DNA1 AATT:AATT >DNA1 AATT TTAA etc. ? cheers, charlie Dr. Charles Allerston Genome Integrity & Repair Structural Genomics Consortium Nuffield Department of Medicine Old Road Campus University of Oxford OX3 7DQ http://www.thesgc.org/scientists/groups/oxford/genome-integrity-and-repair

8 12

Call for submissions to June 2012 Computational Crystallography Newsletter (CCN)
by Nigel Moriarty 01 May '12

01 May '12

Calling for articles and short communications of interest to structural biologists. The deadline for publication in the June 2012 issue is 29 May, 2012. The Computational Crystallography Newsletter (CCN) is an electronic newsletter for structural biologists, and is published online every 6 months. Feature articles, meeting announcements and reports can be submitted to me at any time for consideration. Submission of text by email or word-processing files using the CCN templates is requested. Past newsletters and the template are available at www.phenix-online.org/newsletter. Cheers Nigel -- Nigel W. Moriarty Building 64R0246B, Physical Biosciences Division Lawrence Berkeley National Laboratory Berkeley, CA 94720-8235 Phone : 510-486-5709 Email : NWMoriarty(a)LBL.gov Fax : 510-486-5909 Web : CCI.LBL.gov

1 0

Estimation of ligand binding affinity by occupancy refinement
by Zoran Stefanic 01 May '12

01 May '12

Dear all, I have a question about sensitivity of occupancy refinement in phenix. I have a series of datasets done at our home instrument of relatively modest resolutions from 2.8 to 3 A. These are performed on crystals soaked in progressively higher ligand concentrations. We are trying to see to which of the several active sites the ligand binds first so we went from low to high ligand concentrations. We wanted to estimate the amount of ligand bound by refining the occupancies of the ligand. We expect one active site to bind more strongly than the other two active sites. This was indeed what we observed but when we refine the occupancies of the ligands in weaker binding sites starting at 0.2 occupancies they rise to 0.5-0.6 although some atoms are totally out of density and some are in. B factors are reasonable, i.e. don't go wild. My question would be: how reliable is this estimation of ligand binding by occupancy refinement? Why doesn't the occupancy of ligands stay low if afterwards the density fit of the ligand looks rather unconvincing? Thank you in advance Zoran -- Dr. Zoran Stefanic Division of Physical Chemistry Rudjer Boskovic Institute Bijenicka 54 P.O. Box 180 Zagreb Croatia Phone: 00 385 1 457 1203 Fax: 00 385 1 468 0245

7 6

metal coordination
by Panne Daniel 30 Apr '12

30 Apr '12

Hi all, I had a question concerning metal coordination (zinc in this case). I have used phenix.metal_coordination to generate geometry restraints for refinement. However phenix.refine does not write out the necessary LINK records into the PDB file. This seems to lead to problems later during validation, as the metal coordination is not properly recognized. What would be the best way to generate the LINK records in Phenix? Thanks, Daniel

2 1

Error of Sculptor
by Zhang yu 26 Apr '12

26 Apr '12

Dear Phenixer, When I used Sculptor to generate a new model, there is a error which I can not figure out. I input a PDB file (*.pdb) and an alignment file (*.aln). The following is the log file (contents in ######). There seems something wrong with the *.aln file. ################# Reading PDB file ---------------- File name: **/**/******/******/**.pdb Separating solvent from macromolecules... Reading alignment files ----------------------- 1. **/**/**.aln ##################### The following is the content of the alignment file: **_** MVYSYTEKKRIRKDFGKRPQVLDVPYLLSIQLDSFQKFIEQDPEGQY----GLEAAFRSV **_** ---------MEIKRFGRIREVIPLPPLTEIQVESYRRALQADVPPEKRENVGIQAAFRET * **: :*: :* * .**::*::: :: * : *::****.. What is the problem with the alignment file? Thank you in advance! Fish

2 5

cut-out mtz edition
by Dialing Pretty 26 Apr '12

26 Apr '12

Dear All, I just cut out a fragment of chain and the corresponding electron density from the whole molecule. Will you please give me some suggestion on how to edit the attached file so that those electron density not from the protein fragment can be erased? Or do you have other methods to produce high quality figure which just shows the fragment chain and the fragment eletron density? Cheers, Dialing

4 7

Geometry Restraints - UPDATE
by Mario Sanches 25 Apr '12

25 Apr '12

Last week I asked a question about geometry restraints at low resolution. I would like to thank you all that took the time to answer, specially Pavel for looking at the data. First, here is the original question: __________________________________________ I am refining a low resolution structure (2.9A) using phenix.refine. As I continue the refinement Rwork/Rfree are dropping but my geometry statistics in general are very bad. My clashscore is getting worst and the RMS(angle) is really high. I have tried to play with the "wxc_scale" parameter and also ran phenix selecting the "Optimize X-ray/ADP weight" option. All attempts end with a RMS(angle) of ~3.8 and a Clashscore of ~190. Is there a known procedure to deal with this? I feel that my geometry weighing term is too loose but I don't know exactly how to tighten it other than decreasing the wxc_scale parameter. I have gone and manually corrected bad positions before but given the low resolution nature of the structure the clashes tend to be reestablished during refinement. Thank you in advance for your help, __________________________________________ It turns out that the reason to my nightmares was a highly anisotropic dataset. When I tried to fix geometry related problems in coot, phenix.refine was twisting the geometry back again, probably because it was trying to fit a lot of noise due to the anisotropy. Everything was getting worst, geometry, clashscore, and Ramachandran. Pavel finally corrected it by using this server: http://services.mbi.ucla.edu/anisoscale/ I should have been more diligent regarding that, since I could clearly see that my data was anisotropic from the diffraction images. I just didn't know how important this parameter could be. Anyways, phenix.xtriage will tell you if your data is anisotropic. The lesson is to pay attention to it. In my case, the quality of the electron density improved considerably, the geometry improved massively (manual intervention in coot was absolutely necessary, but now it stays correct after I manually fix the problems), clashscore lowered, etc. As a side note, it worked better without hydrogens in my case than with. It is certainly a parameter to try if you are having problems. Thank you all again for the tips. Mario Sanches -- Mario Sanches Postdoctoral Researcher Samuel Lunenfeld Research Institute Mount Sinai Hospital 600 University Ave Toronto - Ontario Canada M5G 1X5 http://ca.linkedin.com/in/mariosanches

3 4

labelit.index with compatibility file
by "Weiergräber, Oliver H." 24 Apr '12

24 Apr '12

Hello, I have used labelit.check_pdb_symmetry to evaluate a P1 dataset and model for possible higher symmetry. C2 turned out to be a candidate solution. When I used the new asymmetric unit content file (xyz_coset0.pdb) to force indexing in the new SG: labelit.index /path/to/my/images/template_####.img 1 90 compatibility_file=xyz_coset0.pdb, the program crashes with AttributeError: 'NoneType' object has no attribute 'mosaicity_spot_coverage' This happens with the version included in phenix-1.7.3 as well as with the latest standalone labelit package. Any ideas what might be causing this? Maybe the new cell fails to refine? It is absolutely possible that forcing the higher symmetry SG leads to significant positional rmsd - I actually believe that P1 is correct, but it's definitly not far from C2. Best regards ================================================ PD Dr. Oliver H. Weiergräber Institute of Complex Systems ICS-6: Structural Biochemistry Tel.: +49 2461 61-2028 Fax: +49 2461 61-1448 ================================================ ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Kennen Sie schon unsere app? http://www.fz-juelich.de/app

2 3