wiki:PackageCedaccInstall

CEDA Compliance Checker: Download and Installation

See also the example installation notes (from real-life installations at different Institutes).

1. Download and use directly or install in $HOME/bin

This approach is not recommended, but may be useful if you don't have immediate access to python package management libraries used in the 2nd and 3rd options. These libraries are easy to install, but that will require root or sudo access to your machine.

To download the code and configuration files:

  • Latest version:
    svn co http://proj.badc.rl.ac.uk/svn/exarch/CCCC/trunk/   
    
  • Tagged version (see PackageCedaccReleases):
    svn co http://proj.badc.rl.ac.uk/svn/exarch/CCCC/tags/<tag>
    

The script can then be executed:

  • python ceda_cc/c4.py -p <project identifier> -f <full path to netcdf file>

Where the "<project identifier>" is one of the projects the checker has been configured for, e.g. SPECS, CCMI, CORDEX, ESA-CCI.

To create a script in your ~/bin directory, run the following command in the source directory to create ~/bin/ceda_cc:

bash userinst.sh

Execute the checker with:

ceda_cc -p SPECS -f <full path to netcdf file of SPECS data>

2. Download and install in a single step with "pip"

For this option you will probably need root or sudo access on your machine, and you need to have "pip" installed. If these conditions are satisfied, simply type:

  • pip install ceda-cc

The compliance checker can then be executed a directory of your choice:

  • ceda_cc -p SPECS -f <full path to netcdf file of SPECS data>

or after downloading the tarball:

    $ export VERSION=1.0
    $ wget -nH https://pypi.python.org/packages/source/c/ceda-cc/ceda-cc-$VERSION.tar.gz
    $ pip install ceda-cc-$VERSION.tar.gz

3. Download and install with python setuptools package.

If you have the setuptools package you can execute the following from the distribution directory (after downloading the package as described in option 1 above):

  • python setup.py install

If you install ceda-cc with option (2) or (3), you can use the "--copy-config" option to move the configuration directory from the default directory (which is likely to be owned by root) to one which you can edit.