- phenixbb - phenix-online.org

"unlimit" command with Phenix GUI -unlimit: descriptors: Can't remove limit (Invalid argument)
by hari jayaram 03 Apr '08

03 Apr '08

Hi I am giving new to Phenix and the Phenix GUI. For starters I am trying to run the prime and switch strategy in Phenix. I know all my inputs are fine (see below) but the program aborts ( GUI turns red ) after a few seconds. I checked the resolve.com file in the directory and it has a command "unlimit" which in Leopard causes the following output to be echoed to the stdout "unlimit: descriptors: Can't remove limit (Invalid argument)" Once I deleted the unlimit command I can run the script just fine from a shell. My question is how can I tweak the Phenix GUI so that I dont have to run everything from the shell by manually editing the resolve.com file. The script that stops the GUI is reproduced here. Thanks for your help Hari Jayaram Postdoc , Brandeis University script: #!/bin/csh setenv SOLVEDIR /usr/local/phenix-1.3b-rc6/solve_resolve/ext_ref_files setenv SOLVEBIN /usr/local/phenix-1.3b-rc6/build/mac-intel-osx/solve_resolve/exe # setenv CCP4_OPEN UNKNOWN setenv SYMOP $SOLVEDIR/symop.lib unlimit # $SOLVEBIN/resolve<<EOF access_file mirima.dat labin FP=F_s3-3 FC=FC PHIC=PHIC FOM=FOM FWT=FWT hklin resolve_input.mtz mask_cycles 5 minor_cycles 10 hklout testpms-resolve.mtz no_build prime_and_switch EOF unlimit returns------------> [mango:hj/s3-3/prime_switch] hari% unlimit unlimit: descriptors: Can't remove limit (Invalid argument)

1 0

Crystallographic Postdoctoral Research Position - Berkeley, USA
by Paul Adams 02 Apr '08

02 Apr '08

A postdoctoral research position is available immediately to work on challenging problems in structural biology: Postdoctoral Researcher Job ID: 21615 Division: Physical Biosciences Date Opened: 3/28/2008 This postdoctoral position will study the structure and function of macromolecular complexes and enzymes using X-ray crystallographic methods. This position will be joint between the Center for Protein Folding Machinery (proteinfoldingcenter.org) and the Joint BioEnergy Institute (www.jbei.org). The biological systems to be studied will include: Type-II chaperonins responsible for the refolding of unfolded proteins in archeal and mammalian cells, Glycosyl transferases responsible for the synthesis of hemicellulose in plants, and Novel glycosyl hydrolases that are able to breakdown cellulosic material for biofuels production. The candidate will have experience with using crystallographic methods to study macromolecules; robotic hardware for performing crystallization trials and imaging trays are available. Crystals will be characterized and data collected using the beamline resources of the Berkeley Center for Structural Biology at the Advanced Light Source. Essential: Primary duties and responsibilities will include using robotic hardware to perform screens for crystallization conditions. Optimization of crystallization conditions. Biophysical characterization of protein samples using standard techniques, such as dynamic light scattering. Characterization of crystals using the Berkeley Center for Structural Biology beamlines at the Advanced Light Source. Collection and analysis of diffraction data, model building and structure refinement. Extensive email and verbal interaction with other researchers. Marginal: Use of small angle X-ray scattering methods to analyze macromolecular complexes in solution. Essential: Ph.D. or equivalent in a scientific discipline, preferably structural biology, biology, or chemistry. Demonstrated experience of scientific research using crystallographic methods. Experience with crystallization methods. Solid interpersonal skills and the ability to work in a team environment are critical. Ability to communicate with a broad range of researchers. Marginal: Experience with the use of small angle scattering methods. Familiarity with robotic hardware for crystal growth. NOTE: This is a one year Term appointment with the possibility of renewal under the same terms and conditions, contingent upon continued funding and availability of work. Lawrence Berkeley National Laboratory is a world leader in science and engineering research, with 11 Nobel Prize recipients over the past 75 years, and 59 present members of the National Academy of Sciences. LBNL conducts unclassified research across a wide range of scientific disciplines and hosts four national user facilities. AA/ EEO employer committed to the development of a safe and diverse workforce. Learn more at http://www.lbl.gov. For more information about the Center for Protein Folding Machinery visit: http://proteinfoldingcenter.org/ and the Joint BioEnergy Institute visit: http://www.jbei.org/. For more information about the Berkeley Center for Structural Biology visit: http://bcsb.lbl.gov/ To apply: visit http://cjo.lbl.gov/ and search for the job number 21615. Please see http://cjo.lbl.gov/app_instr.html for details of how to apply. -- Paul Adams Deputy Division Director, Physical Biosciences Division, Lawrence Berkeley Lab Adjunct Professor, Department of Bioengineering, U.C. Berkeley Vice President for Technology, the Joint BioEnergy Institute Head, Berkeley Center for Structural Biology Building 64, Room 248 Tel: 510-486-4225, Fax: 510-486-5909 http://cci.lbl.gov/paul Lawrence Berkeley Laboratory 1 Cyclotron Road BLDG 64R0121 Berkeley, CA 94720, USA. --

