Coupled RC Core Wall with MVLEM-3D

[kolozvari]

Hello, thank you. I did change the recorder option as you said but I am getting MPCO error: no nodes in the recorder (something like that).

Can you please email me back the working model to avoid any additional back and forth?

Thank yoi very much!

[kolozvari]

Hello, I have just re-ran the model with less cores and the settings you suggested, and it seems that in some cases deleting databases is not necessary. However, results still come out blank for the coupling beams. If you are able to produce the results for the coupling beams using the model and the API code I emailed you, please email me back the model and the API code with detailed instructions on how to do it. I would really appreciate if you can send me these soon.

Thank you very much.

[STKO Team]

we sent you the modified model by e-mail

[kolozvari]

Thank you very much. I have re-run your model, deleted the empty coupling beam databases, reloaded all the databases, and I still get empty results. I have noticed that there is a message (window with listed green and red items) when I open your version of the model that there have been some updates and that some items are changed, updated, etc. What is this related to? I am pretty sure I have the latest version of STKO since it doesn't ask me to update the software when I start it. Did the solver get updated, I have OpenSees 3.4.0, parallel solver. Would the update in the solver cause this inconsistency between mine and your results processing? If so, where do I find the latest version of the solver?

Please let me know. Thank you.

[STKO Team]

We made an improvement in including auto-generated elements in selection sets in the MPCO.CDATA files that will be included in the next STKO version.


unzip this

tcl_input.zip

(4.67 KiB) Downloaded 6 times

in C:\Program Files\STKO\external_solvers\opensees\utils and replace the existing one.

Then you don't need to re-run the OpenSees simulation. You just need to re-rune the WriteInputFile command in STKO to regenerate the MPCO.CDATA files.

let us know

[kolozvari]

Hello,

I have a few questions about post-processing of results, and I was hoping you could help me.
1) For some reason, when I setup recorders to record results of time history analyses using Recorder Frequency of dt = 0.02 seconds, only the first data point is recorded at 0.02 sec, while the time step of all other data points is 0.04 seconds, which is double of what is prescribed. Are you aware of this issue? How can I fix it?
2) To the best of my knowledge, section cuts for recording forces in various structural elements are not available in OpenSees. Is there any option to create section cuts in STKO? I need to record forces in RC core walls (MVLEM-3D) and basement walls (ASDshellQ4), so I can separate the story shear forces that go into the RC core and basement walls. Please advise how can I do this.
3) How can I visualize strain and stress results from individual soil elements modeled with stdBrick and UCSD soil material models? The results are recorded in the recorder, and I can visualize them. But when I try to plot strain or stress from a soil element using "Chart Data" option. When I select an element, it doesnt appear in the list of the processing menu (see screenshot below).

Please let me know. Thank you.

[kesavapraba]

Hi,
[1] Could you please provide me with a simplified model where this specific issue has occurred? We will thoroughly examine it to better understand the problem.

[2] You are absolutely correct. We are currently in the process of integrating the section cut feature into the STKO postprocessor for our upcoming version. In the meantime, you can utilize the Python API to obtain the section forces.

[3] Have you chosen the Gauss point for extracting the stress-strain response? I recommend trying the Gauss Point plot as stress-strain data can be extracted directly from the Gauss points.

[kolozvari]

Thank you for your response.

1. I have changed my models quite a bit since I experienced this originally. I asked this question a while ago, but didn't get any response before. You should have my models send in early October 10 year. Please let me know if you cannot find it and I will send it to you again.

2. This would be very helpful. Do you have any rough time estimate when will this be available? Can you please elaborate on

In the meantime, you can utilize the Python API to obtain the section forces.

? Which API? How to use it?

3. Yes, I used "On element Gauss points" in the issue reported in the previous message. I am not sure how to obtain these values. Please advise.

Thank you.

[kesavapraba]

Hi, Thank you. Please see if the following answers help you.

[1] Actually, this issue of doubling in MPCO recorder frequency (from 0.02 to 0.04 sec) emerge from how MPCO recorder handles the rounding off of the numerical value. Say for example, if dt is 0.0200000001 instead of 0.02, the recorder automatically jumps to 0.04 time step. This issue will be fixed in the next version of STKO. Nonetheless, you can fix this issue by directly modifying C++ implementation in MPCO recorder.

[2] Our team is working on this feature. It might take another couple of months. However, you can use PyMpc package as found in the link below to develop custom section cut feature. https://asdeasoft.net/stko-wiki/

[3] No, you are selecting it on the surface plot. Instead you should go to the Gauss Plot -> Select the Gauss point -> Chart Data -> On Element Gauss Points -> X-Data, Use a result, Strain -> Y-Data, Stress

[kolozvari]

Thank yo for quick response.

1) I understand the issue. I will wait for the next version of STKO to come out.

2) I will wait for the next version of STKO to come out.

3) Thanks for clarifying, I think I made it work.

Regards,