New Mexico Tech
Dept. Earth & Env. Science

Ronni Grapenthin - CrusDe Project

CrusDe - Download

Up to now the convenient configure-make-make install cycle is not yet provided for CrusDe. Hence, the installation needs a little more attention. I am working on improving this situation, though. Details are given in the INSTALL file that comes with the code.

The most recent version lives on github:

$> git clone git://

This allows read access to the repository. Once you installed CrusDe this way use:

$> git pull

in the CrusDe top level directory to update your copy of CrusDe to the latest version from the repository. Then rebuild.


VersionDateRelease Notes / Changelog
crusde v1.0 2015-06-26
crusde-0_3_0.tar.gz (9.3mb) 2011-04-26
  • improved API, install routines
  • allows for optional parameters in XML files (model definition)
  • added fourier timeseries, implements annual, semiannual, transient load history
  • increased acceptable load functions to 1000
  • added 2D convolution in spatial domain (slow!)
  • Geographiclib added for geodesic computations
  • bug fixes and minor convenience changes
crusde-0.2.0.tar.gz (1.7mb) 2008-08-31
  • time-space convolution has been added, hence time treatment is now available for non-elastic responses
  • multiple loads w/ independent histories, decay functions, parameters
  • multiple job definitions to express combinations of green's functions for more complex expressions (displacement rates, exponential decay ...)
  • bug fixes
  • additional packages no longer in distribution!
crusde-0.1.0.tar.gz (24.6mb) 2007-07-30 Initial release as described in my thesis (pdf, 5.3mb)


NOTE: The current version needs a little more attention than the convenient 'configure-make-make install' cycle. This will change as soon as possible. In the meantime I ask you to hang in there and go through the procedures described below. I appreciate your patience!

  1. solve dependencies and install the following packages: Please follow the installation instructions of these libraries! Preferably all these packages should end up in their default directories or /usr/local respectively.

    If you compiled the shared versions set the LD_LIBRARY_PATH variable in your profile file and add the paths to the respective PACKAGE/lib directory.

  2. move and decompress CrusDe
    • cp crusde-VERSION.tar.gz /usr/local
    • cd /usr/local
    • tar xfz crusde-VERSION.tar.gz
    If you don't want to install to /usr/local you can move the directory to any other place. Whereever it ends up, set this path in your profile file (bash):

    export CRUSDE_HOME=/usr/local/CrusDe

  3. edit Makefile
    • cd $CRUSDE_HOME/src
    • vi Makefile
    Now several things might have to be changed:
    • Binary directory if you don't have write permission to /usr/local/bin, change BIN := [path to where the crusde binary should go]
    • If Qt ended up somewhere different from /usr/local/Trolltech/Qt, change export QT_DIR := [path to where Qt is installed]
    • If any of the other libraries is installed somewhere else than /usr/local/{lib | include}, add the respective paths to INCLUDE_DIRS and LIB_DIRS using -I[path] or -L[path] respectively. Those variables already point to /usr/local/xerces-c. Modify this path, if xerces lives in a different directory.
  4. compile source
    • cd $CRUSDE_HOME/src
    • make all
  5. install the plug-ins

    Try running:

    $> cd $CRUSDE_HOME/src

    This should automatically install the standard plug-ins. If it doesn't work, follow the long procedure that was in place before this script:

    This step might be a little painful, but also helps to familiarize with the plug-in manager; there's always a good side to everything, right?!

    $> crusde -p

    A little window will open, the so called 'CrusDe Plugin Manager', do the following:

    • click 'Add'
    • go to 'src/plugin-src/green'
    • click on '', click on 'Open'
    • Read text and press 'Ok'
    The plugin 'elastic halfspace (pinel)' should be installed in the category 'green' after some tests were run.

    Repeat this for all subdirectories in $CRUSDE_HOME/src/plugin_src. Some plugins depend on others and hence a certain order must be followed. Here is a recommendation:

    • crustal_decay: free choice (exponential, exponential_rate)
    • data_handler: free choice (netcdf, table)
    • green:,,,
    • load: free choice (disk, irregular)
    • load_history: free choice
    • operator:, ( is useless at the moment)
    • postprocess: free choice
    A known problem is that plug-ins that depend on other plug-ins will cause the plugin manager to crash after the tests are performed.

    That is NOT a problem!

    Just restart the plugin manager and you'll see the plug-in was installed. This is an issue that will be tackled soon.

    You should be ready to run the testcases in $CRUSDE_HOME/testcases after that.

  6. I recommend to copy the testcases directory somewhere into your user space so that other users have access to clean testcases. You can then go ahead and play with them:

    $> crusde [path to experiment definition]/experiment.xml

Please refer to the documentation for further details.

Some instructions ...

Additional packages, that are not necessary but certainly nice to have, i.e. recommendations:

| Last modified: March 12 2019 15:19.