1 0

TLS, B factors, phenix and refmac
by Mischa Machius 01 Apr '08

01 Apr '08

Hi - Prompted by the recent discussions on B values, TLS refinement and differences between Phenix and refmac, we looked into these matters in more detail. We found that the crux of the problem lies in the fact that TLS and B value refinements are usually decoupled. We have developed a formalism that rolls both TLS and B value refinement into one. Phenix and refmac were modified to carry out the calculations, and the outputs from both programs were made compatible to allow proper comparison of the results. We found that the stability of the refinements is now vastly improved. More importantly, however, due to the reduced number of parameters, these calculations can be carried out to resolutions of 7 Å with meaningful representations of indiviual, anisotropic atomic displacement parameters. This low-resolution limit required reformulating the calculation of Wilson B values, but that is only a minor aspect of our treatment that can be neglected. The new, combined procedure for the simultaneous refinement of TLS/B is called 'TBS' refinement, reflecting all required components: Translation, Bibation, Screw. Interestingly, the ‘T’ component is fairly insensitive to input parameters, whereas the overall quality of the refinement is greatly dependent on the ‘B’ component. The more emphasis is put on ‘B’, the more convincing the results. There is a limit, though. At very high levels of ‘B’, the so-called ‘bibacity limit’, the refinement becomes very unstable, leading to inversion in severe cases. Seasoned crystallographers familiar with the concepts can successfully push the procedure to quite high 'B limits', whereas less experienced practitioners should follow the protocols very carefully. Please contact us for any details. Best - MM -------------------------------------------------------------------------------- Mischa Machius, PhD Associate Professor UT Southwestern Medical Center at Dallas 5323 Harry Hines Blvd.; ND10.214A Dallas, TX 75390-8816; U.S.A. Tel: +1 214 645 6381 Fax: +1 214 645 6353

2 1

Question about anisotropic refinement of selected waters during automatic solvent update
by Schubert, Carsten [PRDUS] 01 Apr '08

01 Apr '08

Hi, I am trying to refine a couple of waters in a structure anisotropically in the latest version of CCI-Apps (Feb-08) . The selection is: refine.adp.anisotropic = "chain W and (resid 25 or resid 54)" The refinement works fine if "main.ordered_solvent = False". When I enable "main.ordered_solvent" the refinement fails with: "Sorry: Bad (empty or mixed) selection in adp_individual.aniso" during the first update of the solvent in macrocycle 1. A workaround is easy to implement, but I think this kind of scheme should work. Although it has all kinds of tricky implication for the downstream handling of the selection if the residues/waters in questions are deleted.... Cheers, Carsten

1 0

gnomebreakpad error
by shivesh kumar 01 Apr '08

01 Apr '08

Dear all, We are trying to install phenix in Fedora Core 8.While installing it is showing the following error- Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory Please suggest what is wrong or missing. Thanx in advance. Shivesh

2 1

tls definitions
by PhilEvans 01 Apr '08

01 Apr '08

Sorry if this has been answered before, but I've only just joined this BB In phenix.refine, I'm trying to make TLS groups consisting of multiple chains, eg refinement.refine { strategy=individual_sites+tls+individual_adp adp { tls="chain A and chain B and chain Z" tls="chain C and chain D and chain Y" } } but it doesn't work: what should I do? Phil ================== Extract refinement strategy and selections ================= individual_sites = True rigid_body = False individual_adp = True group_adp = False tls = True individual_occupancies = False group_occupancies = False group_anomalous = False size = 1356 n_use = 1356 n_use_u_iso = 1356 n_use_u_aniso = 0 n_grad_site = 0 n_grad_u_iso = 0 n_grad_u_aniso = 0 n_grad_occupancy = 0 n_grad_fp = 0 n_grad_fdp = 0 n_anisotropic_flag = 0 total number of scatterers = 1356 Sorry: Empty selection in adp_tls selection.

4 4

question about refinement in a SAD data set
by Pascal EGEA 31 Mar '08

31 Mar '08

Dear All, I am trying to refine a seleno met structures at 2.2 Ang resolution I used Auto_Sol and Auto_Build and it worked great since it found the 4 semets with occupancies of about 0.85 to 0.95. and most of the model was built. Phenix generated an exptl_fp_phases.mtz with the Rfree flag. so far so good. I have a couple of questions because I am not quite to understand what phenix.refine is doing at this stage? 1- If I refine using the experimental phases mtz file generated by the auto_sol run, the occupancies for the seleniums change quite a bit and they drop to 0.75-0.80 and that does not sound right to me? What am I doing wrong? should I fix occupancies for the seleniums to the values evaluated at the end of the auto_build run (Rfree=27/ Rfac=24?) 2- This experimental phases mtz file contains FP and the HL coefficients for the phases but there are no more anomalous differences. If I try to refine f' and f" using it, Phenix tells me that there is no anomalous information contained in this file. So how do you refine f' and f"? and what is the practical reason for this AutoSol generated mtz file to not contain the anomalous differences that were used to locate the seleniums. Thanks in advance for the explanation Pascal F. Egea, PhD Post Doctoral Researcher University of California San Francisco Department of Biophysics and Biochemistry Robert Stroud Laboratory pascal(a)msg.ucsf.edu

