CDAT DOWNLOAD AND INSTALL

We recommend that you build CDAT from the sources. CDAT is available on these platforms.

For convenience we sometimes provide binary versions in our download area. Binaries might not work properly on your system. If you have trouble with a binary installation, please try a source build before reporting difficulty.

The latest install instructions are always in the README.txt file at the top level of the extracted files.

Obtaining and Installing CDAT Releases

You can download our sources or get them directly from our repository as explained in below.

  1. Go the Sourceforge CDAT Project Page.
  2. Scroll down to "Latest File Releases", find the line "CDAT" and click on "Download".
    The download page will appear and you can select the file you want.

    The distribution is available in one piece or in 3 separate pieces for easier downloading.

  3. Uncompress and untar it
  4. as follows:
  5. Follow the instructions in the README.txt file.

Tutorials

  1. Get the tutorial examples and the datasets as above.
  2. Untar them both.
  3. Enjoy discovering CDAT's capabilities

Direct Access to the Source Repository

CDAT is an open-source project. So how do you see the source? And never download by hand again?

Our normal release cycle releases a set of sources at a stable point. However, you might want to get an update between releases because someone has made an improvement you would like to use. You can now do this yourself. Be aware that while we make every attempt to only commit source that is correct and working, and that we develop in separate "branches" to help ensure this, this direct access is inherently less stable than using our official releases.

Here is how to do it:

  • a. Go to perforce.com and download the "p4" client for your machine and install it in your path. This download is free. You'll need to chmod +x p4 after download, of course.
  • b. Set environment variable P4CONFIG to "p4env".
  • c. Create a directory and change to it. Create a file named p4env that contains:
    P4PORT=esg.llnl.gov:1666
    P4USER=pcmdi
    P4CLIENT=pcmdi-yourname 
    #replace yourname with your name, e.g. pcmdi-dubois
  • d. Execute: p4 info
       If it prints out intelligent-looking stuff like what follows, your access is set up correctly. Note the "Client unknown". If it does not say this, you'll need to pick a different user name because the one you chose is in use.
  • [dubois@ldorritt ~/foo]$ p4 info
    User name: pcmdi
    Client name: pcmdi-junk
    Client host: ldorritt
    Client unknown.
    Current directory: /pcmdi/dubois/foo
    Client address: 192.12.134.251:33720
    Server address: esg.llnl.gov:1666
    Server root: /p4root
    Server date: 2002/03/25 09:29:23 PST
    Server version: P4D/LINUX52X86/2001.1/26850 (2001/10/15)
    Server license: Lawrence Livermore National Laboratory (LLNL) 10 users (support ends 2003/03/01) 
  • e. Execute: p4 client
       Your editor will open on a client specification form. The last lines will be something like:
       //depot/...  //pcmdi-yourname/...
  • Edit this to add "main/" right before the two sets of ...'s, so it reads:
       //depot/main/...  //pcmdi-yourname/main/...
    Save and close your editor.

  • f. Type p4 sync now and any time you wish to update your sources.
  • You can put a minus sign in front of either line if you don't want it now but want to remember how to get it. Full documentation for client mapping is on the Perforce web site.

    You won't need to download from our website. And you'll find that p4 is VERY fast.

    Perforce permits us to do this under our license; the read-only access for everyone only "uses up" one license. Write access for heavy contributors can be arranged by mutual agreement with PCMDI and payment of the Perforce license and annual support fee for an extra user (the license is about $750). You can always use the SourceForge patch facility to submit bug fixes if you do not have write access.

    Troubles ?

    If you have trouble downloading/installing CDAT please email: cdat-discussion@list.sf.net. The project page http://sf.net/projects/cdat also has a bug reporting facility and information on our mailing lists.

    Please also check the mailing list archives.