Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jyzhao

Pages: [1] 2
1
Hi Bofan,

This issue should have been solved in the latest release, in which "simcenter-rWHale-frontera-4.4.0u1" is the default Tapis App ID as defined in R2D preferences.

Please try to use the latest version posted on DesignSafe.

Best,

Jinyan

2
Hi Bofan,

I am sorry that the documentation section you pointed out is outdated, and the running on DesignSafe function has been moved to the R2D graphical user interface.

To run on DesignSafe, you can set up the running workflow in a similar way as running locally. After, you can submit the job to DesignSafe by clicking the "RUN at DesignSafe" button next to the "RUN" button on the R2D user interface. Some instructions are provided at the bottom of https://nheri-simcenter.github.io/R2D-Documentation/common/user_manual/usage/desktop/usage.html.

Hope this helps.

Jinyan

3
To run on DesignSafe, please change the Tapis App ID to "simcenter-rWHale-frontera-4.4.0u1".

Please let us know if there are any other issues.

Best,

Jinyan

4
Hello,

Thanks for using SimCenter forum.

For the first question, it is likely because a new Python is installed and set as the default Python on your computer. The new Python may not be compatible with SimCenter Apps. Could you please reply with the operation system you are using and the Python path defined in your R2D "preferences" menu bar? If you are using a MacOS, you can see info at "https://nheri-simcenter.github.io/R2D-Documentation/common/user_manual/installation/desktop/install_macOS.html#install-python-3-9" about how to get the correct Python to use.

For the second question, we are investigating and will let you know the results as soon as possible.

Best,

Jinyan

5
Hi Bofan,

Thanks for using the SimCenter forum.

To better understand the issue. Can you share the "GroundMotions" folder in your SimCenter LocalWorkDir/HazardSimulation folder with me?

Thanks and regards,

Jinyan

6
Hello,

If you add the three lines at the bottom of this message before Line 295 in the link I sent you in my previous reply, You will be able to set the location of the hypocenter.

Please note that 1. These lines set the location of the hypocenter but not the epicenter. The hypocenter needs to be defined on the fault surface with a depth, and you can add "print(rupSurface.getEvenlyDiscritizedListOfLocsOnSurface().toString())" before Line 295 to check the geometry of the fault surface. 2. The hypocenter defined here is only used by Cambell & Bozorgnia (2014) ground motion models and nowhere else in the backend calculation. If you would like to define the hypocenter for other use, please let us know, and we will see how we can help.

Hope this is clear.

Jinyan

rup = rupList.get(rupture_index)
rup.setHypocenterLocation(Location(33.97, -117.91 , 0))
rupList.set(rupture_index, rup)

7
Hello,

Thanks for using the SimCenter forum.

Defining the location of hypocenter is not available through editing the configuration Json file, but it is possible by editing the SimCenterBackendApplication python code at https://github.com/NHERI-SimCenter/SimCenterBackendApplications/blob/master/modules/performRegionalEventSimulation/regionalGroundMotion/FetchOpenSHA.py#L295.

However, please note that the GMM selected in your configuration Json file (Boore et al. (2014)) does not use the hypocenter location, and defining the hypocenter location will not make a difference to the predicted ground motions. The only GMM in R2D that uses the hypocenter location is (Campbell and Bozorgnia (2014)). This GMM uses the depth of the hypocenter, and R2D uses the mean of the upper and lower fault edge depth as the hypocenter depth by default. This is reflected in the code linked above and can be edited if you would like to.

I hope this addresses your questions. Should you have any more questions, please don't hesitate to reach out.

Best,

Jinyan

8
Regional Hazard Simulation (R2D, rWhale) / Re: Error in DL calculation
« on: March 11, 2024, 07:18:41 PM »
Hello Bofan,

This is a flaw of the software that the output format of the earthquake simulation tool is different from the input format of R2D HAZ panel. The earthquake simulation tool uses "SA(0.01)" to represent spectral acceleration at 0.01s, while the HAZ panel uses "SA_0.01" (See the input files of R2D example 14 at https://github.com/NHERI-SimCenter/R2DExamples/blob/master/E14BasicHAZUSTransportation/input_data/IMs/S_001_1000.csv for an example) to represent spectral acceleration at 0.01s.

To resolve this issue, please rename the columns in the output of the earthquake simulation tool so the R2D HAZ panel can read the files.

Thank you for catching this error and we will fix this in the future release. We apologize for the confusion.

Best,

Jinyan

9
Hello,

The original data (1.84M buildings) described in our San Francisco testbed was produced by our partner, and we are not permitted to share the data. However, SimCenter has produced a similar inventory containing around 1M buildings, and the data is publicly available on DesignSafe at https://doi.org/10.17603/ds2-z5sx-zh27.

Hope this is clear.

Jinyan

10
If the UCERF earthquake rupture forecasting model is used, the uncertainty of the source model is considered in UCERF. For OpenQuake ERF, uncertainty is typically considered with logic trees. However, logic trees are not implemented in R2D now. After earthquake scenarios are generated, R2D uses empirical ground motion prediction equations to generate ground motion intensity measure fields. The uncertainty of GMPEs is considered by modeling the IMs as random fields with distributions as specified in the spatial correlation models. Hope this answers your questions.

Best,

Jinyan

11
The earthquake hazard scenarios in R2D are generated using either UCERF or OpenQuake. Some details are described at https://nheri-simcenter.github.io/R2D-Documentation/common/user_manual/usage/desktop/R2DTool/tools.html#earthquake-scenario-simulation.

12
The minimum building information depends on the types of analysis you would like to perform in the workflow. In general, the minimum building information is the geological location of the building and the information needed to carry out the structural model specified in the MOD panel and the damage and loss model in the DL panel. You could refer to the built-in R2D examples for what information is needed for typical R2D use cases.

13
Yes, it is possible to select MOD as None and use user-provided fragility.

However, the "IMasEDP" option, instead of "None", should be selected in ANA. Otherwise, R2D will not link the intensity measures to the provided fragility curves.

Regards,

Jinyan

14
Hello,

This is the maximum distance from the site "centroid" to the source.

Please note the site "centroid" is roughly estimated by taking the average value of the latitude and longitude values of all sites. It is not the geometry centroid of the sites.

Hope this helps.

Jinyan

15
Regional Hazard Simulation (R2D, rWhale) / Re: R2D extent of the region
« on: January 16, 2024, 06:34:28 PM »
Hello,

This depends on the complexity of the analysis/assessment you would like to perform. If you plan to perform a Hazus-style assessment, where a structural analysis model is not needed, and damage and loss are obtained directly from fragility curves, you should be able to assess a state using a very powerful personal computer or DesignSafe's High-performance Computer (HPC) provided through R2D. The biggest challenge here might be preparing and managing big inventory data and hazard information data for such a region. This requires very large memory and storage space.

If you plan to perform structural analysis models in your assessment, you might need more powerful computers. You might be able to require more computational resources from DesignSafe if you are eligible for DesignSafe's criteria. If you have your own HPC resources, you could also contact us, and we could help set up R2D's backend applications on your HPC. Please let us know more specifics of your plan so we can better assist you.

Regards,

Jinyan

Pages: [1] 2