EE-UQ Dakota Error

[mcetinkaya91]

Hi,

I run EE-UQ locally and I get the following error: Error from Dakota: Error(s) encountered reading results file workdir.7\results.out for Evaluation 7: — Expected 14 function value(s) but found 0.

I don't know what this error could be related to. Any help on how to troubleshoot it is greatly appreciated.

[fmckenna]

go to ~/Documents/EE-UQ/LocalWorkDir/tmp.SimCenter/workdir.7 .. there is a file sc_driver.sh or .bat if windows .. run it from the command line (terminal if mac, cmd or powershell if windows) .. see that the error is when the workflow runs for that 1 sample that is contained in workdir.7

[mcetinkaya91]

Thank you. I have done it, and screenshot from the powershell is shown below. Looks like that particular run is not complete because one of the modeling parameters turn out to be undefined. I use concrete building modeler as Simulator model in EE-UQ, in which I define column and beam dimensions as random. It appears that the "slx" turns out undefined because "nsb-1" (the denominator in the function of "slx" ) turns out 0. I am not sure how "nsb" is defined and what does it stand for. I think if I figure out how "nsb" is defined in the backend and whether it is defined based on any section dimensions, I might limit the range of my random variables to make sure "slx" do not end up undefined. For that, is the RC_FIAP_main.py in ~\EE_UQ_\applications\createSAM\RCFIAP\RC_FIAP_main.py only source to look at, or is there any other source I need to look at as well?

[fmckenna]

i just checked and yes it is the only place. if you are having difficulties with the code I can reach out to the developers

[mcetinkaya91]

Yes that would be great. I think I need to know what the parameter "nsb" stands for and how it is defined based on the input information. And what are the things that the user should pay attention to not to have "nsb" as 1 so that the parameter "slx" does not en up undefined. Looking forward to their response, thank you so much!

[mcetinkaya91]

Hi, I am just following up if there is any update on this. Thank you.