SimCenter Forum
Research in Natural Hazards Engineering [Archived] => Earthquake Engineering (EE-UQ) => Topic started by: mhaindl on September 23, 2020, 04:02:24 AM
-
Hello!
When trying to run the same example that was presented on the EE-UQ training webinar I get this message: "Failed to run the workflow!!!".
I saw the same problem that was posted for other SimCenter application, but could not find the solution.
I already followed the installation steps posted on the SimCenter website.
When trying to run the example at DesignSafe, the message that I get is: "Local Failure Setting Up Dakota".
I am running EE-UQ Application on a Windows 10 machine.
Thank you
-
go to the ~/Documents/EE-UQ/LocalWorkDir/tmp.SimCenter folder and tell me what is there.
-
Hi,
There is a folder called templatedir and inside is a file called dakota.json. Nothing else
Best regards.
-
can you put that dakota.json file in the attachments
-
Yes, sure.
Please see attached.
Thank you.
Best regards
-
the issue was resolved. the problem was that the application was not pointing to a python exe. the solution was to download python 3.7 version from python.org and install it. then in the file prefereences do a reset. the application was able to find python and it ran successfully.
-
Yes, great!
It runs now. Thank you very much for your help.
Best regards.
-
I am trying to run EE-UQ for the steel building model (Guan et al. 2020), but i'm getting the same message. I have attached my log file.
Thanks,
-
1) if you lookin the Documents/EE-UQ/LocalWorkdir/tmp.SimCenter directory can you check if a file dakota.in exists
2) can you provide info on which version of EE_UQ you are running?
-
1) if you lookin the Documents/EE-UQ/LocalWorkdir/tmp.SimCenter directory can you check if a file dakota.in exists
2) can you provide info on which version of EE_UQ you are running?
1) Yes, there is a dakota.in file in this location
2) I am using 2.2.0 (latest version)
Thanks,
-
sorry about the delay i was attending some intensive training course. in the location where the dakota.in file was is there some workdir directories. if not, the program is not finding dakota. if there, the simulations are failing. if it is the simulations tar up one such directory and include it or send it to me.
-
sorry about the delay i was attending some intensive training course. in the location where the dakota.in file was is there some workdir directories. if not, the program is not finding dakota. if there, the simulations are failing. if it is the simulations tar up one such directory and include it or send it to me.
There are no workdir directories when I run it for the steel building model, for MDOF model however these directories are generated and it works fine.
-
can you include the dakota.json for the steel building model ..
-
can you include the dakota.json for the steel building model ..
Attached.
Thanks
-
can you send the files in C:/Users/moein/Documents/EE-UQ/LocalWorkDir/tmp.SimCenter/templatedir\\autosda_files
-
can you send the files in C:/Users/moein/Documents/EE-UQ/LocalWorkDir/tmp.SimCenter/templatedir\\autosda_files
Attached.
Thanks,
-
one last file .. the debug.log in your Documents/EE-UQ folder
there looks to be a few things wrong. to start with the backend application is not starting which is possibly due to the python interpreter not being found. I will see where the program thinks python is from the debug.log file.
-
one last file .. the debug.log in your Documents/EE-UQ folder
there looks to be a few things wrong. to start with the backend application is not starting which is possibly due to the python interpreter not being found. I will see where the program thinks python is from the debug.log file.
Debug log attached.
Thank you,
-
After reviewing your `dakota.json` file, it looks like you assigned a random variable for a building parameter, i.e., perhaps you set H1 to represent the height of the first floor. Currently, the setting of random variables is only supported in the Loading table. Note that for this example, in FEM->OpenSees FE Application, the ConvergenceTest parameter should be: EnergyIncr 1.0e-3 300
-
I am also getting the same error message despite downloading, installing, and setting the Python path. Any assistance is greatly appreciated.
-
this should probably be in a new thread, but i cannot move it .
first off, under file or the app in menubar there should be a preferences option, select it. Does the python location point to the python exe you installed?
if it does, there are a number of things we will need to do to track this down:
1) look in your Documents/EE-UQ folder. there is a file debug.log. the end of the file may show errors related to why failing.
2) in the LocalWorkdir/tmp.SimCenter/templatedir dir there should be at least a dakota.out file (this is the input file for the python app)
3) look in LocalWorkDir/tmp.SimCenter, there is a file log.txt if python was found (look in it for obvious errors, i.e. a python module not loaded)
4) if the UQ engine started there should be a number of workdir.X folders in tmp.SimCenter (if they exist the analysis is failing)
can you post the debug.log, dakota.in, log.txt and a worflow.X compressed folder as attachments in your next post.
thanks and sorry.
-
The Python location does not point to the Python exe that I have installed.
1) From the debug.log, the error shows that the "dakota.out" file does not exist.
2) There is not dakota.out file in the location specified.
3) Attached.
4) The EEUG engine was able to start; however, there are no workdir.X folders. There is only a "templatedir" folder.
I have attached the files. Any assistance is appreciated, thank you.
-
can you send the dakota.json file in templatedir. i am not seeing the cause for the error in what you sent. the dakota.json file is the input file for backend which i can load to see the options you have chosen