Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Anne Hulsey

Pages: 1 ... 3 4 [5]
Another feature that I would start using in September is to include the option for an aftershock flag for the Chiou & Youngs 2008 GMPE. However, based on preliminary conversation with Baker, this request may be constrained by the OpenSHA software, not the EQHazard implementation of it.

If EQHazard and OpenSHA can't handle the aftershock flag, I will need to build my own package. However, I think it is mutually beneficial for this to be implemented by SimCenter.

Thanks for addressing all the recent feature requests I have mentioned. I would like to revisit one from several years ago but which now has an immediate use case for a postdoc project here at Stanford.

Currently, EQHazard can only handle a single scenario for the mean and standard deviations at a site list. For my project, I ran it for 4 different scenarios and then compiled the results. However, it would be a huge improvement for it to run a user specified list of scenarios or all the ERF scenarios.

One difficulty is scaling the output format. I convert the output .json dictionary into .h5 files that are intended to support many intensity measures at many sites for many rupture scenarios. I would be happy to share the format with you, if helpful.

Thank you for tracking down documentation on the dm and on the magnitude area relationships. I am satisfied with these responses. While I still think the magnitude area input would be a great feature to have, I suggest de-prioritizing it. I personally would not use it since Wells and Coppersmith is not an option for UCERF2.

Great, thank you.

This is excellent. Thank you for addressing both features.

If, in addition to sorting the sources by proximity to site, you could further sort each rupture index by the rupture proximity to site, that would be a great bonus.

It would be really helpful to have error messages if EQHazard doesn't work. Currently it gives a 0 if successful and an meaningless number if it doesn't. It look me over 4 hours to discover that I had misspelled Chiou wrong in the GMPE name.

Sounds good, thanks. It might be good to mention this issue and the solution in the documentation. I never would have realized it if I hadn't mapped the sources.

Speaking of which, when mapping the sources, I differentiate between ruptures vs background seismicity based on the index. The background sources start somewhere around 500. I often only need the ruptures so, it would be nice to have a flag that indicates whether the catalog should include background sources or not.

A recent discussion with Jack Baker indicated that there might also be an OpenSHA input parameter to specify the empirical relationships for moment magnitude to rupture geometry (e.g. Wells and Coppersmith 1994).

This would also be a nice feature (that I would use if it were included within the next 2 months) but the parameter for dm is a higher priority.

The MaxSources limit in the UCERF2 ERF causes odd behavior in the background seismicity. I believe that it searches the sources by index until it reaches the maximum number. However, the index seems to be order South to North, such that the background seismicity is not centered around the site.

I have handled this by increasing the number of sources to a value that does not control the selection. However, it would be preferable to have the background seismicity radiate out from the site, no matter what the distance is.

Currently, the ERF output assumes that the magnitude interval for the OpenSHA catalog is 0.1. Can that become an input parameter so I can decrease it to 0.05?

Pages: 1 ... 3 4 [5]