You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
Indeed the GEM logic tree does use the GMM from ESHM20 which needs specific parameters that are added using an adaptation of the script from Graeme (https://gitlab.seismo.ethz.ch/efehr/esrm20_sitemodel). Unfortunately this script currently only works with European countries (the inputs for countries outside Europe are not yet available) and because of it for any event that also affects a non-European country it is not possible to generate the site_model_europe.csv file. Graeme has already been notified of this and said whenever he could he would try to make the script global but we will have to wait for this implementation.
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?The text was updated successfully, but these errors were encountered: