Comments (1)
We decided to remove the option of reading the finite fault page directly because the downloadable rupture polygon files from that page are not very reliable or consistent in format. For instance, the finite fault polygon file for the 2024 Hualien earthquake does contain the rupture coordinates: https://earthquake.usgs.gov/product/finite-fault/us7000m9g4_1/us/1712690873099/shakemap_polygon.txt, but the 2023 Kahramanmaraş finite fault polygon files are empty: https://earthquake.usgs.gov/product/finite-fault/us6000jllz_1/us/1676951251912/shakemap_polygon.txt and https://earthquake.usgs.gov/product/finite-fault/us6000jlqa_1/us/1676676771092/shakemap_polygon.txt
On the other hand, the rupture.json file from the ShakeMap downloads page is reliable and consistent, and if there is a finite fault model for the event, the rupture.json file should eventually be updated to use the finite fault polygon coordinates (but this doesn’t always happen, see below for Atacama). For instance, the 2024 Hualien earthquake rupture.json file contains the same coordinates as the finite fault polygon file: https://earthquake.usgs.gov/product/shakemap/us7000m9g4/us/1717621264531/download/rupture.json. The 2023 Kahramanmaraş ShakeMap rupture.json files contain the rupture geometries which are absent in the corresponding finite fault polygon files: https://earthquake.usgs.gov/product/shakemap/us6000jllz/us/1681495642674/download/rupture.json and https://earthquake.usgs.gov/product/shakemap/us6000jlqa/us/1699129736996/download/rupture.json.
The M7.4 earthquake in Atacama, Chile last month is a case where a finite fault model is available, and the finite fault polygon file does contain the rupture coordinates: https://earthquake.usgs.gov/realtime/product/finite-fault/us7000n05d_1/us/1721493598903/shakemap_polygon.txt, but the ShakeMap rupture.json file was not updated to use the finite fault polygon coordinates and is still a point source: https://earthquake.usgs.gov/realtime/product/shakemap/us7000n05d/us/1721354540462/download/rupture.json. This means that the final ShakeMap for this event is using a point source representation of the rupture even though a finite fault model was created for the event.
Anirudh's proposal was that we should always prefer the rupture.json file. If the rupture.json file polygonal geometry, we need to convert that into an OpenQuake rupture format. The strike and dip are not needed in this case and so the text boxes on the webui must be greyed out. If the rupture.json file contains just a point source, we need to enable the strike and dip text boxes on the webui for the user to enter values, and use those values to construct the rupture polygon along with the magnitude and hypocenter.
This means that for events like the M7.4 Atacama, we would also start from a point source even though a finite fault model is available for the event. If the user wishes to use the finite fault information, they should convert it into an OpenQuake rupture.xml file and use the upload option.
If the user uploads a rupture.xml file, the strike and dip are not needed and so the text boxes on the webui must be greyed out.
That leaves the case when the rupture.json file is not available (could happen in the first few minutes or hour after the event). In this case, we need to extract the magnitude, lat, lon, depth of the event from the USGS event page. In this case, we need to enable the strike and dip text boxes on the webui for the user to enter values, and use those values to construct the rupture polygon along with the magnitude and hypocenter.
from oq-engine.
Related Issues (20)
- Think about disabling numba in same places
- Calculate consequences from multiple perils (ground shaking and sep) for each asset
- openquake Hazard run job.ini crash Memory Error!!! HOT 7
- Improve error handling
- use of region_grid_spacing in a conditioned gmf produces a key error now HOT 2
- Access to additional variance components of GMM standard deviation models HOT 6
- Imported CSV ruptures cannot exported
- Incorrect documentation for Afshari Stewart 2016 HOT 1
- Extend read_geometries to the case of a non-unique field
- Mention `create_jobs` and `run_jobs` in the documentation
- ARISTOTLE: disable the `Run a Calculation` button
- multifault msparams issues HOT 2
- acme_2019.py throws np.RankWarning error HOT 1
- ARISTOTLE: test the workflow using the finite-fault data HOT 1
- Add a warning to the WebUI login page about the possibility to be banned
- Incorrect imports listed at top of GSIM module
- Adjustments for US NSHM GMPEs HOT 6
- New CAV models HOT 4
- Kotha 2020 files missing from pip install
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from oq-engine.