| ... | @@ -19,9 +19,11 @@ you could run the command |
... | @@ -19,9 +19,11 @@ you could run the command |
|
|
sm_create ci3144585 -e ci 1994-01-17T12:30:55 -118.546 34.211 19 6.6 "Northridge, California" -n
|
|
sm_create ci3144585 -e ci 1994-01-17T12:30:55 -118.546 34.211 19 6.6 "Northridge, California" -n
|
|
|
```
|
|
```
|
|
|
|
|
|
|
|
(The -n option is to prevent this event being flagged as a scenario).
|
|
where the `-e` flag tells sm_create to gather origin information from the command line, and
|
|
|
|
|
|
|
|
The latter command will only create an event.xml file.
|
|
the `-n` flag prevents this event being flagged as a scenario.
|
|
|
|
|
|
|
|
The -e command will only create an event.xml file.
|
|
|
|
|
|
|
|
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
|
|
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
|
|
|
```
|
|
```
|
| ... | |
... | |
| ... | | ... | |