Hello,
I have now fixed (I hope) the numpy import bug. (I cannot easily test
this though!) So with this fix you should now not get an error just a
warning if you don't have numpy installed.
But you need to run the upgrade service to get the patch, and since
Analysis will not start with that import bug, you instead have to use the
script updateAll, which should be located in the bin directory (along with
analysis).
However I just discovered that the installCode.py script we are using has
not had the updateAll script included in its output. So this stuff was
added to what we here call branch4 of our code (which is where the
analysis 1.0 code was being created from) and not the trunk of our code
(which is where analysis 2.0 code was being created from). Great, eh.
Well, here is a ten second way of creating updateAll:
cd ccpnmr/bin
cp analysis updateAll
Edit updateAll and change the last line from:
..../python -i -O $CCPNMR_TOP_DIR/ccpnmr2.0/python/ccpnmr/analysis/AnalysisGui.py $1 $2 $3 $4 $5
to:
..../python -O $CCPNMR_TOP_DIR/ccpnmr2.0/python/ccpnmr/update/UpdateAuto.py
(The .... indicates where your python is located.)
Wayne
On Wed, 13 Aug 2008, Wayne Boucher wrote:
>
> PS: And someone already found the first (well, second) bug. Analysis is
> not supposed to require numpy to be installed to run but it seems it does.
> I will have to fix that. (But I would recommend that you install numpy in
> any case.) If you do not have numpy it will throw an exception, when it
> should just give a warning. To get going just comment the line out that
> gets mentioned in the exception. (But that means it would throw an
> exception if you try to use that module later, which is the automatic
> backbone assignment module.)
>
|