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

hazard location (site) behaviour #176

Open
chrisdicaprio opened this issue Dec 3, 2024 · 0 comments · May be fixed by #178
Open

hazard location (site) behaviour #176

chrisdicaprio opened this issue Dec 3, 2024 · 0 comments · May be fixed by #178
Assignees

Comments

@chrisdicaprio
Copy link
Contributor

We, as users of runzi, want to be able to set site-specific vs30 values. This is done by specifying locations in a csv file (rather than using the locations variable in the config toml) each with it's own vs30.

The file is specified by locations_file and cannot be set if locations is set (and vice-versa)

Possible behaviours:

  1. if uniform vs30 specified, ignore for the site specific values
  2. if uniform vs30 specified, raise exception
  3. require uniform vs30 = 0

We will implement option 2 as it is least error prone / subject to misinterpretation.

@chrisdicaprio chrisdicaprio self-assigned this Dec 3, 2024
@chrisdicaprio chrisdicaprio linked a pull request Jan 13, 2025 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant