-
Notifications
You must be signed in to change notification settings - Fork 1
Home
SAGA is pre-installed on many systems across FutureGrid and XSEDE. Here we have documented how to set up the environment and use the SAGA installations on those different machines. Changes to the SAGA deployment setups can be requested on the saga-users mailing list ([email protected]).
The SAGA installations are provided in CSA space, which stands for 'Community Software Area' -- so, the software is provided by the SAGA community (us) in a dedicated system space.
Note that many machines host both a vanilla CSA deployment of SAGA (limited to verifies modules and configurations), and also an experimental ESA deployment (ESA: Experimental Software Area). The latter is subject to be changed w/o further notice, and will contain the latest development codes -- only use the ESA deployments if you know exactly what you are doing.
The following XSEDE machines host CSA installations of SAGA. Please follow the links for more details on how to use it and on the installed components & versions:
| kraken.nics.xsede.org | CSA | ESA |
| ranger.tacc.xsede.org | CSA | ESA |
| lonestar.tacc.xsede.org | CSA | ESA |
| blacklight.psc.xsede.org | CSA | ESA |
| steele.purdue.xsede.org | CSA | ESA |
| trestles.sdsc.xsede.org | CSA | ESA |
The following FG machines host CSA installations of SAGA. Please follow the links for more details on how to use it and on the installed components & versions:
| india.futuregrid.org | CSA | CSA |
| sierra.futuregrid.org | CSA | CSA |
| alamo.futuregrid.org | CSA | CSA |
| hotel.futuregrid.org | CSA | CSA |
The deployment process on the above infrastructures is supported by a deployment script, whose documentation can be found here