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

Pages: [1] 2
Thank you for your response.

1) The frame remains linear elastic when subjected to the loads I'm currently using...

2) I should certainly change the recorders to a nicer looking and more compact format. How can I go from 104 to 10? I have 48 recorder files. The rest of the files in the local directories are the main .jason file and other input files.

- I tried running a simulation with the default stick model in WE-UQ at DesignSafe, but that didn't go through either. I got the same problem as with my 2D frame model. The analysis either fails or is finished with no output. I don't know what I'm doing wrong while running at DesignSafe. I was able to run the 2D frame locally with 1000 samples. But I can't handle more samples locally.

it takes about 3 hours to run on my PC I think. It is a 20-story frame (2D) with panel zones and concentrated plasticity elements. So, lots of nodes and elements. I have modified the recorder and processor files as well. Could this be the problem? I separated the node recorders for each story. So the program should create lots of output files. I have attached my model in here. 


I tried a simulation with 100 samples, 100 nodes, 32 processors, and max time of 40 hours. After almost 10 hours of being in queue, the analysis has suddenly changed status to finished without giving me output. I checked the status of the analysis every now and then when it was in queue, and I didn't see any other status than queue. It was in queue all day, and then suddenly the status changed to finished.

If I use larger number of nodes or processors, or a higher max time, the analysis fails immediately. The above numbers were the highest I could choose.

Thank you so much for your quick response. I will try a smaller sample size and higher number of nodes.

How can I know from the Dakota.out file that samples have been finished or not? I have attached the Dakota.out file for one of my simulations in here. It is written in there that each evaluation has been added to queue and then assigned to a specific peer. But no information is given about the completion of the processes. Does this mean that non of the processes have been completed?

I tried running the simulation on Designsafe again. This time the simulation is completed :) but does not give me any output. The individual work directories are not even generated.

I tried a second time. This time, 32 out of 1000 work directories are created, but the recorders inside them are empty. The DakotaTab file is accordingly generated without any data (it contains only headers).

I'm trying another simulation with fewer number of samples (500 samples) to see if I can get results.

Could this be an issue related to the archiving stage? 


When I specify large number of samples in a forward propagation problem using LHS, my simulation fails. I have tried running this both on my laptop and on Designsafe:

- On the laptop, I get the error "Dakota has stopped working". If I choose the debug option, it says "an unhandled exception occurred in [11756] Dakota.exe".

- On Designsafe, the job status turn to "failed" and it says "APPS_USER_APP_FAILURE Failure indicated by Slurm status TIMEOUT with user application return code: 0:0".

* I have previously run this model for 32768 time steps with only one random variable and one sample using WE-UQ without any errors and got results comparable to deterministic OpenSees simulation results.
* I have also run the model as a test with only two time steps and 26 random variables and 30 samples successfully.

So I think the issue might not be because of the way the model and WE-UQ parameters are set up. It seems like it is due to the large number of samples. But I don't know why and how to resolve it.

Thank you,

Wind Engineering (WE-UQ) / Re: numeric assignment for the pset command
« on: April 28, 2021, 06:57:40 AM »
sounds great, thank you!

Wind Engineering (WE-UQ) / numeric assignment for the pset command
« on: April 27, 2021, 07:26:27 PM »

When I use the pset command with an expression instead of a number like below:

pset mass_roof [expr 40.06/(2.*6.*12.)] 

the "mass_roof" random variable doesn't appear in the tool. I can replace the expression with a number for this specific case. But is it possible to be able to have expressions as inputs as well?

Wind Engineering (WE-UQ) / Re: correlation between RVs in LHS method
« on: April 19, 2021, 10:11:39 PM »
That's great, Thank you!

Wind Engineering (WE-UQ) / correlation between RVs in LHS method
« on: April 17, 2021, 03:45:35 AM »
In the current version, are the RVs uncorrelated? Does the shuffling approach in the current LHS sampling method configured in a way to prevent spurious correlations between RVs?

Wind Engineering (WE-UQ) / Re: existing event file format
« on: April 14, 2021, 07:09:21 AM »
ok thank you, I saw the static analysis parameters in the example.tcl file now. But I don't understand what this means:

integrator LoadControl 0.0
analyze 1

This is an OpenSees question, I guess. But I don't know what a load factor increment of zero does. Does this take the first input in the wind loading time series and apply that statically to the building? If yes, then the value assigned to "staticWindLoad" in the event.jason file is unused.

General Questions / Re: Running on DesignSafe
« on: April 12, 2021, 06:07:52 AM »
Just wondering how many nodes and processors is ok to use when running on DesignSafe? I think I remember 64 processors per node from a WE-UQ video tutorial. But I don't remember how many nodes we can use.   

Wind Engineering (WE-UQ) / Re: constraint handler
« on: April 12, 2021, 05:16:02 AM »
Thank you so much for you swift response. I am referring to the definition of the analysis engine parameters in the FEM module of the WE-UQ tool. They include "analysis", "integration", "algorithm", "convergence test", and "solver". But I don't see a constraint option. I just wonder how constraint equations are handled by the program, and whether or not I need to include the constraint command in my tcl file when I am uploading an analysis script?

Wind Engineering (WE-UQ) / constraint handler
« on: April 12, 2021, 04:56:50 AM »

I'm just curious to know why isn't there a "constraint" section in the FEM section of WE-UQ?


Wind Engineering (WE-UQ) / Re: existing event file format
« on: April 10, 2021, 04:17:40 AM »
Well that is great! I didn't know about that, so I have added a ramp at the beginning of my loading histories to prevent sudden dynamic impact.

I couldn't find anything in the example.tcl file about "StaticWindLoad". I am just wondering what is the timeSeries type using which this load pattern is applied to the structure? Is it a linear timeSeries to create a ramp? If that is the case, then it's so nice since I don't have to add the ramp manually to the loading histories.

Pages: [1] 2