Download Cactus

Requirements

Required Optional
Perl MPI
C C++
CPP F90/F77
GNU make ctags/etags
SVN

Getting the Code

Method #1: GetComponents

    Cactus is maintained using Subversion. The preferred method is to use the GetComponents script along with a thornlist as described below. We maintain a page of basic thornlists, but you can use your own customized thornlist.

    Download GetComponents and make sure it is executable. wget --no-check-certificate https://raw.github.com/gridaphobe/CRL/master/GetComponents chmod a+x GetComponents

    To checkout the Cactus flesh and required thorns, choose and save one of our ThornLists (or provide your own) and issue the command: ./GetComponents <thornlist-name>

Method #2: Subversion

    Instead of using the GetComponents script, you can also check out Cactus and the Cactus Computational Toolkit using svn commands or another Subversion client. The main Cactus Subversion Server (svn.cactuscode.org) hosts several different repositories including different branches for the stable and development versions of Cactus.

    The Subversion server can be use anonymously to checkout Cactus components. It supports both http and https connections, but only https can be used for authenticated logins, e.g. for commits to the repositories.

    Check out the Cactus flesh: svn co http://svn.cactuscode.org/flesh/branches/Cactus_4.2.0 Cactus Move to the arrangements directory of the Cactus installation and install the required arrangements and thorns: cd Cactus/arrangements If you are using thorns other than those in the standard Cactus distributions you will need to know the details for downloading or checking them out. Here we just describe checking out from the Cactus distribution.

    To checkout individual thorns (e.g. see our standard ThornLists): svn co http://svn.cactuscode.org/arrangements/<arrangement>/<thorn>/branches/Cactus_4.2.0 <thorn>

License

The Cactus Code is (C) Copyrighted by the individual Authors and distributed under the GNU Lesser General Public License. Most of the computational packages that come with it follow this license, but the authors of any thorn are free to follow any licensing they deem appropriate as long as they state it explicitly in their thorn distribution.