2.6.2. Compiling and installing in the Anaconda environment

Note

If you are using a prebuilt Virtual Computer, you can skip this page.

This is the second of four final steps required to get the CODAS software installed on the computer built using earlier sections of this documentation. This page is specific to an Anaconda environment.

This assumes you have (from the previous section)

  1. code in /home/adcpcode/programs

  2. your anaconda directory is ~/anaconda

This was written for an OSX example, but would work just as well with Linux.

Note

You must compile the codas3 library and binaries before you compile/install the rest of the Python code.

Note

If your Anaconda environment has python and pyhton3, make sure you are running Python3 for all CODAS operations.

Test your Python environment:

type:
        python --version

you should see:

        Python 3.6.3 :: Anaconda custom (64-bit)

(or a Python version of 3.7)

Compile and install codas3 first:

cd codas3
./waf configure --python_env
./waf build
./waf install
cd ..

Note

If the build stage gives an error on OSX, try re-doing the configure stage with an additional specification:

./waf configure AR=/usr/bin/ar --python_env
./waf build
./waf install

The --python_env option above will make the installation be in the Anaconda environment instead of the default /usr/local. Either will work, but keeping everything together makes it easier to keep track of what you have installed, and to delete it all if you want to make a fresh start some time.

At this stage, you can compile the CODAS Python extension code, in pycurrents, which includes the Python CODAS reader and various tools we use for Python-based CODAS processing:

cd pycurrents
python ./runsetup.py
cd ..

Last, install uhdas and onship:

cd uhdas
python runsetup.py
cd ..

cd onship
python setup.py build
python setup.py install
cd ..

Now that you have actually compiled and installed CODAS C and Python extension code, it is time for the next step: getting the non-Mercurial components.