|
|
|
To run ShakeMap, the data associated with an event needs to be added to the data directory. Numerous event data are included in this repository in the `tests/data/eventdata` directory. You can copy one or more of these directories to the data directory associated with your shakemap profile. Using the example from the previous section on setting up profiles, this would be
|
|
|
|
```
|
|
|
|
cp -R [shakemap]/tests/data/eventdata/northridge \
|
|
|
|
/home/shake/ShakeMap/default/data/.
|
|
|
|
```
|
|
|
|
where `[shakemap]` is the directory to the local clone of this repository.
|
|
|
|
|
|
|
|
The programs for running ShakeMap are all managed by the command [shake](http://usgs.github.io/shakemap/programs/shake.html). The basic idea is that you will call `shake`, which has a number of optional arguments, but it is followed by an event id (i.e., the name of the event directory in the data directory) and then the names of the modules that you want to run for that event. You can get help in a terminal like this
|
|
|
|
```
|
|
|
|
> shake -h
|
|
|
|
usage: shake [-h] [-d] [-q] [-l] eventid cmds [cmds ...]
|
|
|
|
|
|
|
|
Run specified ShakeMap modules.
|
|
|
|
|
|
|
|
|
|
|
|
positional arguments:
|
|
|
|
eventid The id of the event to process.
|
|
|
|
cmds The modules to run.
|
|
|
|
|
|
|
|
optional arguments:
|
|
|
|
-h, --help show this help message and exit
|
|
|
|
-d, --debug Print all informational messages.
|
|
|
|
-q, --quiet Print only errors.
|
|
|
|
-l, --log Log all output.
|
|
|
|
|
|
|
|
Available modules:
|
|
|
|
- assemble -- Assemble ShakeMap input data into the shake_data.hdf input file.
|
|
|
|
- augment -- Incorporate additional content into the shake_data.hdf input
|
|
|
|
file.
|
|
|
|
- contour -- Generate contours of all configured IMT values from the
|
|
|
|
shake_result.hdf output file.
|
|
|
|
- gridxml -- Create grid.xml and uncertainty.xml files from shake_result.hdf.
|
|
|
|
- info -- Extract info.json from shake_result.hdf and write it as a file.
|
|
|
|
- mapping -- Generate maps of the IMTs found in shake_result.hdf.
|
|
|
|
- model -- Interpolate ground motions to a grid or list of locations.
|
|
|
|
- raster -- Generate GIS raster files of all configured IMT values from
|
|
|
|
shake_result.hdf.
|
|
|
|
- rupture -- Generate rupture.json from shake_result.hdf.
|
|
|
|
- select - Parse STREC output, make a GMPE set, create model_zc.conf.
|
|
|
|
- stations -- Generate stationlist.json from shake_result.hdf.
|
|
|
|
```
|
|
|
|
So a simple call to organize the input data for the 'northridge' event into the HDF input file would be
|
|
|
|
```
|
|
|
|
> shake northridge assemble
|
|
|
|
INFO ; 2018-02-09 11:43:24 ; shake.main ; Running command assemble
|
|
|
|
INFO ; 2018-02-09 11:43:24 ; shake.main ; Finished running command assemble: Elapsed 0.14 secs
|
|
|
|
```
|
|
|
|
This is not all that useful unless you want to read in and inspect the HDF file. |
|
|
\ No newline at end of file |
