The OpenSees Community

To bump a 6 year old thread, I finally got back around to addressing this. For those of you interested in using the code Frank posted, it requires some other OpenSees framework. It is available in its entirety in SRC/handler. 'make test' will produce a binary that can be used. When the socket is ope...

I now have access to the machine. Two of us are going to tackle compiling this weekend. Our cluster compiling skills are a little weak. If you have any helpful pointers, we would appreciate it. I was considering starting with Makefile.def.LINUX_Redhat_EL5, since Lonestar is CentOS 5.5. If you think ...

When I get access to Lonestar I will pursue this. I was a little bit hesitant of the MAKES directory, since most of the Makefiles.def haven't been updated in 1000s of days. For example, Makefile.def.LONESTAR is significantly older than the cluster (perhaps it was for a previous incarnation). Unfortu...

Lonestar seems to be the new Intel-Linux cluster on the block. It seems perfectly suited for OpenSees. Has anybody compiled a binary on Lonestar?

What Teragrid resources have OpenSees binaries available for them? This week NCSA Abe will be shutting down, forcing me to find a new home. I have access to LONI Queen Bee and NCSA Abe. Compiling OpenSees seems to be a complicated procedure.

Any help is appreciated.

Thanks,
Dan

I would like to second this request. It is common to "wrap" another program like MATLAB around OpenSees (i.e., generate input, run OpenSees, analyze output). It would be useful to pass errors (such as convergence issues) and state information back upstream without having to analyze the console text....

An up to date Makefile.def would probably suffice. The one in the source code does not seem to be recent (references tcl 8.4). The one from 2.2.0 would probably work. I have tried to compile it with Makefile.def.ABE without any luck. I changed the home directory, removed MUMPS and set it to sequenti...

Frank, I unfortunately am running into a bug in version 2.2.0 that was fixed in version 2.2.2. However, the binaries in your home direction on Abe are still version 2.2.0. Would it be possible to get a build of the current version on Abe? (If it is simple and I am just being stupid, you can just tel...

I found the region command, that seems to work well. I can appreciate maintaining backwards compatibility. I doubt many users double check their results are still valid when upgrading. Perhaps it can be added to a list of items to be fixed for a release not guaranteeing backwards compatibility (3.0?...

Currently different elements default to Rayleigh damping on or off. For example, truss elements by default will be excluded from Rayleigh damping while elastic beam columns will be included. It would likely reducing modeling error if all elements defaulted to the same behavior (perhaps off by defaul...

Frank,

Sounds perfect, thanks.

Dan

It would be nice if the recorders could be set to only record every "n steps".

If OpenSees does not have an internal step counter, providing an option to base it on time would be a good options as well.

Thanks,
Dan

I used the code below to read the xml output in MATLAB. It reads displacements, reactions and element forces from the xml recorders. It also regenerates node locations and element connectivity. The output should be obvious.... It requires xml_read (mathworks.com/matlabcentral/fileexchange/12907-xmli...

It would be useful if sections had the ability to report their stiffness to the element recorder. I am particularly interested in the fiber section. The motivation for this request is to identify when a plastic hinge has developed. Obviously there are several methods, but noting when the section sti...

I noticed that version 2.2.1 added support for sending recorder output over a tcp connection. This is very interesting and could alleviate having to dump output to disk. It has a lot of potential and is exciting. I am giving it a shot with a simple model (below). I am using this program to listen to...