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

Pages: [1]
Thank you for the prompt response! I appreciate the input.

Essentially, I'd like to run through the entire EE-UQ workflow as I would in the application but have the ability to run a set of building simulations back-to-back and store the results locally (as opposed to re-running manually in the GUI).

In general, the only pieces of the workflow I'll be using are:
SIM - both user-specified OpenSees models and AutoSDA
EVT - a suite of PEER NGA records
FEM - an OpenSees analysis script
EDP - Standard Earthquake

The only parts of the workflow I will be varying across analyses are:

  • SIM: the building model
  • EVT: the scaling of the ground motions

So the MATLAB routine would ideally run each analysis and store the results locally.

Good evening, all! Just wanted to ask for best practices if I would like to run EE-UQ within a MATLAB routine.

Based on previous posts, my understanding is that record selection must be done prior to running the backend (the PEER NGA record selection feature wouldn't be available), and the "Multiple PEER" option should be selected.

To run the full analysis, would I need to "loop" through each downloaded ground motion and run the EE-UQ workflow using a custom BIM.json file for each iteration?

I'm just brainstorming at this stage, so any input on (1) if my understanding on the implementation is correct and (2) the specific lines of code needed to run each analysis would be much appreciated.

Thank you!

Greetings, all - I am trying to leverage the Steel Building Model (Auto-SDA) feature in EE-UQ, but am currently unable to complete the analysis - I'd appreciate any pointers/advice you have.

I have the latest version of EE-UQ installed on Windows, and previous analysis types (MDOF, OpenSees) have worked well in the past. On my end, I am able to run Auto-SDA on my PC (the Github Python version), if that makes a difference.

UQ: 2 samples

Steel building model: the default model is used.

EVT: 2 ground motions selected using the PEER-NGA West 2 database (ASCE 7-10 Design Spectrum with default parameters, Acceleration components set to SRSS).

FEM: No analysis script defined

EDP: Standard Earthquake

RV: None defined

All paths in preferences set to default.

Here is the error I encounter:
An error occurred in the Python script, the exit code is 1.

I've attached:
  • debug.log- the last line reads: FileNotFoundError: [Errno 2] No such file or directory: 'dakotaTab.out'
  • log.txt

While the templatedir folder is partially populated, the dakota.out files are not generated. I can pull some more information from my end if needed. I appreciate it!

Pages: [1]