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

Adding with_betw_ratio in Aristotle mode #10127

Merged
merged 1 commit into from
Nov 7, 2024
Merged

Adding with_betw_ratio in Aristotle mode #10127

merged 1 commit into from
Nov 7, 2024

Conversation

micheles
Copy link
Contributor

@micheles micheles commented Nov 7, 2024

Fixing errors like

You cannot use the conditioned ground shaking module with the GSIM AtkinsonBoore2006Modified2011

@micheles micheles added this to the Engine 3.22.0 milestone Nov 7, 2024
@micheles micheles merged commit 14ff31e into master Nov 7, 2024
7 checks passed
@micheles micheles deleted the aristotle branch November 7, 2024 13:59
expo_hdf5, oq.mosaic_model,
oq.tectonic_region_type.encode('utf8'))
# add with_betw_ratio when only the total stddev is defined
betw = {'with_betw_ratio': 1.7}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should try to avoid the hardcoding of the value for this parameter, especially because the ratio might be different for different tectonic region types. Can we surface this through the interface in some way so that the engine doesn't make an implicit decision on behalf of the user?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is already done, since in the job.ini file it is possible to specify the parameter with_betw_ratio to any value (see #10128). The value 1.7 was chosen for consistency with GEESE. However, we do not have a WebUI interface to change the parameter. If you want that, I guess for the advanced interface i.e. for GEM people and not for Aristotle users, you should open a ticket.

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

Successfully merging this pull request may close these issues.

2 participants