Hi Everyone,
I've just upgraded an 64Bit precompiled release and find myself unable
to start analysis again.
it seems that the things went worng in the startup-script (analysis2)
because:
setenv CCPNMR_BIN_DIR "$cwd/`dirname "$0"`"
setenv CCPNMR_TOP_DIR "`dirname "${CCPNMR_BIN_DIR}"`"
set both the TOP and the BIN to wherever the startup-script is located.
Meaning that everything after that fails for obvious reasons.
Christoph
On 08/10/2010 11:21 AM, Wayne Boucher wrote:
> Hello,
>
> If you are running a source code release then Dan has figured out why
> the upgraded to 2.1.4 has not coped correctly. So after the
> compilation in the c/ directory the upgrade script has to make
> symbolic links in the python/ directory. Only the normal way of doing
> that outside of a script ("make links") does not work inside that
> script for some reason I forget (at least some people found it didn't
> work) so instead it goes into the individual subdirectories and runs
> some other scripts. Well the relevant subdirectory is not listed for
> the BayesPeakSeparator. This means that another way to fix this is to:
>
>> cd ccpnmr/ccpnmr2.1/c
>> make links
>
> And then 2.1.4 should be ok. Note, this is only for source code
> updates. If you have a pre-compiled update and are hitting a problem
> with BayesPeakSeparator then something else must be going wrong.
>
> Wayne
>
> On Tue, 10 Aug 2010, Wayne Boucher wrote:
>
>> Unfortunately we look set to have a 2.1.5 pretty damn soon (because
>> it turns out there is a small stupidity in the C code for printing
>> windows), but I'd like to understand this issue about the
>> BayesPeakSeparator code before we try and produce a 2.1.5.
>>
|