gem / earthquake-scenarios Goto Github PK

When running the notebook the following error appears for the example for Puebla

AttributeError                            Traceback (most recent call last)
----> 3 # Read file using pandas
      4 
      5 stations = read_usgs_json(json_path)
      6 

~/earthquake-scenarios/src/usgs_stations_json_csv.py in ?(json_path)
     46 
     47         # Iterate over different columns. Each colum can be a component
     48         data = []
     49         pgas = []
---> 50         for index, chan in rec_sation.iteritems():
     51             try:
     52                 if chan["name"].endswith("Z") or chan["name"].endswith("U"):
     53                     continue

~/openquake/lib/python3.9/site-packages/pandas/core/generic.py in ?(self, name)
   5985             and name not in self._accessors
   5986             and self._info_axis._can_hold_identifiers_and_holds_name(name)
   5987         ):
   5988             return self[name]
-> 5989         return object.__getattribute__(self, name)

AttributeError: 'Series' object has no attribute 'iteritems'

The current gmfs indicated for Gorkha can be improved by:

• Add rupture model and estimates from the rupture geometry defined by Stevens et al. 2018
• Include gmpe logic tree from NSET
• Evaluate and incorporate macroseismic information to condition gmf

The following studies consider macroseismic data for the characterisation of the ground shaking:

1. Martin SS, Hough SE and Hung C (2015) Ground motions from the 2015 Mw 7.8 Gorkha, Nepal, Earthquake constrained by a detailed assessment of macroseismic data. Seismological Research Letters 86(6): 1524–1532. DOI: 10.1785/0220150138. https://doi.org/10.1785/0220150138
2. Hough SE, Martin SS, Gahalaut V, et al. (2016) A comparison of observed and predicted ground motions from the 2015 MW7.8 Gorkha, Nepal, earthquake. Natural Hazards 84(3). Springer Netherlands: 1661–1684. DOI: 10.1007/s11069-016-2505-8. https://doi.org/10.1007/s11069-016-2505-8
3. Adhikari SR, Baysal G, Dixit A, et al. (2017) Toward a unified near-field intensity map of the 2015 Mw 7.8 Gorkha, Nepal, Earthquake. Earthquake Spectra 33(Special issue 1): S21–S34. DOI: 10.1193/120716EQS226M. https://doi.org/10.1193/120716eqs226m
4. McGowan SM, Jaiswal KS and Wald DJ (2017) Using structural damage statistics to derive macroseismic intensity within the Kathmandu valley for the 2015 M7.8 Gorkha, Nepal earthquake. Tectonophysics 714–715. Elsevier B.V.: 158–172. DOI: 10.1016/j.tecto.2016.08.002. https://doi.org/10.1016/j.tecto.2016.08.002
5. Adhikari, Sujan & Guragain, Ramesh & Murakami, Hitomi. (2016). Study on shaking intensity distribution of the 2015 Gorkha earthquake in Nepal. Conference: International workshop on the first memorial day of 25th April, 2015, Gorkha Earthquake at Kathmandu, Volume: I.

Requesting Changes

The local experts in El Salvador have requested a change in the name for the two events in the country. I would suggest to follow their suggestions (see below) to the make the events more familiar to users in El Salvador:

Issues

1. In El_Salvador/20010113_M7.6_SanMiguel/Recording_Stations there seems to be additional station images that do not belong to this event. Two are for events in Haiti, and another one for an event in Kashmir. These should be removed.

2. job.ini files in the OpenQuake_gmfs do not work out of the box. The rupture files cannot be found because the path provided in the job.ini are of the following form:

rupture_model_file = ../Ground_Shaking/Rupture/earthquake_rupture_model_GCMT.xml

However, the Ground_Shaking folder is not there. By removing that folder from the path the job.ini files work properly. I experienced this in the scenarios for El Salvador, but might be in the files for other countries as well

The current gmfs can be improved:

[ ] Japan/Kobe 1995: Add the gmf "Stations: Seismic, gmlt: USGS, Rupture: USGS";
[ ] Botswana/Moijabana 2017: Fix the GEM logic tree;
[ ] Tanzania/Bukoba 2016: Fix the GEM logic tree.

