- phenixbb - phenix-online.org

Raw data.....
by Jrh 24 Oct '15

24 Oct '15

Good morning Tim, Overnight thoughts: Another aspect that seems to me to be accelerating now is the use of the diffuse scattering in MX structure AND dynamics analysis. There are several really nice papers in the last year. I post this on the Phenixbb because the drive forward on this is linked to Phenix. My point obviously is that this involves the whole diffraction pattern. I recognise that raw diffraction data measured for 'conventional crystal structure analysis', to use a term, may not be ideal but nevertheless these papers show that analysis is developing and so, at the Beamline, if diffuse scattering is evident it seems to me not so burdensome to add a data sweep with stronger exposures and a smaller beam (ie to minimising obscuring the diffuse by the Bragg). Also, just to mention, to add to my last message to you, I could mention specifically the very important initiative taken by Wladek Minor at Virginia within the US Big Data new funding. He already has a portal to 2800 raw data sets. At Utrecht Loes Kroon Batenburg and Toine Schreurs have shown what can be done with personal weblinks to raw data these last three years. And of course the US Structural Genomics centres pioneered much of this too. Greetings, John Emeritus Prof John R Helliwell DSc_Physics FInstP FRSC FRSB Fellow of the ACA Emeritus Member of the British Biochemical Society School of Chemistry, University of Manchester, M13 9PL, UK.

1 0

Positions at the NKI - Amsterdam
by Anastassis Perrakis 24 Oct '15

24 Oct '15

