SimCenter Forum

Hi Anne,

From the log.txt it seems that the app does not find ground motion events, wondering if you could please try to select ground motion records in the EVT panel (please feel free to check out detailed steps here: https://nheri-simcenter.github.io/EE-UQ-Documentation/common/user_manual/examples/desktop/eeuq-0004/README.html).

And please feel free to get me back if you still have the same or any other issue!

Regards,
Kuanshi

Hi Anne,

This issue might be related to the screen resolution.  Can you try to change the resolution in the "Settings" (https://support.microsoft.com/en-us/windows/change-desktop-icon-size-or-screen-resolution-c6626736-5bb0-e094-7f03-49c828ff5da3, https://support.apple.com/guide/mac-help/change-your-displays-resolution-mchl86d72b76/mac#:~:text=display%20is%20connected.-,On%20your%20Mac%2C%20choose%20Apple%20menu%20%3E%20System%20Preferences%2C,click%20Displays%2C%20then%20click%20Display.&text=Press%20and%20hold%20the%20Option,option%20for%20the%20second%20display.).

If this does not work out, maybe try to use mouse to resize the message window either laterally or vertically, just to see if the view can be recovered. Please let me know if these could help to resume the view and maybe we could schedule a meeting to sort this issue out together.

Thanks,
Kuanshi (kuanshi@stanford.edu)

Thank you for these great questions, nsk! I'm happy to respond to the first three mainly related to the HAZ tab.
1. The hazard and ground motion selection module mainly supports scenario-based simulation (given an earthquake scenario, simulating the resulting spatial correlated intensity map and selecting ground motions).
2. The ground motions for each grid site are selected based on the site's target response spectra (including median and standard deviation). The target response spectra are computed conditional on the given magnitude and site-to-source distance. Meanwhile, both the inter-event and between-event correlations are considered in computing these target spectra.
3. The "Earthquake Name" is taken by the tool to look for rupture sources whose name contains the "Earthquake Name" string in the ERF. The tool would also filter the plausible ruptures by the user-defined earthquake characteristics (e.g., magnitude) if any. And then the tool would randomly sample one plausible rupture in the remaining ruptures for the selected earthquake scenario.

Hi Mariana and kubee77,

The updated Anchorage example is now available via the link: https://github.com/NHERI-SimCenter/R2DTool/tree/master/Examples/Earthquake3_Anchorage, which is configured for running on the newly released rWhale-2.3.0 (https://www.designsafe-ci.org/rw/workspace/#!/rWhale-2.3.0u1#workspace).

To submit the analysis job in the DesignSafe workspace, please first zip the "input_data" folder and select it as the "Regional Simulation Data" in the "Inputs" widget; and then select the "rWHALE_Anchorage.json" as the "Workflow Configuration File". The v2.3.0 also allows to run a subset of the entire building inventory by specifying "filter for buildings to run" (e.g., 1-10 for running the first 10 buildings", 1,3-10 for skipping the second building) - or specifying the "filter" in the configuration file.

We're working on the documentation of these updated examples along with the R2DTool and backend applications, please check out the latest documentation page: https://nheri-simcenter.github.io/R2D-Documentation/, and feel free to come back to us if you have questions or comments.

Regards,
Kuanshi

Yes, Mariana - the source code of latest rWHALE is available in SimCenter repo SimCenterBackendApplications: https://github.com/NHERI-SimCenter/SimCenterBackendApplications.

Hi wangcb98, the issue comes from the recent commit by the OpenSHA-1.5.2 (https://github.com/opensha/opensha-commons/commit/5fea7ff95faa3b1ece47fe4c97b5dbcfcd5e8cee) where the site data were moved to the commons and their corresponding servlet paths were updated, so the old url in OpenSHA-1.4.0 cannot be recognized anymore.

The solution is to rebuild your EQHazard with the updated dependency to the OpenSHA-1.5.2. It can resolve the issue of "null" ground motion in your case. We're now in the process of testing other examples before making a merge commit. But you're welcome to check out the current source code from https://github.com/kuanshi/GroundMotionUtilities/tree/opensha152.