How can I find the 3D Embedded Beam Slipping (sliding) between the pile and the soil?

Dear Kostis,

Indeed, you are correct and in this case, you can use Python scripting to compute this relative movement of the embedded beam. For that, you could use the coordinates of all the nodes of the embedded beam element and find the equivalent coordinates from the soil side. In that case, the getsingleresult or the getresults commands can assist.

Currently, there is no direct option to view this result in PLAXIS Output program.

Thanks again Stefane, it sounds a bit complicated, because the embedded-beam nodes (which I believe are created at the intersection with the solid soil elements), do not coincide with the solid-element nodes. It would be appreciated if this was picked up in a future version of Plaxis.

I am not familiar with Python. What would be the best place for someone to start/ get exposed? 

Finally, similar question, what would be the best way to visualize what parts of the embedded beam have reached the interface side-shear capacity? It is kind of straight forward when the side-shear capacity is constant with depth, but gets tricky if it varies, and even more tricky if it is estimated by the program.

Thanks again Stefane, it sounds a bit complicated, because the embedded-beam nodes (which I believe are created at the intersection with the solid soil elements), do not coincide with the solid-element nodes. It would be appreciated if this was picked up in a future version of Plaxis.

I am not familiar with Python. What would be the best place for someone to start/ get exposed? 

Finally, similar question, what would be the best way to visualize what parts of the embedded beam have reached the interface side-shear capacity? It is kind of straight forward when the side-shear capacity is constant with depth, but gets tricky if it varies, and even more tricky if it is estimated by the program.

Dear Kosti,

The nodes are different but the coordinates they correspond to are the same. Therefore, for example, a node at (x, y, z) = (7, 5, -2) for an embedded beam will also give a soil result at the same coordinates. 

As an example, which can be turned into a for-loop for all embedded beams:

embbeam = g_o.EmbeddedBeam_1_1  # I select one of the embedded beams in the model

x = g_o.getresults(embbeam, g_o.ResultTypes.EmbeddedBeam.X, "node")
y = g_o.getresults(embbeam, g_o.ResultTypes.EmbeddedBeam.Y, "node")
z = g_o.getresults(embbeam, g_o.ResultTypes.EmbeddedBeam.Z, "node")
utot = g_o.getresults(embbeam, g_o.ResultTypes.EmbeddedBeam.Utot, "node")
# print(utot)

coords = [coord for coord in zip(x, y, z)]
# print(coords)

utot_embbeam = [g_o.getsingleresult(g_o.Phase_5, g_o.ResultTypes.Soil.Utot, coord) for coord in coords]
# print(utot_embbeam)

for i, j in zip(utot, utot_embbeam):
    print(i-j)  # this will print the difference per node

To start with I would say check all the different examples we have in our Wiki page:
API / Python scripting - PLAXIS - PLAXIS | SOILVISION Wiki - PLAXIS | SOILVISION - Bentley Communities
Identify Python commands from Plaxis command line - PLAXIS | SOILVISION Wiki - PLAXIS | SOILVISION - Bentley Communities

and for sure our Scripting reference that is provided with CONNECT Edition V20:
Scripting reference and how to use it - PLAXIS | SOILVISION Wiki - PLAXIS | SOILVISION - Bentley Communities

Concerning the skin resistance, the only available result is the Tskin, which shows the mobilized resistance. I will pass to the developers if there is any way to visualise when the maximum capacity is reached, according to what Input provides.

Thank you very much!