3 2

Getting Residual Bs
by Frank von Delft 30 Mar '08

30 Mar '08

Hi Pavel, picking up on your point earlier: > and that there are tools available from both ends (phenix, ccp4) to easily > go from partial to total and back. What *is* the tool in phenix to from total to partial? I suspect it's one of the phenix.pdbtools adp commands, but the documentation is a bit sparse on that program. Cheers phx P.S. Pavel, despite my rant today: great program! :-)

2 1

Re: [phenixbb] refmac,tlsanl vs TLS, B and anisou
by Paul Adams 30 Mar '08

30 Mar '08

Some comments: - We (the PHENIX developers) are working with the PDB to come up with a more streamlined deposition of TLS information for PHENIX. There are some other issues that need to be resolved first that have slowed this down a little. - I am in agreement with George (not unusual). - As far as I remember Garib was supportive of the idea of no longer depositing residual B-factors in the atomic iso-B column. - What phenix.refine writes in the PDB file is almost exactly the same as you would get by running TLSANL on a REFMAC PDB file. - It is my understanding that the EBI runs TLSANL on REFMAC deposited PDB files to extract the ANISOU records so that R-factors can be calculated. It would seems that this information is then discarded. [I could be mistaken about this whole process though] - Allowing ANISOU records only when atomic anisotropic displacement parameters have been refined seems very restrictive. There may be multiple ways to arrive at anisotropic displacements other than the traditional method (TLS is one, George mentioned TLS restraints instead of constraints, and we have some ideas about ADP refinement that would also result in anisotropic displacements). - It is good to remember that TLS refinement is constrained anisotropic displacement parameter refinement. - If we want bioinformaticians to analyze our structures then we should be writing something in the iso-B column that they can understand - I favour the iso-B equivalent of the total atomic B-factor. This I assume they can handle. I very much doubt that anyone other than a crystallographer will go to the trouble of extracting the TLS information and recalculating atomic displacements. - The biologists looking at structures from the PDB do not care about TLS or ANISOU records. If they choose to look at anything it will be the iso-B column (probably by colouring the atoms by B-factor in a display program). I'd like to give them a fighting chance of seeing something meaningful such as the iso-B equivalent of the total atomic B-factor rather than a residual B-factor (which has no meaning to them). - I will not be holding my breath waiting for any of the popular display programs to start interpreting TLS header information. - I agree that it is best for everyone if we have some clear standards for deposition and tags that make it clear to anyone looking at files from the PDB what is meant by the contents. The PDB is very aware of this and I expect things to be straightened out fairly soon in collaboration with the developers of phenix.refine and REFMAC. -- Paul Adams Deputy Division Director, Physical Biosciences Division, Lawrence Berkeley Lab Adjunct Professor, Department of Bioengineering, U.C. Berkeley Vice President for Technology, the Joint BioEnergy Institute Head, Berkeley Center for Structural Biology Building 64, Room 248 Tel: 510-486-4225, Fax: 510-486-5909 http://cci.lbl.gov/paul Lawrence Berkeley Laboratory 1 Cyclotron Road BLDG 64R0121 Berkeley, CA 94720, USA. --

1 0

Rant: B vs TLS, anisou, and PDB headers
by Frank von Delft 29 Mar '08

29 Mar '08

Just spent an hour trawling docs, BBs (recent threads) and logs to figure out what the hell my B column is telling me (phenix vs refmac vs pdb). Oh dear, it's a disaster area, quite Heissenbergian... the most important number (uncertainty) is itself unknowable: * Phenix writes total ADP, Refmac writes residual ADP. * Refmac writes a remark -- pdbdep strips it (!?!!?) * Phenix writes no remark (I think?) * Refmac writes different numbers to TLSOUT and pdb header (trace of S) * Phenix duplicates the information in header (TLS) and ANISOU cards, the latter thereby making implicit what should be explicitly stored: how the ADPs are connected. * Refmac, given phenix TLS-originating ANISOUs, flattens them into first number, but does not remove them * PDB does not care I'd like to appeal for an urgent consensus -- which should be unusually easy, since it involves only two programs and one repository. My strong recommendation, from first principles of usability: residual B into ATOM, no TLS in ANISOU, and the rest into the header. I know it's religious, but here's the reasoning: ==> the end-user looks *locally*, that's what ATOM and ANISOU are for. ==> global stuff (cell, symmetry, NCS, and yes, TLS) belongs in the header -- as do what's still missing, namely twinning, lattice modulations, scatter factors, and restraints. Yes, we crystallographers want easy B-factor stats (phenix's reason), but then lets fix the analysis programs to look at the header as well. And yes, packing and internal motions (TLS) are all very important for analysis - but that is why it should be explicit in the header, so that graphics tools have easy access to it. End rant (but not end hope :) phx.

3 6