- phenixbb - phenix-online.org

Reporting phasing statistics.
by Francis E Reyes 15 Oct '08

15 Oct '08

So normally when I run autosol, my primary indicator of 'goodness' would be the SKEW, but in reporting to papers, it seems that the MIR statistics involve Rcullis, phasing power, and FOM. I can find FOM from solve_x.prt and resolve_x.log but where are the others? Thanks FR --------------------------------------------- Francis Reyes M.Sc. 215 UCB University of Colorado at Boulder gpg --keyserver pgp.mit.edu --recv-keys 67BA8D5D 8AE2 F2F4 90F7 9640 28BC 686F 78FD 6669 67BA 8D5D

2 2

? about optimize weights
by gerwald jogl 15 Oct '08

15 Oct '08

Hi All, I just started using phenix.refine and it's working quite well so far. I ran the optimize weight strategy at the end of a test refinement and it lowered the Rfree as intended. Unfortunately, when I ran the next refine job based on the output .def file, it seems that the 'best weights' found in the previous run were not conserved as the geometry and R factors got a lot worse. Where can I find the weights determined by the optimize run and how can I fix those for further refinement? Thanks, Gerwald

2 1

helix deformed during refinement in phenix
by Raja Dey 13 Oct '08

13 Oct '08

Dear All, I am using phenix to refine a long helix of about 120 residues in a complex structure, but in course of refinement the helix becoming distorted from helical geometry. As a result when I am displaying the refined structure in pymol as cartoon one long helix showed 3/4 discontinuous helices in a single chain. Is there any way to constrain or restrain the helix during refinement, so that refinement process can maintain the helical geometry? Any suggestion is well appreciated. With regards... Raja Raja Dey, Ph.D. Research Associate Molecular and Computational Biology University of Southern California

2 1

detwin data
by HUA YUAN 13 Oct '08

13 Oct '08

Dear Phenix community, I've used the phenix.refine with its detwin function. Is there any way to have a detwinned data output so that I can use it for other things. I tried use CCP4 detwin with the same twin law and twin fraction obtained from Phenix. However, this didn't work. Another question is whether I can use "some" phase information, say from DM into Phenix? I tried to include the PHIDM but Phenix complained about it saying "wrong array". Any suggestions or comments are hightly appreciated! Thanks, Hua

4 5

Re: [phenixbb] Files generated in Autobuild from simulated annealing runs
by Tom Terwilliger 07 Oct '08

07 Oct '08

Hi Rebecca, I'm sorry this didn't get answered on the phenix_bb! I somehow missed it too. When you run an omit map with model=mymodel.pdb omit_box_pdb=mymodel.pdb omit_res_start_list=500 omit_res_end_list=500 the autobuild wizard edits mymodel.pdb, setting the occupancies of all atoms that are within a box enclosing the atoms in residue 500 of mymodel.pdb (plus a 2 A border) to zero. Then it runs the cycles of autobuild you specify (in this case just a SA step), and produces a density-modified map (resolve_composite_map.mtz) using the resulting model to generate phase information (and keeping the occupancies of these atoms at zero). If mydata.mtz contains phase information, that is used as well. The output map is in resolve_composite_map.mtz and a pseudo-map showing where the OMIT region(s) is(are) located is in omit_region.mtz The file overall_best_denmod_map_coeff.mtz is actually not really relevant or useful when you are doing OMIT maps because it is just one of the intermediate files that are produced. In this particular example it will be identical to resolve_composite_map.mtz but if you do other types of OMIT maps it won't be the same. I changed the output of the autobuild wizard recently, so you might want to upgrade to the 1.3-final version. The end of the log file in this case should say: -------------------------------------------------- Summary of model-building for run 1 Tue Oct 7 08:17:30 2008 Files are in the directory: /net/chevy/raid1/terwill/misc/test/ AutoBuild_run_1_/ Starting mtz file: /net/chevy/raid1/terwill/misc/test/perfect.mtz Sequence file: /net/chevy/raid1/terwill/misc/test/seq.dat Composite omit map is in : /net/chevy/raid1/terwill/misc/test/ AutoBuild_run_1_/OMIT/resolve_composite_map.mtz Boundaries of omit regions are in : /net/chevy/raid1/terwill/misc/test/ AutoBuild_run_1_/OMIT/omit_region.mtz -------------------------------------------------- Which I hope is clearer than earlier output in which the overall_best_denmod_map_coeff.mtz file is mentioned but is irrelevant. I hope that helps! All the best, Tom T On Oct 7, 2008, at 7:19 AM, Page, Rebecca wrote: > Hi Tom, > I posted the question on the phenix bb and, when I got no response, > shot an email over to Frank von Delft, an old friend, to see if he > knew answer. > > He didn’t, but recommended I email you directly and to “ask him to > post the answer on the general bb :)”. He also mentioned he hadn’t > seen the post on the phenix bb and I would be interested to know if > you did not see it either (I received it). > > At any rate, here it goes: > > > I am newcomer to phenix and have a rookie question about the > generated > > files using the phenix.autobuild command. I generated an sa-omit map > > of my model, omitting the coordinates for a bound ligand (ligand is > > residue > > 500): > > > > phenix.autobuild data=mydata.mtz model=mymodel.pdb > > omit_box_pdb=mymodel.pdb omit_res_start_list=500 > omit_res_end_list=500 > > omit_chain_list=A composite_omit_type=sa_omit > > > > The output omit map (resolve_composite_map.mtz) looks great. > > > > > > My question is: > > What, exactly, is the "overall_best_denmod_map_coeff.mtz" in this > case > > and how is it related, if at all, to the > "resolve_composite_map.mtz"? > > > Thanks for your help, > Rebecca > > Rebecca Page > Brown University >

