Coupled RC Core Wall with MVLEM-3D

[STKO Team]

It's because your selection-sets only include one-half of the beams, so the algorithm I used will not work because I assume you have both sides of the beam.

Can you show me a screenshot of the selection sets in the pre-processor? With the current STKO version this is working fine. If you have an old version, try to upgrade it. Then you need to regenerate the mpco.cdata by writing the tcl commands (you don't need to re-run the analysis)

[kolozvari]

Hello, I dont think it is possible to select only half of the beam because the beam is modeled as only one element (BeamWithShearHinge). I attached the model for your reference. Maybe it is something in the way I defined MPCO recorder with regions. I would appreciate if you can take a look.

Thank you.

[STKO Team]

I found the issue. It's a bug we have writing the Selection Sets to the MPCO.CDATA file when the BeamWithShearHinge Edge is discretized in an odd number of elements (1 in your case).
In this situation, we (behind the scene) split the element in half, and we forget to add the new part of the split element to the selection set.

We will fix it soon. In the meantime you can:

• select all edges with a BeamWithShearHinge element (just right-click on each BeamWithShearHinge Element Property and select)
• Assign an edge seed by division=2
• re-mesh
• re-run

[kolozvari]

Thank you for your quick response. OK, I am glad you found the issue. Please let me know when this is fixed.

Would dividing BeamWithShearHinges create multiple shear springs? If so, it would be unclear which spring yields. Also, obtaining plastic rotation would be difficult from multiple springs. Please let me know if my understanding is correct.

I would really prefer to use only one shear hinge, as I am trying to validate results from this model against other software that uses only one shear hinge, and this is currently holding me back. Hopefully, you can fix the issue soon.

Thank you.

[kolozvari]

Can you please give me a time estimate on fixing this issue so I can plan my work?

Thank you.

[STKO Team]

Can you please give me a time estimate on fixing this issue so I can plan my work?

The bug will be fixed this week. I will post an updated version of the associated python file here, but it will be available to everyone with the next STKO version.

Would dividing BeamWithShearHinges create multiple shear springs? If so, it would be unclear which spring yields. Also, obtaining plastic rotation would be difficult from multiple springs. Please let me know if my understanding is correct.

Sorry for the misunderstanding. You DON'T have to divide the Edge. The CAD model remains unchanged. You just need to mesh the coupling beams with an even number of elements. For example 2. In this way, STKO will always create 1 single shear spring in the Middle of the Edge, but since there is already a mesh node in the middle (due to the even number of subdivisions), it will not create an extra element.

It's super easy, just follow these steps:

• select all edges with a BeamWithShearHinge element (just right-click on each BeamWithShearHinge Element Property and select)
• Assign an edge seed by division=2
• re-mesh
• re-run

[kolozvari]

Thank you for your response. I did what you said and I received an error message below.

Please advise.

Thank you.

[STKO Team]

I'm afraid there is a collapsed edge in your model. Otherwise, U_span is always > 0. Unless the 2 nodes of an edge coincide. Could you share your model? or send it here: info@asdeasoft.net

[kolozvari]

Not exactly sure what you mean by that. I emailed you the model. Thank you

[STKO Team]

Here we are! You found a bug that only happens when the BeamWithShearHinge is used on an Edge which is a boundary of a face (like in your example).
Instead, when the edge is free (like in a pure frame model) this bug did not appear.

Now, following the previous steps

select all edges with a BeamWithShearHinge element (just right-click on each BeamWithShearHinge Element Property and select)
Assign an edge seed by division=2
re-mesh
re-run

it should work, and you should be able to extract results from selection sets


Extract this file

BeamWithShearHinge.zip

(4.29 KiB) Downloaded 3 times

in C:\Program Files\STKO\external_solvers\opensees\element_properties\special_purpose.
This fix will be available to everyone in the next STKO release.

Let us know