Skip to content

Using the circulant embedding regular grid in OQImpact - #11939

Open
micheles wants to merge 5 commits into
masterfrom
grid
Open

micheles wants to merge 5 commits into
masterfrom
grid

Conversation

@micheles

Copy link
Copy Markdown
Contributor

No description provided.

@micheles micheles added this to the Engine 3.27.0 milestone Oct 19, 2026
@micheles
micheles requested a review from raoanirudh October 19, 2026 13:20
region_grid_spacing is mandatory in impact mode since the circulant
embedding regular grid commit, but the shakemap validation path never
set it, so impact_validate failed. Default it to 10 km, expose it in the
impact form (label, placeholder, default, strictly positive validator)
and pass it from the JS form data.
The sites of impact jobs are now a regular UTM grid around the rupture
(see 9ba22b7), which changes the aggregated risk and the exposure by
MMI tables. Regenerated with OQ_OVERWRITE=1 for impact1, impact3,
impact4 and impact5. impact2 is left unchanged: it fails when building
the grid because it straddles a UTM zone boundary.
The job.zip of an impact job has no exposure HDF5, so the reloaded job
was not in impact mode and required reference_vs30_value. Associate the
site parameters of the site model close to the rupture to the sites
before writing sites.csv, so the reloaded job finds them there.
The grid sites of impact jobs have no parameters and req_site_params is
still empty when they are associated in base.py, so vs30 was 0 at every
site and the GMPEs returned garbage. Add all the site model parameters
to the sitecol and to the complete sitecol before associating them.
Drop the export helper, since sites.csv now carries the parameters.
Regenerate the impact1, impact3 and impact4 expected values.

This branch has not been deployed

No deployments
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