Difference between revisions of "CyberShake MareNostrum Training"
| Line 19: | Line 19: | ||
== Set up needed files == | == Set up needed files == | ||
| − | <b>Create a directory to work from. I recommend something in scratch.</b> | + | <b># Create a directory to work from. I recommend something in scratch.</b> |
<pre> | <pre> | ||
| Line 36: | Line 36: | ||
Due to the outgoing connection problem, on MN4 we are using a local SQLite database rather than a remote MySQL database, which is what SCEC's CyberShake install uses. Each trainee should work from their own database. | Due to the outgoing connection problem, on MN4 we are using a local SQLite database rather than a remote MySQL database, which is what SCEC's CyberShake install uses. Each trainee should work from their own database. | ||
| − | <b>Copy in my training database from /gpfs/projects/pr1ejg00/CyberShake/database/training.sqlite.</b> | + | <b># Copy in my training database from /gpfs/projects/pr1ejg00/CyberShake/database/training.sqlite.</b> |
<pre> | <pre> | ||
| Line 42: | Line 42: | ||
</pre> | </pre> | ||
| − | In order to look at this database, we need sqlite. <b>Add the SQLite module to your environment.</b> | + | # In order to look at this database, we need sqlite. <b>Add the SQLite module to your environment.</b> |
<pre> | <pre> | ||
pr1ejg10@login2:/gpfs/scratch/pr1ejg00/pr1ejg10/TEST> module load sqlite | pr1ejg10@login2:/gpfs/scratch/pr1ejg00/pr1ejg10/TEST> module load sqlite | ||
</pre> | </pre> | ||
Revision as of 20:39, 13 February 2020
This page provides training for running the CyberShake TEST site on MareNostrum (MN4)
Training overview
Here are the basic steps involved in the training:
- Set up needed files
- Initialize database with run information
- Create Strain Green Tensors
- Create synthetic seismograms and intensity measures
- Populate database with intensity measures
- Populate Hazard Dataset
- Plot hazard curves
Actions you need to take will be in bold.
Terminal commands and output will be in this font. Replace <username> or <working dir> with your username or your working directory, respectively. My username is pr1ejg10 and my project is pr1ejg00.
Set up needed files
# Create a directory to work from. I recommend something in scratch.
pr1ejg10@login2:~> cd /gpfs/scratch/pr1ejg00/<username> pr1ejg10@login2:/gpfs/scratch/pr1ejg00/pr1ejg10> mkdir TEST pr1ejg10@login2:/gpfs/scratch/pr1ejg00/pr1ejg10> cd TEST
An overview of the code involved in CyberShake is provided here. For this test, we are using the SGT-related codes, the PP-related codes, and the Data Products codes, but not the Stochastic codes.
Since MN4 does not permit outgoing connections, it is impossible to install CyberShake on MN4 directly from the repository. For the purposes of this training, I suggest you use my install directly. My CyberShake installation is located at:
/gpfs/projects/pr1ejg00/CyberShake
Due to the outgoing connection problem, on MN4 we are using a local SQLite database rather than a remote MySQL database, which is what SCEC's CyberShake install uses. Each trainee should work from their own database.
# Copy in my training database from /gpfs/projects/pr1ejg00/CyberShake/database/training.sqlite.
pr1ejg10@login2:/gpfs/scratch/pr1ejg00/pr1ejg10/TEST> cp /gpfs/projects/pr1ejg00/CyberShake/database/training.sqlite .
- In order to look at this database, we need sqlite. Add the SQLite module to your environment.
pr1ejg10@login2:/gpfs/scratch/pr1ejg00/pr1ejg10/TEST> module load sqlite
