Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Branched average b-values for NSHM23 WUS inversion #3

Open
heathercrume-moodys opened this issue Oct 23, 2024 · 4 comments
Open

Branched average b-values for NSHM23 WUS inversion #3

heathercrume-moodys opened this issue Oct 23, 2024 · 4 comments

Comments

@heathercrume-moodys
Copy link

Can you add the weighted branch average for b-values to the NSHM23 WUS inversion so it's possible to run a single inversion with branched averaged ingredients? Thanks!

@kevinmilner kevinmilner transferred this issue from opensha/opensha Oct 23, 2024
kevinmilner pushed a commit that referenced this issue Nov 12, 2024
@kevinmilner
Copy link
Contributor

This option is supported by the fst_inversion_factory_runner.sh script, does that work for you? It doesn't allow you to specify all of your own constraints, but rather uses the full NSHM23 inversion recipe (potentially with your data instead of NSHM23 data if you pass in a rupture set). For example, you could reproduce an NSHM23 inversion with the average b-value branch via:

fst_inversion_factory_runner.sh --nshm23 --branch-choice SupraB:AvgSupraB --output-file solution.zip

You can also pass in your own rupture set via --rupture-set /path/to/rupture_set.zip instead of building one for NSHM23 data.

It will be a bit trickier to build this into the regular and more customizable inversion tool. Instead, I suggest averaging them post hoc, which is possible with the solution averager tool (and simple because they're evenly weighted).

@heathercrume-moodys
Copy link
Author

This works great, thank you! One follow-up question, are the averages in the different branch options (for example, --branch-choice DM:AVERAGE) the weighted averages from the logic tree or are they equally weighted?

@kevinmilner
Copy link
Contributor

Good question; they're the weighted average from the model. So, uneven for deformation model and segmentation, even for b-values.

If you use the average b-value and/or segmentation branches, it does a pretty good job of approximating the average of separately-run inversions because it calculates the target MFDs separately for each branch choice, then weight-averages those target MFDs. This gets better to the average behavior than using, for example, a central b-value or an segmentation penalty.

@heathercrume-moodys
Copy link
Author

Perfect, thank you!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants