[Shake-dev] SM3.5 Borcherdt table

[Bruce Worden]

Hi Pete,

That's a bit of misleading setup in the default grind.conf.  
site_corr_slope.dat is something used by global ShakeMap for  
situations where the site conditions are estimated from topographic  
slope. site_corr_cdmg.dat is correct for the California Vs30 map  
derived from Wills, et al. For consistency I'll change grind.conf in  
the next update, but users outside California will still have to use  
their own site amplification files.

There is an as-yet-unannounced update to makeMMIsiteTable in the  
repository. If you're going to be running some maps, I'd suggest  
getting it and re-running makeMMIsiteTable to generate new site  
correction tables for MMI. The older version had a glitch that didn't  
allow amplified sites (i.e., sites softer than 'rock') to reach  
intensity 1.0.

Bruce


On Jan 23, 2011, at 9:54 AM, Peter Lombard wrote:

> Bruce,
>
> The default grind.conf file included with ShakeMap 3.5 calls for the  
> following
> "Borcherdt table" files or their derivatives:
> ampfactor_file          : lib/sitecorr/site_corr_slope.dat
> mifactor_file           : lib/sitecorr/site_corr_cdmg_mmi
>
> Can you provide some guidance about the differences between  
> site_corr_cdmg.dat
> and site_corr_slope.dat?
>
> Why would we choose site_corr_slope.dat for the ampfactor_file, and
> site_corr_cdmg.dat for the source for the mifactor_file, as opposed  
> to using
> the same file for both?
>
> Pete
>