Re: [ccp4bb] ccp4-6.1.0: iMosflm libtermcap.so.2 error - SOLVED

2008-12-22 Thread Winter, G (Graeme)
Dear Victor and BB, For reasons which are opaque at best some linux distributions name this file libtermcap.so, and some libtermcap.so.2. Evidently the binary worked fine on the collection we tested. Fortunately there is a relatively simple if inelegant fix: cd $CLIB ln -s

Re: [ccp4bb] refmac 5.5.063 vs. 5.5.066

2008-12-22 Thread Stein, ND (Norman)
Just to add to that, Windows users can download a Refmac 5.5.0070 binary from the CCP4 prerelease page. www.ccp4.ac.uk/prerelease Norman Norman Stein CCP4 Daresbury Laboratory -Original Message- From: CCP4 bulletin board [mailto:ccp...@jiscmail.ac.uk] On Behalf Of Pavol Skubak Sent:

Re: [ccp4bb] Bug in Sketcher?

2008-12-22 Thread Winter, G (Graeme)
Dear James, I have just tried this on a linux binary installation and it appeared to work fine. Please could you tell me what platform you are running on? Many thanks, Graeme CCP4 Support Team -Original Message- From: CCP4 bulletin board on behalf of James M. Vergis Sent: Sun

Re: [ccp4bb] Transferring a Free R set.

2008-12-22 Thread Eleanor Dodson
Alun R. Coker wrote: Hi All, I have been in the habit of transferring my initial free R assignments to any new data sets or to isomorphous data sets such as substrate complexes. Although theoretically this is necessary to obtain a valid free R many of my colleagues maintain that this is

Re: [ccp4bb] Refmac and MSE?

2008-12-22 Thread Eleanor Dodson
I also see such peaks. I have assumed it is because the default in REFMAC is to use the CuKa SE formfactor, which should be modified at shorter wave lengths. (Solution - copy $C:IBD/atomsf.lib and modify Se c to c(CuKa) - f' for your wavelength.. then assign ATOMSF myversion/atomsf.lib in the

[ccp4bb] LSQKAB, version 6.0 vs version 6.1

2008-12-22 Thread Jose M de Pereda
Dear colleagues, While using LSQKAB I have encountered what it seems a different behavior between version 6.1 and 6.0. If I superpose two structures with LSQKAB version 6.1 (included in CCP4-6.1.0), residues with alternative conformations are not included for the calculations. This is an

Re: [ccp4bb] LSQKAB, version 6.0 vs version 6.1

2008-12-22 Thread Jose M de Pereda
Hi Tim, Not a stupid question at all. This is how I came to think that version 6.0 uses atoms with alternative conformations: If I do the same superposition (with a pdb file that contains alternative conformations) with LSQKAB version 6.0 and 6.1: 1) Version 6.0 reports 110 atoms to be

Re: [ccp4bb] ccp4-6.1.0: iMosflm

2008-12-22 Thread William G. Scott
Hi Harry et al: Well, it it makes you feel any better, imosflm works great for me on ubuntu ibex: http://diablo.ucsc.edu/~wgscott/debian/imosflm_xubuntu_ibex.png I just lost my imosflm virginity at the synchrotron a few nights ago (they have it working or rh at SSRL). If it helps

[ccp4bb] A primer on linux shared libs [was: ccp4-6.1.0: iMosflm libtermcap.so.2 error - SOLVED]

2008-12-22 Thread Ethan A Merritt
On Monday 22 December 2008, Winter, G (Graeme) wrote: Dear Victor and BB, For reasons which are opaque at best some linux distributions name this file libtermcap.so, and some libtermcap.so.2. This much I can explain, and since it is useful knowledge for tracking down linux library

[ccp4bb] Off topic question

2008-12-22 Thread Gina Clayton
Hi CCP4ers Apologies for the off topic... I have been trying to get hold of L-ribulose-5-phosphate (D- is readily available). Does anyone know where I can get such a compound? Thanks in advance for any suggestions and Merry Xmas! Gina

Re: [ccp4bb] ccp4-6.1.0: iMosflm

2008-12-22 Thread William G. Scott
Hi Tim: I know, I've been through it with them too, but neither debian nor ccp4 want to change, so it was easier just to roll my own bltwish package, being the natural born diplomat that I am. As for the debian maintainer, it seems kind of arbitrary to remove an executable that builds

Re: [ccp4bb] LSQKAB, version 6.0 vs version 6.1

2008-12-22 Thread Borhani, David
I think the LSQKAB change at Line 291(old)/Line 300(new) DOES introduce new and possibly incorrect logic. I haven't looked at all the code, but this one change does seem to substitute a check that chain, residue number, and atom name (only 3 characters; incorrect) match [OLD] for a check that