The OpenSees Community

That is fantastic, thanks! So many gems in your blog.

I'm curious if there is any way of doing a linearly varying load in OpenSees. My understanding is no right now, but I could have missed something.
Linearly varying loads are seen a lot in foundations, and it would be fun to use OpenSeesPy for this design task.

Hey,

I'm looking to create a wrapper of the OpenSeesPy package that includes dostrings. The dream is that this will automatically be generated from the .rst files.

Basically convert this:
https://github.com/zhuminjie/OpenSeesPy ... Length.rst

To this:


To do this I need to parse all .rst accurately and get the arguments among other things. However, I'm struggling with understanding the possible arguments - could someone in the know lend me a hand?

As I understand it we have 9 possibilities, see a-i:




a - start tag
used to denote the specific type of "sub function", they affect the entire function behavior.
b - a standard argument.
These always occur before any "tagged" arguments
c - chevron optional argument group start
The beginning of an optional argument group. Some optional arguments are grouped by chevrons, I'm not sure why..
d - chevron optional argument group middle/end
The middle/end of an optional argument group
e - chevron tag
A optional argument tag. Only the inner text is passed as an argument. For example <-'TAG'> is included, only the string '-TAG' is passed to the argument.
f - tag
These are used to denote 'special' inputs, and are followed by a set of arguments.
g - tag argument
These are arguments that follow an input tag. Sometimes they are optional, sometimes they are required. They always occur after basic arguments.
h - tag wrapped optional argument:
A optional argument. These may be needed for different dimensions? I'm not sure why these are different than other optional arguments.
h - basic optional argument:
A optional argument.

Does this sound correct? Any category I may be missing?

There are tutorials here that show using OpenSeesPY with functions:
https://www.youtube.com/watch?v=scemwqZ ... 9a7bqFN6zG

(disclaimer - I recorded those..)

Hey Michael,

Thanks for your response on github and here. This works perfectly. I forgot you could use the eleResponse command with additional arguments.
For anyone else reading, the following command will do what I want.

out = op.eleResponse(1, 'section', '1', "fiberData" )

For most non-fiber elements we don't even input section dimensions, so manual input will be required either way to thicken elements.

C.

Hey,

Maybe a little late, but the pip version is currently updating.
The get rendering is updated on github but not pip.

If you manually install the files everything should work!
Hopefully the pip version will be updated soon.

Cheers,
C.

Hey,
Right now OpenSeesPy needs to be updated to python 3.8.
The new version should be up sometime in the next two weeks or so.

If you are using anaconda, you can create a python 3.7 virtual environment and run OpenSeesPy there.
something like:

conda create -n yourenvname python=3.7 anaconda
conda activate yourenvname

Plenty of good resources on using these environments online!

Cheers,
C.

Hey Michael
Thanks for your response.

That makes sense - would that output would be through a recorder command, or is there any output command for fibre locations?
i.e. sectionFiber(eleTag, secNum) = [fibre_x, fibre_y, fibre_z]

What about non-fibre sections/elements?

I'm wondering if anyone knows of a convenient way to get the section geometry for an element already in a OpenSeesPy model.

I'm working on a few post-processing scripts for OpenSeesPy.
If I knew of a way to get section info about an element, it would be possible to plot thickened elements and do a whole host of other things.

Micheal, that is incredibly useful to know about the fibre sections!
I spent my entire masters degree thinking it was not possible to recorder individual fibers in OpenSees.
I'm wondering what the scope is for string arguments?
For example, it seems like for the node recorder, using ints in python works okay. Is it just element commands that are getting tripped up?

For anyone:
My assumption always was that the overhead from recorders in OpenSeesPy was less than the overhead from using Python output commands.
Pavan, it seems like your experience was opposite to this.
I'm curious, has anyone stress tested a model using both methods?