Dear community,
ZoBio is looking for a senior protein crystallographer (M/F) with experience in
drug design. The ideal applicant has a demonstrable track record solving
protein-ligand structures and has worked with medicinal chemists to interpret
these results for drug discovery campaigns. The
Dear all
Just a note that the deadline to apply for this position is Sunday the 10th of
December 2017:
I am looking for a person with a structural biology/bioinformatics background
and software development experience to work on an exciting joint project with
Garib Murshudov’s group (MRC-LMB) t
Yes. Things are now fine using 2.7.11. I just had to play a bit with the Apple
Thunderbolt Display which was causing XQuartz to behave funny.
Problem solved.
Cheers
Roberto
On 4 Dec 2017, at 13:39, Engin Özkan
mailto:eoz...@uchicago.edu>> wrote:
Hi,
I have been using Xquartz 2.7.11 (the lat
Hi,
I have been using Xquartz 2.7.11 (the latest release) perfectly fine on
High Sierra. We did not have to downgrade to 2.7.8. CCP4i and Coot works
perfectly fine with XQuartz 2.7.11 on multiple iMacs and MacBook Pros we
have in the lab.
Best,
Engin
On 12/4/17 4:49 AM, Martin Montgomery
Dear All
update 047 is out and contains
* mmdb2
- fix for false duplicate sequence number error in case of short residue names
* panddas
- version 2.11.0
* edstats
- new version
* ccp4i2
- updates to molrep interface
* pointless
- 1.115, bug fix for multi-lattice data
* lorestr
- fix to ccp4
Dear Roberto,
You can install Xquartz 2.7.8 which is still available from the xquartz web
site. This was the last version where Xquartz behaved properly and it runs
fine on High Sierra.
Regards
MGM
Martin G Montgomery
Medical Research Council Mitochondrial Biology Unit
University of Cambrid
Solution: I noticed yesterday that XQuartz was behaving normally when my laptop
was not connected to the Apple Thunderbolt Display. Resetting the Thunderbolt
Display solved the problem.
Roberto
On 2 Dec 2017, at 00:04, Steiner, Roberto
mailto:roberto.stei...@kcl.ac.uk>> wrote:
Hi all
Since m
On 2 December 2017 at 00:31, Ivan Shabalin
wrote:
> Instead, we just used the search of the
> unit cell parameters in the PDB, which is much faster (but works only if the
> structure of this particular artifact in the same SpGr is in PDB! otherwise,
> one should use ContaMiner or similar service