1 0

Files generated in Autobuild from simulated annealing runs
by Page, Rebecca 06 Oct '08

06 Oct '08

Dear Phenix users: I am newcomer to phenix and have a rookie question about the generated files using the phenix.autobuild command. I generated an sa-omit map of my model, omitting the coordinates for a bound ligand (ligand is residue 500): phenix.autobuild data=mydata.mtz model=mymodel.pdb omit_box_pdb=mymodel.pdb omit_res_start_list=500 omit_res_end_list=500 omit_chain_list=A composite_omit_type=sa_omit The output omit map (resolve_composite_map.mtz) looks great. My question is: What, exactly, is the "overall_best_denmod_map_coeff.mtz" in this case and how is it related, if at all, to the "resolve_composite_map.mtz"? Thanks in advance, Rebecca

1 0

phenix.refine v.1.3 vs 1.24
by Leo Sazanov 06 Oct '08

06 Oct '08

When refining the same (large) molecule in several different crystal forms at about 3.1 A resolution, I noticed that in two cases when experimental phase information is available, in phenix.refine-1.3 I get worse Ramachandran compared to phenix.refine-1.24 - about 2% less residues in most favored regions. In one case when there is no experimental phase information, there is no difference between two phenix versions. What could be the reason for that? These comparisons where done for cases when final RMSDs and R-factors are similar (and all RMSDs calculated in v.1.3), so automatic weights adjustment in v.1.3 should not have played much role. Adding to other people's comments, it would be useful to be able to switch this adjustment off, as sometimes one wants full control over final RMSDs, etc. Thanks! -- Dr. Leonid A. Sazanov Research group leader Medical Research Council Dunn Human Nutrition Unit Wellcome Trust / MRC Building Hills Road Cambridge CB2 0XY WEB: www.mrc-dunn.cam.ac.uk Tel: +44-1223-252910 Fax: +44-1223-252915

2 3

wxc_scale automatically doubled during the refinement
by yentingl＠gate.sinica.edu.tw 06 Oct '08

06 Oct '08

Dear phenix users, I've observed that in phenix 1.3 final if I specify wxc_scale the value is automatically doubled in every successive macrocycle. For example if I set wxc_scale=0.9 at the beginning, it becomes 1.8, 3.6, 7.2, 14.4 ... at macrocycle 2, 3, 4, 5 ... Is this normal? This was not found in phenix 1.3 rc4 on the same machine. Thanks! Yen-Ting

2 1

library values for H in phenix.refine and MOLPROBITY
by Pavel Afonine 06 Oct '08

06 Oct '08

Hi Jianghai, > Another thing about riding H atoms. As I said before, the bond > distance between riding H and its attached atoms is different from > phenix library (ccp4 mono library) to the library MOLPROBITY uses. I > think the distance from MOLPROBITY is longer. The result is that the > structure refined by phenix.refine has a not so good clash score. Is > there a way to keep the distance from phenix.reduce in phenix.refine? Yes, I remember you mentioned this in the past (may be even several times). And this is true: the distances in Mon.Lib. and internal library in Molprobity might be different. Theoretically, longer distances are more correct since they reflect the actual nuclear position (that one can observe in neutron diffraction experiment), while the X-rays show hydrogens shifted along the bond towards the atom they are bonded to. This is why some programs (like SHELX) use shortened distances for X-H bonds and some uses those obtained from neutron scattering. Overall, I agree that the dictionaries must be made consistent within the package - this is something to fix on PHENIX end. Pavel.

1 0

TLS refinement
by HUA YUAN 05 Oct '08

05 Oct '08

Dear Phenix community members, I have a molecular replacement solution refined agains a twinned 2.7 angstrom data to Rfree as 33%, with TLS and twin-law and others as default. The map looks good and shows extra map for my flavin ligand. Then I manually rebuild the model, fixing some obvious off-map residues and put a flavin molecule into the model. After this, I used the *def file from previous run to do another round of refinement. This time the Rfree increased to 36%. I realized that it has something to do with the TLS, isotropic and aniostropic B factor. However, I don't know exactly what's the reason and what to do at this stage. Any comments or suggestions? Should I do TLS refinement at the last step? Thanks and Best Wishes for all, Hua

2 1