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 - kuanshi

Pages: [1] 2 3 4
1
Earthquake Engineering (EE-UQ) / Re: Validating the Surrogate Model
« on: June 16, 2023, 01:24:49 AM »
Hi Gaurav,

Good questions and thanks so much for the interest of using the surrogate modeling in EE-UQ and quoFEM!  I'm trying to first brief a potential use case of the PLoM package in EE-UQ/quoFEM and then write my thoughts to your questions - hope they could be helpful if any.

Let's consider the uncertainty in earthquake source, path, and local soil condition, one would except different ground motions given a specific return period. If we select a set of representative ground motions and use them for response history analysis of the structure, the ground motion uncertainty is propagated to the uncertainty in the resulting structural responses.  Let's assume one ground motion could be described by a set of M intensity measures (e.g., PGA, PSA...) and we're interested in P different responses (e.g., peak displacement/peak acceleration), a (M+P)xN matrix can be constructed (with N realizations).  The PLoM package could help on two possible tasks: (1) it can learn this matrix and generate new realizations that preserve the data structure and (2) it can generate new realizations in which a few dimensions have moments per user-defined values (e.g., the mean Sa of input matrix is 0.6g while the mean Sa of new realizations is moved to 0.4g) by adding corresponding constraints (e.g., the target mean Sa, 0.4g).  So, the PLoM package develops a mapping between the joint distributions of input parameters and output responses (e.g., mapping a sample of PSA to a sample of responses).

