asdeasoft.net

Dear Ted, I am able to visualize the result section.fiber.damage . Are you visualizing this result? Are you using the Fiber Color Map? Keep in mind that, with a layered shell, material results can be visualized on fibers, because of the nature of the Layered Shell (Fiber Section for shells) let us k...

You're welcome

Dear Zhang Bin, we identified the issue, and it belongs to the PressureDependMultiYield that does not follow the standard OpenSees rules for writing the results. This is not a problem typically, but when you mix this material with others (in your case the ElasticIsotropic) in a partitioned mesh, it ...

Typically you should not ignore that warning, because it tells you that you tried to do updateMaterialStage on the material N , but material N could not handle the updateMaterialStage or material N is not available in the domain. But in your case you can ignore it, because you are doing a partitione...

this is because the localForce output is not a result on gauss points (it is on the element's end-nodes). If you need beam forces along the element, in each gauss point, you need the section.force output. But to do so, you first need to use either a forceBeamColumn or a dispBeamColumn, i.e. those el...

This is strange... can you share your model here?

What material tag are you using with the "updateMaterialStage"?

It should be the material tag of the initial-state-wrapper, and not the tag of the source material.

Can you share your model if the above suggestion does not work?

You are welcome!

You are welcome.

You are welcome!