Dear all, Three positions are available in the group of Anastassis (Tassos) Perrakis at the Netherlands Cancer Institute. We are looking for: 1. A post-doctoral scientist to work on the European Horizon2020 project iNEXT (http://www.inext-eu.org <http://www.inext-eu.org/>), on collaborative research activities aiming to develop, establish and apply biophysical methodologies for enabling ligand and fragment-based inhibitor discovery (in collaboration with the teams of Jose-Antonio Marquez at EMBL-Grenoble and Frank von Delft at Diamond) and for studying macromolecular interactions in vitro and in vivo (in collaboration with the group of Jan Ellenberg at Heidelberg). The research theme for applying and testing these technologies will be in the area of mitotic kinases and in particular on the study of their regulatory/localisation domains (see Hiruma et al, Science 2015 and Nijenhuis et al, J Cell Biol 2013). 2. A scientific programmer to help further develop our ProteinCCD Java application (http://xtal.nki.nl/ccd <http://xtal.nki.nl/ccd>, Mooij et al, Nucleic Acids Res 2009) and the PDB_REDO web server (http://xtal.nki.nl/pdb_redo <http://xtal.nki.nl/pdb_redo>; Joosten et al, IUCrJ 2014), and deploy them in virtual research environments and cloud-based systems, within the WestLife Horizon2020 e-Infrastructures project. The candidate should also help maintain and further develop the (C++) code behind the PDB_REDO rebuilding applications (Joosten et al, Bioinformatics 2011; Joosten et al Acta Crystallogr D 2012). 3. A scientist with a background on Cheminformatics or (Structural) Bioinformatics, to develop further the PDB_REDO pipeline (see above) to handle automated ligand and fragment placement, refinement and validation pipelines, and to pro-actively participate in the scientific and technical development of PDB_REDO. The Netherlands Cancer Institute (http://www.nki.nl <http://www.nki.nl/>) is a center of excellence with a high standard of biological research and an interactive international atmosphere. It is located in Amsterdam, with all its cultural amenities, close to the Schiphol airport. The group of Tassos Perrakis, which also hosts the team of Robbie Joosten working in the PDB_REDO project, is closely associated with the neighbouring group of Titia Sixma. Both groups have an interest in structural studies coupled to functional analysis, combined with activities in method development for structural biology. Our department also hosts the "Protein Facility" with equipment that includes high throughput crystallisation and crystal visualisation robotics, an X-ray facility, Biacore surface plasmon resonance, isothermal titration calorimetry (ITC), microscale thermophoresis, thermal shift analysis, multi-angle laser light scattering (MALLS), versatile systems for fluorescence based equilibrium and transient state kinetics analysis (a versatile plate reader and stopped-flow), and operational facilities for E.coli, insect cells and mammalian cells based protein expression and purification. Computational facilities are locally available. The groups also share equipment and office space, and together with the group of Thijn Brummelkamp create a lively and highly interactive research environment. Applicants should write an e-mail including a CV, a short letter of motivation and names and addresses of scientists willing to provide a reference to a.perrakis(a)nki.nl <mailto:[email protected]>. Tassos Anastassis (Tassos) Perrakis, Principal Investigator / Staff Member Department of Biochemistry (B8) Netherlands Cancer Institute, Dept. B8, 1066 CX Amsterdam, The Netherlands Tel: +31 20 512 1951 Fax: +31 20 512 1954 Mobile / SMS: +31 6 28 597791

1 0

Re: [phenixbb] [ccp4bb] Tantalum anomalous signal of a low-resolution SAD dataset with lattice-translocation disorder
by Christian Roth 21 Oct '15

21 Oct '15

Hi, difficult to say why it doesn't work. Generally as mentioned already automatic model buildíng will most likely fail at this resolution. However why do you think your sites are wrong? Ta-cluster are regular compounds and the sites should fit with the geometry of the cluster at least. Anyway, molecular replacement using anomalous differences and the cluster as search model might work in that case as well, if direct experimental phasing fails. Cheers Christian Am 21.10.2015 um 05:19 schrieb Shun Liu: > Dear CCP4 colleagues, > > We are working on a Ta6Br14 cluster-SAD dataset (4.3 angstroms) with lattice-translocation disorder (with a total Rmerge of 0.16). Both SHELXC and Xtriage gave the similar positive result about the anomalous signal (See below). > > ------------------------------------------------------------------------------------------------- > Resl. Inf. 9.58 7.61 6.65 6.04 5.61 5.27 5.01 4.79 4.61 4.45 4.31 > N(data) 1427 1410 1410 1409 1385 1452 1367 1399 1367 1395 1385 > <I/sig> 76.3 52.1 26.7 13.7 8.7 6.1 5.1 5.0 3.9 2.7 1.8 > %Complete 98.8 99.9 100.0 99.9 100.0 100.0 100.0 99.9 99.7 99.6 95.8 > <d"/sig> 11.67 9.67 6.12 3.73 2.50 1.59 1.21 0.99 0.84 0.79 0.68 > ------------------------------------------------------------------------------------------------ > unused: - 49.7669 [ 0/29 ] > bin 1: 49.7669 - 9.2629 [3086/3100] 0.8212 > bin 2: 9.2629 - 7.3599 [3031/3031] 0.7689 > bin 3: 7.3599 - 6.4318 [3073/3073] 0.5380 > bin 4: 6.4318 - 5.8447 [3071/3075] 0.2933 > bin 5: 5.8447 - 5.4263 [3054/3054] 0.1230 > bin 6: 5.4263 - 5.1067 [3070/3071] 0.0363 > bin 7: 5.1067 - 4.8512 [3038/3039] 0.0126 > bin 8: 4.8512 - 4.6402 [3028/3048] 0.0074 > bin 9: 4.6402 - 4.4617 [2955/3037] 0.0021 > bin 10: 4.4617 - 4.3078 [2730/3059] 0.0000 > unused: 4.3078 - [ 0/0 ] > -------------------------------------------------------------------------------------------------- > The Tantalum sites and the initial map seem ambiguous, with which automatic model-building failed. > I am wondering whether the lattice-translocation disorder of the dataset impacts the reliability of the anomalous signal, tantalum sites and the initial map. If it does, how can we decrease its impact? If it doesn't, is it possible to find the accurate Ta sites and generate an interpretable map suitable for model-building with this dataset? (After all, it has been reported that Ta sites can be found at 6A resolution.) > > Any suggestion and comment will be highly appreciated! > > Best, > Shun >

1 0

Tantalum anomalous signal of a low-resolution SAD dataset with lattice-translocation disorder
by Shun Liu 21 Oct '15

21 Oct '15

Dear Phenix colleagues, We are working on a Ta6Br14 cluster-SAD dataset (4.3 angstroms) with lattice-translocation disorder (with a total Rmerge of 0.16). Both SHELXC and Xtriage gave the similar positive result about the anomalous signal (See below). ------------------------------------------------------------------------------------------------- Resl. Inf. 9.58 7.61 6.65 6.04 5.61 5.27 5.01 4.79 4.61 4.45 4.31 N(data) 1427 1410 1410 1409 1385 1452 1367 1399 1367 1395 1385 <I/sig> 76.3 52.1 26.7 13.7 8.7 6.1 5.1 5.0 3.9 2.7 1.8 %Complete 98.8 99.9 100.0 99.9 100.0 100.0 100.0 99.9 99.7 99.6 95.8 <d"/sig> 11.67 9.67 6.12 3.73 2.50 1.59 1.21 0.99 0.84 0.79 0.68 ------------------------------------------------------------------------------------------------ unused: - 49.7669 [ 0/29 ] bin 1: 49.7669 - 9.2629 [3086/3100] 0.8212 bin 2: 9.2629 - 7.3599 [3031/3031] 0.7689 bin 3: 7.3599 - 6.4318 [3073/3073] 0.5380 bin 4: 6.4318 - 5.8447 [3071/3075] 0.2933 bin 5: 5.8447 - 5.4263 [3054/3054] 0.1230 bin 6: 5.4263 - 5.1067 [3070/3071] 0.0363 bin 7: 5.1067 - 4.8512 [3038/3039] 0.0126 bin 8: 4.8512 - 4.6402 [3028/3048] 0.0074 bin 9: 4.6402 - 4.4617 [2955/3037] 0.0021 bin 10: 4.4617 - 4.3078 [2730/3059] 0.0000 unused: 4.3078 - [ 0/0 ] -------------------------------------------------------------------------------------------------- However, the tantalum sites we found and the initial map seem ambiguous, with which automatic model-building failed. I am wondering whether the lattice-translocation disorder of the dataset impacts the reliability of the anomalous signal, tantalum sites and the initial map. If it does, how can we decrease its impact? If it doesn't, is it possible to find the accurate Ta sites and generate an interpretable map suitable for model-building with this dataset? (After all, it has been reported that Ta sites can be found at 6A resolution.) Any suggestion and comment will be highly appreciated! Best, Shun

5 4

Queueing system commands for parallel Phenix/Rosetta jobs
by Yonglin Hu 21 Oct '15

21 Oct '15

Hello All, We have setup a cluster with several executing nodes and we would like to run our Phenix/Rosetta molecular replacement jobs on the cluster. In the Job Control screen, I put "qsub -q all.q -o $HOME/log1 -e $HOME/log1" as command to use to run multiple jobs. But I am not sure what I should use for "queueing system commands". We are using SGE as the queueing system on our cluster. Any help would be greatly appreciated! Yonglin Hu

2 1

on cif file
by Smith Lee 20 Oct '15

20 Oct '15

Dear All, My protein containing the ADP-AlF3-Mg. In the protein ADP-AlF3-Mg should be very close to each other so that they look like the ATP binding with the Mg. I have prepared the ADP.cif and the ALF3.cif, and have merged the 2 cif files with elbow.join_cif_files. However when I run phenix.real_space_refine with the merged cif file, there was a tendency that ADP, ALF3 and Mg separated from each other based on the map density, which seems did not comply with the prior knowledge on that ADP-AlF3-Mg should occupies the space of ATP-MG. Will you please advice how to have ADP-AlF3-Mg occupies the space of ATP-MG rather than separated by the refine? Best regards. Smith

1 0

Re: [phenixbb] How to convert XDS_ASCII.HKL to MTZ
by Whitley, Matthew J 19 Oct '15

19 Oct '15

Hi Murpholino, I’m not sure if your Phenix commands are correct, but you might try using the program that comes natively with XDS for converting between file formats. That program is XDSCONV. (As a side note, I think that some of the XDSCONV functions require CCP4 to be installed, so if you don’t have CCP4 installed you might need to stick to converting with Phenix.) You can find step by step instructions for generating an MTZ file from XDS output under the “Typical Use” heading here: http://strucbio.biologie.uni-konstanz.de/xdswiki/index.php/Xdsconv More info about XDSCONV: http://homes.mpimf-heidelberg.mpg.de/~kabsch/xds/html_doc/xdsconv_parameter… Good luck! Matthew On Oct 19, 2015, at 12:16 PM, <phenixbb-request(a)phenix-online.org> <phenixbb-request(a)phenix-online.org> wrote: > > Message: 5 > Date: Mon, 19 Oct 2015 11:16:17 -0500 > From: Murpholino Peligro <murpholinox(a)gmail.com> > To: PHENIX user mailing list <phenixbb(a)phenix-online.org> > Subject: [phenixbb] How to convert XDS_ASCII.HKL to MTZ > Message-ID: > <CAMdBu0Uejh0k+Wih1KaF+c=FRJ3fKg+LhQrfuGhUs1tJ8x8HwQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Just want to be sure. > I want to generate the mtz file for refinement. The last step of XDS leaves > me with intensities and space group 89. So I need > > phenix.reflection_file_converter --generate-r-free-flags > --write-mtz-amplitudes --mtz_root_label=FOBS --mtz=d01.mtz > --change-to-space-group=96 XDS_ASCII.HKL > > Is this right? > > Thanks again >

2 2

How to convert XDS_ASCII.HKL to MTZ
by Murpholino Peligro 19 Oct '15

19 Oct '15

Just want to be sure. I want to generate the mtz file for refinement. The last step of XDS leaves me with intensities and space group 89. So I need phenix.reflection_file_converter --generate-r-free-flags --write-mtz-amplitudes --mtz_root_label=FOBS --mtz=d01.mtz --change-to-space-group=96 XDS_ASCII.HKL Is this right? Thanks again

1 0

refinement of coordinated ions
by Irina PROKHOROVA 18 Oct '15

18 Oct '15

Hello, I have many Osmium ions in my structure. They have 6 coordinated ammonium groups and I would like to refine the B-factors for them: one B-factor for Os in each residue and one B-factor for all 6 ammonium groups in each residue. For this I have chosen *group_adp with following syntax adp { group_adp_refinement_mode = one_adp_group_per_residue \ two_adp_groups_per_residue *group_selection group = chain O and element Os group = chain O and element N } I wanted to refine only B-factor for Osmiums in this refinement. To avoid the bias from previously refined values of B-factor I presetted B-factors for all Osmiums to 50. As a result I got the change of B-factors for all residues in the model to the same value (which probably means that all model was refined as one group) and R-free increased from 0.25 to 0.34. What should be the correct syntax for this refinement? Should I also refine ions coordinates for a good refinement of B-factors? Irina

2 1

Fw: on phenix.real_space_refine
by Smith Lee 18 Oct '15

18 Oct '15

Dear Pavel, On Oct 9, 2015 I have e-mailed to you my experience with 1.9-1692 and version 1.10 (and 1.10.1) on phenix.real_space_refine. Today I just completed another protein phenix.real_space_refine. For the following comparison runs, the initial model same, the map same, all 5 macro_cycles default run. For version 1.10.1, the results were as following, Map CC (whole unit cell)： 0.672Map CC （around atoms）： 0.761rmsd （bonds): 0.01rmsd (angles): 1.55All-atom clahscore: 39.27Ramachandran outlier: 0.98%Ramachandran allowed: 12.71%Ramachandran favoured: 86.31%Rotamer outliers: 0.91%C-beta deviations: 0 For version 1.9-1692, the results were as following, Map CC (whole unit cell)： 0.645Map CC （around atoms）： 0.687rmsd （bonds): 0.0071rmsd (angles): 1.15All-atom clahscore:16.88Ramachandran outlier: 2.00%Ramachandran allowed: 6.23%Ramachandran favoured: 91.77%Rotamer outliers: 0.05%C-beta deviations: 0 For the version 1.10.1 phenix.real_space_refine, the most unacceptable was on the clashscore, the whole refine process seems did not care on the clashcore refine at all. I am looking forward to getting an explanation from you on the causes of the difference for phenix.real_space_refine for the 2 versions, and the possible strategy we can take to eliminate the difference to get the acceptable results. Best regards. Smith On Friday, October 9, 2015 12:52 AM, Smith Lee <smith_lee123(a)yahoo.com> wrote: Dear Pavel， As I have told you, I have tried phenix.real_space_refine for 2 protein with version 1.9-1692 and version 1.10 (and 1.10.1) for many times, with cif or without cif, with or without annealing. The general feedback was that the version 1.9-1692 was much much better for the final analysis of the PDB given at the end of the run of the phenix.real_space_refine. Especially for clashing score, version 1.9-1692 can gave acceptable results (below 20 or around 20), but the clashing score given by the above 2 new versions of phenix.real_space_refine was very high (around 50 or 100). For C-beta deviations, the output by 1.9-1692 was also much better Before I have tried the other nightly built versions of phenix.real_space_ refine between version 1.9-1692 and version 1.10 (and 1.10.1) , all I gave acceptable output analysis (something like the Molprobity analysis at the end of the run). Thus may I ask the reason you have version 1.10 (and 1.10.1) phenix.real_space_refine was because you have realized that the result given by version 1.9-1692 was too satisfactory? One direct concern of me was that you have recommended not to use the old version phenix. But I cannot get the satisfactory result with the new version phenix.real_space_refine. The other concern of me was that, I have noticed there were publications In Nature and Science which wrote they use phenix.real_space_refine to got the results in Nature and Science. The Phenix they used should be the versions earlier than version 1.10. Considering what I mentioned above, the Nature and Science results may be not so correct, if new version of phenix was considered as much better than the old version. Thus am I the only user who communicated with you on the high clashing score given by the new version of phenix？Can you give some comments on what I mentioned above on the high clashing score given by the new version phenix.real_spac_refine? Best regards. Smith

2 1