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 ... 7 8 [9] 10 11 ... 16
121
Wind Engineering (WE-UQ) / Re: Running WE-UQ EVT
« on: May 03, 2021, 06:26:46 PM »
1 and 2 could be same issue, i.e. no random variable.

go to the SIM panel. If using the stick model unaltered, put in wFloor for weight. Then go to RV tab and for a normal distribution put in a mean value, say 150 and a stddev say 10 just to see if you get out some numbers .. then try and run again.

122
Wind Engineering (WE-UQ) / Re: Running WE-UQ EVT
« on: May 03, 2021, 03:35:50 PM »
1) the error is likely due to fact that you defined no random variables for the building. you need to create at least one random variable for the building when you use the CFD option and then provide information on the variables distribution. you can create a variable named "dummy", specify it to be of type normal and enter a value for mean and stdDev if you have no actual random variables.

2) can you send the .out and .err files from designsafe. also the dakota.in and dakota.out files that are in the tmp.SimCenter directory if present.

123
Earthquake Engineering (EE-UQ) / Re: Strain energy calculation
« on: May 03, 2021, 03:26:56 PM »
there is no command in OpenSees that directly calculates and returns the strain energy .. you would have to write some script that would loop over all ele and all gauss points and would have to be element specific

124
Wind Engineering (WE-UQ) / Re: numeric assignment for the pset command
« on: April 27, 2021, 10:01:47 PM »
yes that is something we should do .. i will add it to our list of things to do and place it in our Jira system for inclusion in our 2.3.0 release of the tool (i will try for 2.2.0 release but that is due out tomorrow!)

125
Hydrodynamic Engineering (Hydro-UQ) / Re: FEATURE: Requests from meetings on 16th & 22nd April
« on: April 23, 2021, 05:53:35 AM »
Ajay

we should discuss which ones should be added to Jira.

126
Wind Engineering (WE-UQ) / Re: existing event file format
« on: April 17, 2021, 04:55:35 AM »
in an analysis step it increments the pseudo time by 0 .. in opensees the applied load is given by the load factor obtained from the time series for the current time multiplied by the reference loads in the load pattern .. so for this case it uses the very first value in the time series as the loadFactor.

127
Wind Engineering (WE-UQ) / Re: existing event file format
« on: April 12, 2021, 06:49:10 PM »
if you look at the example.tcl script, you see the first analysis step after the wind loading is created is not actually a transient step, but a static one .. which is why no ramp was needed

128
Wind Engineering (WE-UQ) / Re: constraint handler
« on: April 12, 2021, 06:46:15 PM »
for your analysis script do include a constraint handler .. the default one built in is the Transformation method .. if you would like other options let us know.

129
General Questions / Re: Running on DesignSafe
« on: April 12, 2021, 06:28:18 PM »
the queue it defaults to is set up for maxNodes = 256

130
Wind Engineering (WE-UQ) / Re: existing event file format
« on: April 08, 2021, 10:04:55 PM »
it should be. it should be an initial load applied under static analysis before the dynamic analysis begins so the building does not get a sudden impact load. it is that way in current code base; not 100% sure it is in what you have. we are releasing a new version of this app (should have been done this week but late) .. you can check the example.tcl file in a workdir.X dir to see how it is currently being handled.

131
Wind Engineering (WE-UQ) / Re: recorders not generated
« on: April 06, 2021, 09:20:13 PM »
Hi,

is this resolved or do you need more help?

frank

132
Wind Engineering (WE-UQ) / Re: existing event file format
« on: April 06, 2021, 09:19:21 PM »
I attach an example. This was generated from WE-UQ using the stochastinc option for a 2 story building. It is in JSON format, basically there is an EVENT object that defines some patterns and time series, a pattern for each floor for each dof (the example only provides for dof 1). If you understand OpenSees the idea of a time series and load pattern should be familiar. If you need more keep posting.

