[Shake-dev] Define image size of output file (e.g. intensity.ps)

Bruce Worden cbworden at gmail.com
Mon Jan 12 16:24:57 UTC 2015


Hi Erik,

Setting lonspan in grind.conf is the way to go for what you want to do. Keep in mind, though, that what is set in grind.conf will be overridden by -lonspan given on the command line when you run grind. Settings in shake.conf are meant for automatic runs from the shake program. The first time shake runs, it will set the command line flags for the various shakemap programs according to the configuration in shake.conf, but subsequent runs will use the flags found in the database for the most recent run. For instance, if you run grind manually with a non-default -lonspan, the next run by shake will include that setting. To see how shake will run the shakemap programs, you can use -dryrun, which will print out the commands, but not run them. You can then copy and paste the commands one at a time, altering the command line flags as necessary. Subsequent runs by shake will remember those flags. 

As I said above, if you want your maps to default to 10 degrees, set the lonspan in grind.conf. Then use the settings in shake.conf only to override that.

Bruce

On Jan 12, 2015, at 6:28 AM, Erik Bäckman <ek.backman at gmail.com> wrote:

> I should probably add that if type
> 
> $ ./grind -event <event id> -xml -lonspan 10.0 -psa
> $ ./mapping -event <event id> -timestamp -itopo
> 
> then the output files will have a lonspan of 10.0. But what I want is lonspan by default to be e.g. 10.0. Tried changing lonspan in <shake home>/bin/grind as well, but without success.
> 
> 2015-01-12 14:39 GMT+01:00 Erik Bäckman <ek.backman at gmail.com>:
> Hi all,
> 
> I am struggling with how/where to define the size of the images located in /data/<event id>/mapping after running an event, or a scenario in my case.
> 
> In shake.conf I found that you can define 'lonspan' such that the image size gets increased for larger events (to give a better view of mi/pga/pgv etc). I tried to change that, but no visible changes in the output. Also scrolled through grind.conf where the parameters 'lonspan', 'latspan' and 'llratio' are explained but no success.
> 
> Any ideas?
> 
> Best regards,
> Erik Bäckman
> 
> _______________________________________________
> Shake-dev mailing list
> Shake-dev at geohazards.usgs.gov
> https://geohazards.usgs.gov/mailman/listinfo/shake-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/shake-dev/attachments/20150112/8bbdcc6c/attachment-0001.html>


More information about the Shake-dev mailing list