61
AI use in Regional Simulation (BRAILS) / Re: The strings for available modules are missing in the doc
« on: October 10, 2022, 06:29:31 PM »
Charles.
can you be a bit more specific. thanks
can you be a bit more specific. thanks
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.
62
Regional Hazard Simulation (R2D, rWhale) / Re: Run at DesignSafe returns status BLOCKED
« on: September 20, 2022, 11:49:59 PM »
sorry for delay.
we are going to need to see some log.txt files. Where they are depends on if running locally or remotelly. Can you confirm which.
we are going to need to see some log.txt files. Where they are depends on if running locally or remotelly. Can you confirm which.
63
Regional Hazard Simulation (R2D, rWhale) / Re: Run at DesignSafe returns status BLOCKED
« on: August 26, 2022, 09:15:12 PM »
Can you open up the Preferences pane for the tool and tell me what is the "Tapis App" that is listed.
thanks.
frank
thanks.
frank
64
Performance Based Engineering (PBE) / Re: Error running PBE App with Openseespy file for Model
« on: August 22, 2022, 04:04:54 PM »
At the moment there is no direct means to do so .. you could have a Tcl script invoke the openseespy interpreter to create the model and perform the analysis .. you will have to understand the EVENT file and the outputs requested to do so.
65
Wind Engineering (WE-UQ) / Re: Error Using CFDBeginner and CFDExpert
« on: July 07, 2022, 07:15:29 PM »
from the main menu can you open the preferences and set the app to simcenter-openfoam-dakota-1.3.0u2 from simcenter-openfoam-dakota-1.3.0u1
thanks and sorry for the delay.
thanks and sorry for the delay.
66
Wind Engineering (WE-UQ) / Re: Error Using CFDBeginner and CFDExpert
« on: June 30, 2022, 09:27:31 PM »
Hi,
Can you go to the designsafe portal and go to the workspace area: https://www.designsafe-ci.org/rw/workspace and under workspace select the Tools and Applications options. Now on the very right of that page is a very narrow column titled Job Status .. click on the Job Status text and the column open up to show all your jobs .. select the 'More Info' for one of these jobs and send a picture of the error message.
thanks
frank
Can you go to the designsafe portal and go to the workspace area: https://www.designsafe-ci.org/rw/workspace and under workspace select the Tools and Applications options. Now on the very right of that page is a very narrow column titled Job Status .. click on the Job Status text and the column open up to show all your jobs .. select the 'More Info' for one of these jobs and send a picture of the error message.
thanks
frank
67
Regional Hazard Simulation (R2D, rWhale) / Re: Result Displaying Request
« on: June 11, 2022, 06:49:58 AM »
you need to open up Preferences and point the path to the Python interpreter. The interpreter is required to have the NHERI-simCenter module pip installed.
68
Uncertainty Quantification (quoFEM) / Re: Bayesian Calibration -identical params in workdirs-
« on: June 06, 2022, 07:07:33 PM »
Aakash, what are the circumstances for which the params.in is going to be the same in each workdir.
69
Uncertainty Quantification (quoFEM) / Re: FEATURE: application for running backend directly
« on: June 06, 2022, 06:52:11 PM »
1. We are updating the doc on this type of usage, here is a heads up if you want to try in out .. you can get back to me if you have issues (it will help me with the documentation, the other helper is an undergraduate student here at Berkeley). But the simplest way to get what you need is to run quoFEM locally once. In your Documents folder you will find a directory quoFEM and in that directory a file called debug.log. That file contains a line starting with PYTHON COMMAND: (mine looks like the following)
a. you need to create a folder in which quoFEM will run the input
b. in that folder, create a folder named templatedir
c. in templatedir, place all files that will be needed (including the input file for workflow .. we call it scInput.json if you are using the current quoFEM application)
d. from the terminal you need to issue a few commands (those commands will depend on where the application is installed and what your operating system is). I have modified the quoFEM application to when they run locally spit out these commands to the debug.log file (The debug.log file is located in your ~/Documents/quoFEM directory after you start the application and run a local run). Writing this I think I should also modify the application to pop up these commands in a dialog.
The debug.log file contains in it a line with the words "PYTHON COMMAD" which you can search for. The following was in my debug.log file.
PYTHON COMMAND "source $HOME/.bash_profile; export PATH=/Library/Frameworks/Python.framework/Versions/3.8/bin:/Users/fmckenna/release/WE-UQ/build/WE_UQ.app/Contents/MacOS/applications/opensees/bin:/Users/fmckenna/release/WE-UQ/build/WE_UQ.app/Contents/MacOS/applications/dakota/bin:$PATH; \"/Library/Frameworks/Python.framework/Versions/3.8/bin/python3\" \"/Users/fmckenna/release/SimCenterBackendApplications/applications/Workflow/sWHALE.py\" runningLocal \"/Users/fmckenna/Documents/WE-UQ/LocalWorkDir/tmp.SimCenter/templatedir/scInput.json\" \"/Users/fmckenna/release/SimCenterBackendApplications/applications/Workflow/WorkflowApplications.json\"" ()
From this line you can create a .bat file or a .sh file (depending on your operating system) .. that file splits up the command above into a number of line & removes the \" .. for example, I would create a run.sh file from the above with the following:
source $HOME/.bash_profile;
export PATH=/Library/Frameworks/Python.framework/Versions/3.8/bin:/Users/fmckenna/release/quoFEM/build/quoFEM.app/Contents/MacOS/applications/opensees/bin:/Users/fmckenna/release/quoFEM/build/quoFEM.app/Contents/MacOS/applications/dakota/bin:$PATH;
/Library/Frameworks/Python.framework/Versions/3.8/bin/python3 /Users/fmckenna/release/quoFEM/build/quoFEM.app/Contents/MacOS/applications/Workflow/qWHALE.py
runningLocal /Users/fmckenna/Documents/quoFEM/LocalWorkDir/tmp.SimCenter/templatedir/scInput.json /Users/fmckenna/release/quoFEM/build/quoFEM.app/Contents/MacOS/applications/Workflow/WorkflowApplications.json
This file I copy now to templatedir and run.
2.A second approach underway is creation of a jupyter notebook created that is an example of using the quoFEM backend that is being finished. It will be done by end September.
a. you need to create a folder in which quoFEM will run the input
b. in that folder, create a folder named templatedir
c. in templatedir, place all files that will be needed (including the input file for workflow .. we call it scInput.json if you are using the current quoFEM application)
d. from the terminal you need to issue a few commands (those commands will depend on where the application is installed and what your operating system is). I have modified the quoFEM application to when they run locally spit out these commands to the debug.log file (The debug.log file is located in your ~/Documents/quoFEM directory after you start the application and run a local run). Writing this I think I should also modify the application to pop up these commands in a dialog.
The debug.log file contains in it a line with the words "PYTHON COMMAD" which you can search for. The following was in my debug.log file.
PYTHON COMMAND "source $HOME/.bash_profile; export PATH=/Library/Frameworks/Python.framework/Versions/3.8/bin:/Users/fmckenna/release/WE-UQ/build/WE_UQ.app/Contents/MacOS/applications/opensees/bin:/Users/fmckenna/release/WE-UQ/build/WE_UQ.app/Contents/MacOS/applications/dakota/bin:$PATH; \"/Library/Frameworks/Python.framework/Versions/3.8/bin/python3\" \"/Users/fmckenna/release/SimCenterBackendApplications/applications/Workflow/sWHALE.py\" runningLocal \"/Users/fmckenna/Documents/WE-UQ/LocalWorkDir/tmp.SimCenter/templatedir/scInput.json\" \"/Users/fmckenna/release/SimCenterBackendApplications/applications/Workflow/WorkflowApplications.json\"" ()
From this line you can create a .bat file or a .sh file (depending on your operating system) .. that file splits up the command above into a number of line & removes the \" .. for example, I would create a run.sh file from the above with the following:
source $HOME/.bash_profile;
export PATH=/Library/Frameworks/Python.framework/Versions/3.8/bin:/Users/fmckenna/release/quoFEM/build/quoFEM.app/Contents/MacOS/applications/opensees/bin:/Users/fmckenna/release/quoFEM/build/quoFEM.app/Contents/MacOS/applications/dakota/bin:$PATH;
/Library/Frameworks/Python.framework/Versions/3.8/bin/python3 /Users/fmckenna/release/quoFEM/build/quoFEM.app/Contents/MacOS/applications/Workflow/qWHALE.py
runningLocal /Users/fmckenna/Documents/quoFEM/LocalWorkDir/tmp.SimCenter/templatedir/scInput.json /Users/fmckenna/release/quoFEM/build/quoFEM.app/Contents/MacOS/applications/Workflow/WorkflowApplications.json
This file I copy now to templatedir and run.
2.A second approach underway is creation of a jupyter notebook created that is an example of using the quoFEM backend that is being finished. It will be done by end September.
70
General Questions / MOVED: Bayesian Calibration -identical params in workdirs-
« on: June 01, 2022, 08:15:48 AM »
This topic has been moved to Uncertainty Quantification (quoFEM).
http://simcenter-messageboard.designsafe-ci.org/smf/index.php?topic=268.0
http://simcenter-messageboard.designsafe-ci.org/smf/index.php?topic=268.0
71
Uncertainty Quantification (quoFEM) / Re: Bayesian Calibration -identical params in workdirs-
« on: June 01, 2022, 07:51:48 AM »
we will need to see the input file to start solving this one. If running locally it will be in ~/Documents/quoFEM/LocalWorkDir/tmp.SimCebter/templatedir. It is either dakota.json or scInput.json depending on version of quoFEM. We will probably need more, but if you can post this we can see what else is needed/
72
Regional Hazard Simulation (R2D, rWhale) / Re: Result Displaying Request
« on: May 31, 2022, 04:28:26 PM »
Are you running locally or remotely. If Remote, can you run locally to see if it fails. If Local can you go to your Documents/R2D/LocalWorDir/tmp.SimCenter .. there should be a file inputRWHALE.json and a directory input_data. For now can you post the inputRWHALE.json file. If there is a Resuts dir, there should be a log.txt file. Can you attach that file as well. We may need the input_data folder.
73
Site Response Analysis (s3hark) / Re: Progress bar
« on: May 30, 2022, 03:45:22 AM »
Amber,
It should have given you an error if you left the path to OpenSees from the line edit. Does OpenSees exist on your system in the location shown in the image posted?
1) If yes, can you check OpenSees runs by trying to run opensees from a terminal window. If it fails to run, you will need to install it and provide the path to it. If it does run, we will need to set up a zoom call to sort out the issue.
2) If not, can you download OpenSees and provide that path to it.
frank
It should have given you an error if you left the path to OpenSees from the line edit. Does OpenSees exist on your system in the location shown in the image posted?
1) If yes, can you check OpenSees runs by trying to run opensees from a terminal window. If it fails to run, you will need to install it and provide the path to it. If it does run, we will need to set up a zoom call to sort out the issue.
2) If not, can you download OpenSees and provide that path to it.
frank
74
Uncertainty Quantification (quoFEM) / Re: QUOFEM offline?
« on: May 23, 2022, 06:33:46 PM »
are you trying to launch the DCV application at DesignSafe or are you running the application locally?
1) If the former, you need to be part of the DCV allocation at DesignSafe. To gain access submit a ticket requesting access https://www.designsafe-ci.org/help/new-ticket/
sorry about this, it is something we just became aware of and we are updating the dcv tool page with this info.
2) if this message is coming from your desktop application, does the job run locally and is it just failing when you hit the run at designsafe button. If just designsafe, can you open up the applications preferences and tell me what the remote app id is.
thanks
frank
1) If the former, you need to be part of the DCV allocation at DesignSafe. To gain access submit a ticket requesting access https://www.designsafe-ci.org/help/new-ticket/
sorry about this, it is something we just became aware of and we are updating the dcv tool page with this info.
2) if this message is coming from your desktop application, does the job run locally and is it just failing when you hit the run at designsafe button. If just designsafe, can you open up the applications preferences and tell me what the remote app id is.
thanks
frank
75
Educational Applications / Re: TFT does not run properly with M1
« on: May 10, 2022, 05:44:27 PM »
I have rebuilt the app, code signed it and bundled it again. We have tested an a colleagues M1 and it works. I have uploaded that revised dmg.