Hi Ian,
Improving the CCP4 tests is a priority. We (the core team) have a project
looking into that. If developers have their own tests for components of the
suite that have not made it into the distribution, then we'd be happy to
collect them for the new test set.
Best wishes
-- David
On 29 A
Hi Marcin
It was obviously added originally because there was a limit to the length
of the PATH variable (presumably there still is), so repeated invocations
of setup scripts could take you over the limit. Ideally the script should
remove old versions from the PATH, not just prepend the new one,
On Mon, Apr 28, 2014 at 03:51:57PM +0100, Ian Tickle wrote:
> Harry,
>
> I've run into this problem before with other programs when I switch between
> v6.3 & v6.4. I think the problem is this code in ccp4.setup-sh:
>
> if [ `expr ":${PATH}:" : ".*:${dir}:"` -eq 0 ]; then
We can remove this co
Hi Felix
You're very trusting! Bugs in new versions of software are not unknown!
The bug may not manifest itself in a program crash (though it makes life
easier if it does), rather it may simply give different numerical results
that you may not spot for some after. This is why CCP4 distributes t
Hi Tim,
What can be a reason to work with an obsolete version of CCP4?
I remember reading somewhere that 6.3.0 version is obsolete.
FF
Dr Felix Frolow
Professor of Structural Biology and Biotechnology, Department of Molecular
Microbiology and Biotechnology
Tel Aviv University 69978, Israel
A
Dear all,
For experiments that involve switching between different versions of CCP4
you might like to try the CCP4Dispatchers scripts (see
http://www.ccp4.ac.uk/html/CCP4Dispatchers.html). On a binary install of
ccp4 6.4.0 these will have been generated automatically. For example, on my
Linux mach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Sreetama, dear Ian,
I avoid sourcing both version 6.3 and 6.4 in the same terminal. If I
need to work with 6.3 I modify my .bashrc from 6.4 to 6.3 and then
open a new terminal to make sure everything refers to v6.3 and vice versa.
Best,
Tim
On
Harry,
I've run into this problem before with other programs when I switch between
v6.3 & v6.4. I think the problem is this code in ccp4.setup-sh:
if [ `expr ":${PATH}:" : ".*:${dir}:"` -eq 0 ]; then
if test $ccp4_first_in_path -eq 1; then
PATH=${dir}:${PATH}
else
PATH=${PA
Hi Sreetama
That's the problem - sourcing the old ccp4 6.3 distro has set up MOSFLM_EXEC to
point to an old copy of ipmosflm that will not run with the latest iMosflm.
> Mosflm version 7.0.9 for Image plate and CCD data 14th May 2012
which cannot be used with iMosflm 7.1.0.
So it looks
Dear Sir,
If I sorce ccp4-6.3, and then change in the bashrc file & source
ccp4-6.4, (and source the modified .bashrc file in either case) but don't close
the previous terminal, then opening imosflm gives the aforementioned error.
After closing the imosflm GUI, if I type at the ter
Hi
When you get this error, and "everything" has been closed, what do you get if
you type (in the same terminal window that you tried to start iMosflm) -
$MOSFLM_EXEC
?
It's plain from the message that
"ipmosflm" is not compatible'
that iMosflm is trying to run with an inco
Dear All,
Whenever I open up imosflm GUI from the terminal, I get the
following error:
iMosflm version 7.1.1, 24th March 2014
"ipmosflm" is not compatible.
Please configure iMosflm with the correct executable.
clicking the Configure button at the bottom of the error message panel
12 matches
Mail list logo
