Thanks Paul,
I'll give that a try. Is there any similar mechanism to load a global
initialization file(s) under scheme as there is for Python, e.g. can I define a
similar directory to COOT_PYTHON_EXTRAS_DIR but just for scheme commands. It
would make the life of our sysadmins and users a bit easier if some settings
and macros could be administered centrally through this mechanism.
BTW, coding in scheme gives me the heebie jeebies :-), any way this little
misbehavior can be changed in future releases?
Cheers,
Carsten
-----Original Message-----
From: Mailing list for users of COOT Crystallographic Software
[mailto:[email protected]] On Behalf Of Paul Emsley
Sent: Thursday, March 06, 2014 6:51 PM
To: [email protected]
Subject: Re: [COOT] Unable to run probe and reduce in coot under Linux
On 06/03/14 23:11, Schubert, Carsten [JRDUS] wrote:
> Hi,
Hi Carsten
>
> I am bit stumped on how to get probe or reduce to work with coot under Linux.
> I followed the instructions and defined the path to reduce/probe in various
> startup and system files in which I could find a reference to probe/reduce:
> * ~/.coot.py
> * coot.py (path defined by COOT_PYTHON_EXTRAS_DIR)
> * coot /share/coot/python/coot_load_modules.py
>
> In all cases the 'Validate -> Probe Clashes' menu item stays grayed out. I
> referenced both locally installed versions of probe/reduce as well as the
> ones distributed with Phenix to no avail.
>
> >From the scripting console "print probe_command" gives the correct path to
> >the executables, indicating that the program at least picked up the correct
> >settings. The function "probe_available_p()" returns 1 for what it's worth.
>
> I am trying to get this to work under coot 0.7.2 and coot 0.8pre 4941
>
Sorry this is confusing. I think you need to set the path in scheme mode:
I have this in my ~/.coot
(set! *probe-command*
"/home/paul/molprobity/probe4linux/probe.2.12.071128.linuxi386")
(set! *reduce-command*
"/home/paul/molprobity/reduce4linux/reduce.3.13.080428.linuxi386")
Paul.
