Hi Paul, It’s r4833 - stand alone version for 10.9 distributed via Bill Scott’s page.
You’re absolutely right - when I run cprodrg on the command line I get the same error - I’ll redirect my query to the CCP4BB. Thanks, Oliver. On Nov 25, 2013, at 6:49 AM, Paul Emsley <[email protected]> wrote: > On 25/11/13 03:46, Oliver Clarke wrote: >> Hi all, >> >> I get the GUI error “something went wrong running cprodrg” when I try to >> view a ligand in LIDIA - I’m guessing some incompatibility between coot and >> the version of cprodrg distributed with CCP4 6.4.0? I am running the latest >> coot nightly build (0.8-pre r4833) on Mac OS X 10.9, using CCP4 with all >> current updates installed. The console output is reproduced below. Thanks in >> advance for any help/advice! >> >> Oliver. >> >> (info-dialog "Something went wrong running cprodrg >> >> (write-pdb-file 8 "coot-ccp4/prodrg-tmp-68067-xyzin.pdb") >> :<B><FONT COLOR="#FF0000"><!--SUMMARY_BEGIN--> >> forrtl: severe (180): SIGBUS, bus error occurred >> Image PC Routine Line Source >> cprodrg 00000001000013FC Unknown Unknown Unknown >> cprodrg 00000001000011AC Unknown Unknown Unknown >> cprodrg 0000000100001164 Unknown Unknown Unknown > > Hi Oliver, > > To which nightly build do you refer? > > This looks like cprodrg is crashing. And that, I believe, is a problem for > CCP4. You can verify this by running cprodrg on the command line. > > IIRC, coot writes out the command line with which it tries to run cprodrg. > At a guess, it would be > > $ cprodrg XYZIN prodrg-in.mdl XYZOUT prodrg-DRG.pdb LIBOUT prodrg-out.cif << ! > MINI NO > ! > > Paul. >