> For the first question, it may not be straightforward to validate one PLoM realization at a particular SAavg (it's a single realization given the SAavg though one could potentially generate sufficient sets of PLoM realizations and then estimate the statistics); alternatively, it's more easier to validate one set of PLoM realizations at a particular mean SAavg - one could first compute the mean SAavg of the validation set and provide that as a constraint, then the comparison would be made between the statistics of the responses from PLoM and the validation set.

> For the second question, if I understand correctly, ground motion selection/scaling (e.g., https://www.nist.gov/publications/selecting-and-scaling-earthquake-ground-motions-performing-response-history-analyses) seems what you were asking for.  Given the target intensity measures (e.g., PSA), one could select recordings that fit the target intensity measures, and spectral matching algorithms may also be considered if desired.

> For the LOOCV, similar to the first questions, it may not be straightforward to do one data point (PLoM is intended to focus on the joint distribution instead of individual points).

Hope the above discussion could be helpful if any and please do feel free to get us back if you have any trouble of running the PLoM package and/or  have any needs that we could help on to extend/gear the package better for your use case.

Regards,
Kuanshi

2
Hi Francisco,

The problem might be caused by the python path in the preference dialog (it currently seems to be directed to anaconda's python instead of your x86 python3.9 install) - could please try to update that to your new python3.9's path to see if it could help resolve the issue.

Kuanshi

3
Hi emongold,

Sorry about the late reply and thank you so much for sharing the input files with us!  I'll look into this issue and get you back soon.

Regards,
Kuanshi

4
Hi mcetink,

Sorry about the issue encountered in the user-defined EDPs - this could be related to the restructuring of the backend applications between v2.5.1 and v3.0.0 (so the old json configuration may need to be converted with new attribute keys/values to be processed by the version after 3.0.0).  It would be greatly appreciated if you could provide us with an example including the user-defined EDP script and an old version json input file, and we could help to look into and troubleshoot the error. 

Sorry about this inconvenience again and many thanks in advance,
Kuanshi

5
Hi Emily,

Thank you for providing the feedback to us!  Yes, I can add an option for excluding point sources in the rupture forecast model.  In the meantime, as we're extending the toolbox involving the OpenSHA in R2D, wondering if it would be also useful to support using logic tree for a set of user-defined OpenSHA ruptures - if so the point-source filter can be also designed along with the logic tree feature - but the point-source filter itself would not be very difficult and I would work on that first and let you know soon after I have a testing version.

Thanks,
Kuanshi

6
Regional Hazard Simulation (R2D, rWhale) / Re: Length of value error
« on: April 08, 2022, 07:15:27 PM »
This post is related to the topic the emongold and SimCenter developers are working together to add a new feature in R2D backend application to calculate ground motion maps for multiple scenarios in one run (where calculating multiple records per site for a single scenario is supported in the current release).

Thank you, emongold, for sharing the example input configuration and site file.  While this function along with relevant patches are under development, a developer version of the backend application that can be built from the linked repository https://github.com/kuanshi/SimCenterBackendApplications/tree/RegionalSiteResponse for testing the example, and please feel free to get us back if you have any comments or suggestions!

-Kuanshi

7
Regional Hazard Simulation (R2D, rWhale) / Re: Simulated hazard magnitude
« on: February 07, 2022, 05:13:10 PM »
Hi Emily,

Thank you so much for giving feedback and sharing more details!  Yes, following your suggestions, maybe we can add two new features to the tool: (1) defining the number of earthquake scenarios (this will be in conjunction with the current number of ground motions per site per scenario) and (2) scenario sampling.  The scenario sampling can support (a) using a distribution of magnitude or/and distance (distribution can be uniform or (log)normal) and (b) using the mean annual frequency as the weight.  Please feel free to let me know if these two described features fit to your need (and I would start working on them then), or maybe we could have a follow-up zoom.

Regard,
Kuanshi

8
Hi alfred,

Thanks for sharing the snapshot of the error message and reaching out to us for the running issue.  It seems the hazard simulation job is not launched correctly. One possible cause is cannot load java, so it might be helpful if you could check if java is installed on the computer (https://nheri-simcenter.github.io/R2D-Documentation/common/user_manual/installation/desktop/install_Windows.html#install-java), as it is needed for invoking OpenSHA jar library.  In the meantime, it would be appreciated if you'd like to share the sample input folder with us, so we could help to replicate and debug the problem.  The input folder "HazardSimulation/GroundMotions/Input" is under the "Local Jobs Directory" which could be found by clicking "File"->"Preference"->"Local Jobs Directory" (as highlighted in the attached snapshot).

Best,
Kuanshi

9
Regional Hazard Simulation (R2D, rWhale) / Re: Simulated hazard magnitude
« on: February 03, 2022, 07:38:08 PM »
Yes, Emily - the current R2D supports simulating ground motion maps (as defined by the number of ground motion) for the selected scenario in one run - so the magnitude is for that selected scenario.  Please feel free to let us know if you'd like to sample/run multiple scenarios in one job and maybe we could discuss details and upgrade the feature in to the future release.

Best,
Kuanshi

10
Regional Hazard Simulation (R2D, rWhale) / Re: Simulated hazard magnitude
« on: February 02, 2022, 02:50:06 AM »
Hi emongold,

Yes, the earthquake magnitude and MAF for the ground motions are saved in SiteIM.json, which is located under the local work directory (e.g., "C:/Users/user_name/Documents/R2D/LocalWorkDir/HazardSimulation/GroundMotions/Output").  You can find an attribute "Earthquake_MAF" in the SiteIM.json which reports the earthquake magnitude.  Please feel free to get me back if you have trouble accessing it.

Regards,
Kuanshi

11
Earthquake Engineering (EE-UQ) / Re: number of records for AutoSDA
« on: October 08, 2021, 06:22:10 AM »
Thanks for the feedback, Anne!  The user and developer team had met and resolved the issue together.

Regards,
Kuanshi

12
Earthquake Engineering (EE-UQ) / Re: record max base shear for AutoSDA
« on: October 08, 2021, 06:22:03 AM »
Hi Anne,

The shear could be recorded by using the "User Defined" option in the EDP panel.  I've attached two tcl scripts for getting story shear values (along with other EDPs in the "Standard Earthquake" option).  "MyRecorder.tcl" helps to create recorders in OpenSees and "MyPostprocess.tcl" helps to prepare a results.out file for dakota to parse the output.  Since the number of story and number of bays are specified by users, so please also modify "num_story" and "num_bay" in these two tcl scripts accordingly.  In addition to load these two scripts, EDP names are also needed by adding them via the "Add" button in the EDP panel.  Please see the attached "user-defined-edp.png" where EDP names follow the format: 1-EDP-story-direction (e.g., first story shear in X direction: 1-V-1-1).  Please feel free to download and test them.

Regards,
Kuanshi

13
Earthquake Engineering (EE-UQ) / Re: number of records for AutoSDA
« on: October 07, 2021, 07:58:33 AM »
Hi Anne,

Sorry about the confusion,

(1) currently EE-UQ always expects the job has at least one random variable (either the random variable defined in RV or multiple ground motion events) but running 1 gm with a deterministic model could still be achieved by defining a dummy variable in RV (with a non-constant distribution, please see an example in the attached "dummy-RV.png" and "dummy-RES.png").

(2) yes, EE-UQ would receive and use the "# Samples" in UQ->Dakota to set up the number of samples with sampled random variables (including ground motions) - when the number of selected motions (in EVT) is less than the "# Samples", samples with repeated motions would happen which corresponds to (not limited to) the user case of investigating the response sensitivity to structural modeling parameters.

(3) For the issue on DesignSafe - we tested the run on DesignSafe but could not replicate the problem - Thanks for sharing the log.txt from which the remote application is still v2.3.0. Could you please check the "Preferences" (File->Preferences) that "Remote Applications Directory" is "/work2/00477/tg457427/stampede2/SimCenterBackendApplications/v2.5.0" - and click the "Reset" button to automatically recover the settings if not. Please let us know if this could help resolve the remote run issue.

Thanks,
Kuanshi

14
Earthquake Engineering (EE-UQ) / Re: retrieving tmp files from DesignSafe
« on: October 06, 2021, 09:46:23 PM »
Hi All,

The Save Data button is updated in the recent release, please feel free to download and test it via https://www.designsafe-ci.org/data/browser/public/designsafe.storage.community//SimCenter/Software/EE_UQ.  And yes, the periods.out will be available in the planned release on December.

Best,
Kuanshi


15
Hi Anne,

Yes, I can add an option for using the _SearchResults.csv to load the records and this will be included to the features for the next minor version release planned on December - but will get you back once it is available for developer built testing.

Thank you,
Kuanshi

Pages: [1] 2 3 4