Currently the event only uses the recording stations from the USGS.

The SGC_station_data.csv reports different values. It is important to check the latest information from the USGS and generate a unified file with the latest information.

For example, based on the current numbering/sorting, it seems 3_3_run_oq_scenarios.ipynb should be run before 3_oq_gmmLT_from_usgs_shakemap.ipynb. However, one needs a gmmLT to run the models.

When parsing the stationlist.json file from the USGS, stations marked as outliers are being included.

Add in the notebook 1_stations_usgs_json_to_csv.ipynb the option to highlight and remove outliers.

For example, for the event "20010213_M6.6_SanVicente" in El Salvador, the stations TO - Tonacatepeque and ZA - Zacatecoluca are highlighted as outliers.

There's a requirement for USGS station data, but some events (e.g., 1989 Salima) don't have any station data in USGS.

Organise folders to be compatible with the GRM regions:

• Africa
• Caribbean_Central_America
• Central_Asia
• East_Asia
• Europe
• Middle_East
• North_America
• North_Asia
• Oceania
• South_America
• South_Asia
• Southeast_Asia

We use contextily for basemaps. Our default option in the notebooks is Stamen Terrain, but that is no longer supported in contextily (see geopandas/geopandas#3065). Alternate options to Stamen.TonerLite might include CartoDB.Positron, CartoDB.VoyagerLabelsUnder, OpenTopoMap, Esri.WorldGrayCanvas, OpenStreetMap.Mapnik, etc.

The full list of options is here: https://contextily.readthedocs.io/en/latest/providers_deepdive.html#What-is-this-%E2%80%9Cprovider%E2%80%9D-object-?

The site model generated using the scr/3_2_oq_vs30_uniform_grid.ipynb is producing duplicated sites. Below a configuration example to replicate the issue:

# Events list from ECD
event = 'DRAFT_20230817_M6.1_ElCalvario'

# Reference rupture
rupture = 'earthquake_rupture_model_USGS.xml'

# Grid parameters in km
# Indicate tuples with: (x_distance, y_distance, grid_spacing)
corners = [(100, 100, 5), (250, 250, 10)]

# Define region CRS !!! (CRS UNITS MUST BE IN METERS)
# Check for reference (see https://spatialreference.org/)
region_crs = "EPSG:3857"  # EPSG:3857 - Web Mercator Auxiliary Sphere

# Clip sites based on country boundaries (use ISO3)
clip_countries = ['COL'] # Empty list for the full map

The error message is:

...

openquake.baselib.InvalidFile: Found duplicate sites {(-72.61278, 3.52155): 2, (-72.61278, 3.61121): 2, (-72.61278, 3.70086): 2, (-72.61278, 3.79049): 2, (-72.61278, 3.88013): 2, (-72.61278, 3.96975): 2, (-72.61278, 4.05936): 2, (-72.61278, 4.14896): 2, (-72.61278, 4.23855): 2, (-72.61278, 4.32813): 2, (-72.61278, 4.4177): 2, (-72.61278, 4.50726): 2, (-72.61278, 4.59681): 2, (-72.61278, 4.68634): 2, (-72.61278, 4.77587): 2, (-72.61278, 4.86538): 2, (-72.61278, 4.95489): 2, (-72.61278, 5.04438): 2, (-72.61278, 5.13385): 2, (-72.61278, 5.22332): 2, (-72.61278, 5.31277): 2} in /earthquake-scenarios/Colombia/20230817_M6.1_ElCalvario/OpenQuake_gmfs/site_model.csv

Currently, the model input files for 20230206_M7.8_KahramanmarasGaziantep include only the site_model.csv and not the site_model_europe.csv.

The GEM logic tree uses ground motion models from ESHM20, notably KothaEtAl2020ESHM20SlopeGeology. This ground motion model requires additional inputs, which are not available from the standard script used to generate the site_model.csv. Since we resolved this already with other European events (e.g., 20161026_M6.09_CentralItaly), perhaps we can run the Europe iteration of the site model code also for Turkey?