SimCenter Forum

Hello. I would like to use the uq module to create a truncated lognormal fragility curve. I currently use stats.lognorm(beta, scale=median).pdf(x) to get a lognormal fragility curve so I'm hoping for something that could give me a similar result but with a truncation. Any suggestions?

Hello,

I want to check whether each AutoSDA gm causes yield in the building. (I am using it to cross-check the Taghavi-Miranda modal approximation, which is limited to linear responses.) The best way I can think of is to compare the max base shear to the pushover curve. Is it possible to include max base shear as an output?

Thanks,
Anne

Hello,

I've gotten some surprising results when changing the number of records for the AutoSDA analysis.

1) I tried to run 1 gm so that I could get the design/model files stored locally before running more gms on DesignSafe. This caused an error.

2) 2 gms ran locally but sampled from the same two records to populate 11 rows in the results.

3) I tried to run 16 gms on DesignSafe to see if it only sampled 11 of them. The job says it finished but when I retrieve the results I get a blank table in the Data Values tab. This might be because I accidentally selected SRSS instead of H1 but I'm having a hard time testing it because my jobs are getting stuck in a queue. I'm attaching the log file. The zipped tmp folder is too big and looks like it's just input files anyway.

Hello,

Is there a way to get pushover results from the AutoSDA analysis? It looks like they have been commented out of the main_program script. Speaking of which, I'm a little surprised to see that the Eigen Value Analysis has also been commented out, given that I am still getting eigen value results, such as the first few periods of the building.

If you could help me confirm how to get all the results, in particular the pushoever curve, I would appreciate it.

Thanks,
Anne

Hi Kuanshi,

I just discovered that the poe terms in the oq .ini files is for the investigation time, not annual. Could you update line 238 in FetchOpenQuake.py to be (something like):

1 - np.exp(-n_years * (1/RP))

Thanks,
Anne

Hello,

It looks like the AutoSDA edps above the 10th story are getting collected incorrectly. The attached results have identical edp for the 11-15th and the 1-5th stories. See this (unrestricted) folder for the backend files: https://drive.google.com/drive/folders/1ZjFFgGKpcCBHp27bh84q2LogAQgC1jKI?usp=sharing

Also, would it be possible to collect the peak drifts, in addition to the displacements and accelerations?

Thanks,
Anne

Thanks to Kuanshi for fixing the Z1.0 and Z2.5 conversion from the SiteFile.csv to the OpenQuakeSiteModel.csv!

The new file looks good but OpenQuake crashes when it tries to run it. Here's a link to the working directory, accessible by Kuanshi and Adam: https://drive.google.com/drive/folders/17H0H3Xe-yV-EW1N9O3b6xVzPqgstskOR?usp=sharing

I reran it all in PowerShell (see the uploaded .txt file in the linked folder), using:

python "C:/Users/ahul697/Desktop/R2D/build_date\\applications\\performRegionalEventSimulation\\regionalGroundMotion\\HazardSimulation.py"   --hazard_config   "C:/Users/ahul697/Documents/R2D/LocalWorkDir\\HazardSimulation\\GroundMotions\\Input\\EQHazardConfiguration.json"

The 09_15 build gets to the same spot and crashes at :

FetchOpenQuake: OpenQuake configured.
ERROR 1: PROJ: proj_create_from_database: Cannot find proj.db
PROJ: proj_create_from_database: Cannot find proj.db
INFO:root:Upgrade completed in 0.000997304916381836 seconds
WARNING:root:DB server started with C:\Users\ahul697\Anaconda3\python.exe on tcp://127.0.0.1:1908, pid 23532
[2021-09-15 16:12:08 #4 WARNING] The parameter 'trucation_level' is unknown, ignoring
FetchOpenQuake: Classical PSHA failed.

I then reran the files in the LocalWorkDir using the 08/23 build (also in the .txt file), hoping that it would retrieve the correct OpenQuakeSiteModel.csv file. It was able to run and produce results, however, it recreated the .csv file, using the old scripts that didn’t correctly include Z1.0 and Z2.5.

Note that both the 09/15 and 08/23 builds include the line:
[2021-09-15 16:12:08 #4 WARNING] The parameter 'trucation_level' is unknown, ignoring.
I’m curious about what that means. But, regardless, the unique issue for the 09/15 build seems to be the missing proj.db file.

Thanks,
Anne

Hello,

The EVT page of EE-UQ includes a pulldown for the acceleration component of interest. As this is part of the record selection, it would be more intuitive if it were placed above the "Select Records" button. I'm attaching a suggestion.