The OpenSees Community

I want to develop in C++, as we want to integrate our software with the opensees FEM capabilities. The TCL interpreter is useless integrating C/C++ softwares. Now, I have some questions for translating your code into C++. What does this mean? set lambda1 [eigen 1] Is this true? pattern UniformExcita...

Here's a little excerpt of the modified code: theMaterial = new ElasticIsotropicMaterial(0, 3000, 0.3, 4); Current Domain Information Current Time: 4 tCommitted Time: 4 NODE DATA: NumNodes: 300 Node: 0 Coordinates : 14 0 0 commitDisps: 0 0 0 Velocities : 0 0 0 commitAccels: 0 0 0 unbalanced Load: 0 ...

I thought it was done automagically by the bBarBrick, defining the geometry and the material property: theMaterial = new ElasticIsotropicMaterial(0, 3000, 0.3); theElement = new BbarBrick(tot, en[0], en[1], en[2], en[3], en[4], en[5], en[6], en[7], *theMaterial); So, if I'm wrong, and the probabilit...

No, the simulation isn't working. The displacement is always zero, but it's not realistic. An example: Node: 188 Coordinates : 3.45919 -10.3116 9 commitDisps: 0 0 0 Velocities : 0 0 0 commitAccels: 0 0 0 unbalanced Load: 0 0 0 ID : 483 484 485 Node: 189 Coordinates : 8.95919 -6.31564 9 commitDisps: ...

I decided to use bbarbricks to analyze my model. I can do a static analysis but I'm quite uncomfortable with the transient one. Can you help me? This is what I do: theSeries = new TrigSeries (0, 200, 1, 0); GroundMotion *theMotion = new GroundMotion(0, 0, theSeries); theLoadPattern = new UniformExci...

So I have to write everything on my own... starting from newElement probably...

Ok, thanks!

Just miswrote... n-cells are n-dimensional cells, but we're in 3D.

Just substitute n-cell with:

polyhedral cells with N faces

So: not cubical cells, not simplicial cells...

Hi. I'm new to opensees and I have a simple question. We have a mesh generator based on bsp trees, so all the cells in the mesh are polyhedral. Is it possible to define a mesh using custom cells? The problem seems to be with the element associated with the MeshRegion, since it doesn't seem to handle...