ps. when you run the examples locally if you go to your Documents folder there will be a new directory WE-UQ. thta dir wil contain a file debug.out we use to track down issues and another folder tmp.SimCenter. In there there will be. folder templatedir, some dakota files and if it ran succesfully a whole bunch of workdir.X directories. You can go into any of those directoris and have a look atthe files. The workflowdriver file is the series of commands that is run for each sample. If you ever have problems, you can run that script to see the errors. I like to sometimes look at the .tcl file here to see what the errors are.

133
Earthquake Engineering (EE-UQ) / Re: Running EE-UQ backend using Command Line or MATLAB
« on: April 01, 2021, 05:47:10 PM »
ok. I will update the doc to show people how. basically:

1) if you look in ~/Documents/EE-UQ/LocalWorkDir/tmp.SimCenter after you run from the GUI there are files dakota.out and dakotaTab.out containing the results and a directory templateDir .. the templatedir should have a file dakota.json.
2) dakota.json is the output of the UI when you hit run and it is the input file for the application femUQ.py that actually runs the workflow causing the 2 output files to be generated.
3) you start femUQ by invoking python (you possibly might have to start in same dir as the input file (dakota.json).
4) fewUQ.py takes some additional arguments. if you look in ~/Documents/EE-UQ there is a debug.log file and in there search for something like PYTHON COMMAND . this is how the frontend UI is invoking the backend application and it will show you these additional args.
5) that line will also show that we are adding stuff to the env variable, adding OpenSees, dakota, and possibly python to the env setting of the process that runs. you will have to add these to your env variables if you run from outside the UI.
 
my PYTHON COMMAND line looks like:

PYTHON COMMAND "source $HOME/.bash_profile; export PATH=/Library/Frameworks/Python.framework/Versions/3.8/bin:/Users/fmckenna/release/EE-UQ/build/EE_UQ.app/Contents/MacOS/applications/opensees/bin:/Users/fmckenna/release/EE-UQ/build/EE_UQ.app/Contents/MacOS/applications/dakota/bin:$PATH; \"/Library/Frameworks/Python.framework/Versions/3.8/bin/python3\" \"/Users/fmckenna/release/EE-UQ/build/EE_UQ.app/Contents/MacOS/applications/Workflow/femUQ.py\" runningLocal \"/Users/fmckenna/Documents/EE-UQ/LocalWorkDir/tmp.SimCenter/templatedir/dakota.json\" \"/Users/fmckenna/release/EE-UQ/build/EE_UQ.app/Contents/MacOS/applications/Workflow/WorkflowApplications.json\""

when i run from the terminal i need to take off the \", basically this:

python3 /Users/fmckenna/release/EE-UQ/build/EE_UQ.app/Contents/MacOS/applications/Workflow/femUQ.py runningLocal   /Users/fmckenna/Documents/EE-UQ/LocalWorkDir/tmp.SimCenter/templatedir/dakota.json
/Users/fmckenna/release/EEUQ/build/EE_UQ.app/Contents/MacOS/applications/Workflow/WorkflowApplications.json

so python3 <path to femUQ.py> runningLocal <path to input file> <path to WorkflowApplications.json>


134
Earthquake Engineering (EE-UQ) / Re: EE-UQ with Steel Building Model - error: Dakota files not generated
« on: March 31, 2021, 11:11:36 PM »
the log file has following message:
C:\SimCenter\EE-UQ\EE-UQ\applications\python\python.exe: can't open file 'C:/SimCenter/EE-UQ/EE-UQ/applications/createSAM/AutoSDA/main_program.py'

can you see if that file exists on your machine. If not, can you try downloading again the application and check for that file again.

thanks and sorry.

135
Earthquake Engineering (EE-UQ) / Re: Running EE-UQ backend using Command Line or MATLAB
« on: March 31, 2021, 11:08:10 PM »
the Event tab specifies the type of event application . the current event applications do one of two things:
1) go off and do the record selection and get the motions ready for when the backend runs
2) create/get the motions as part of the running backend.

just exactly do you want the Matlab function to do?

Pages: 1 ... 7 8 [9] 10 11 ... 16