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

Pages: [1] 2 3 ... 12
Regional Hazard Simulation (R2D, rWhale) / Re: JOB BLOCKED
« on: November 16, 2022, 10:49:58 PM »
sorry for the delay in responding. can you open the tool, go to preferences and tell me the tapis app id .. should be the last one in the window. sorry and thanks

Regional Hazard Simulation (R2D, rWhale) / Re: Hurricane database
« on: November 15, 2022, 09:17:37 PM »
i am looking into the source code .. there should be a file ibtracs.last3years.list.v04r00.csv in a folder Databases in the applications folder (note if you are on a mac the app is actually a directory and you can cd into from the terminal .. the R2D.exe is located in the following and Datanases should be a folder there) .. can you tell me if the folder and file exists .. thanks and sorry

AI use in Regional Simulation (BRAILS) / Re: Modules not being imported
« on: October 25, 2022, 03:40:29 PM »
while waiting .. as part of SimCenter training there was an AI workshop held this summer .. Day 3 contains some material and in particular notebooks for crack detection you might want to look at to get you started.

AI use in Regional Simulation (BRAILS) / Re: Modules not being imported
« on: October 25, 2022, 10:17:32 AM »
Sorry for your struggles. The examples you are using are for version 2.0.x of BRAILS

The examples that you were using do not work in current version. I have updated the example page. The person responsible for BRAILS is away till Thurs, at which time I will get him to provide more examples and show how to pre-train to get better results for local areas.

General Questions / Re: Extrude doesn't follow enclosed area
« on: October 24, 2022, 11:03:39 PM »
what NHERI SimCenter tool are you using?

if using the dakota option in quoFEM, you can use the file generated by a dummy run of the tool and modify that dakota input file to put lower (and upper) bounds on the lognormal random variables.

for future users, the lower and upper bounds could be added to quoFEM if deemed useful?


can you be a bit more specific. thanks

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.

Can you open up the Preferences pane for the tool and tell me what is the "Tapis App" that is listed.

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.

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.

Wind Engineering (WE-UQ) / Re: Error Using CFDBeginner and CFDExpert
« on: June 30, 2022, 09:27:31 PM »

Can you go to the designsafe portal and go to the workspace area: 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.


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.

Aakash, what are the circumstances for which the is going to be the same in each workdir.

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/$PATH; \"/Library/Frameworks/Python.framework/Versions/3.8/bin/python3\" \"/Users/fmckenna/release/SimCenterBackendApplications/applications/Workflow/\" 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 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/$PATH;
/Library/Frameworks/Python.framework/Versions/3.8/bin/python3 /Users/fmckenna/release/quoFEM/build/
 runningLocal /Users/fmckenna/Documents/quoFEM/LocalWorkDir/tmp.SimCenter/templatedir/scInput.json /Users/fmckenna/release/quoFEM/build/

    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.

Pages: [1] 2 3 ... 12