-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On extracting p-y curves #35
Comments
Just to ask as well, are soil layering corrections, such as Georgiadis (1985) or Allen (1983) employed for computation and use in openpile? |
Hi @emabcede30, this is not employed and not yet implemented in the library. I'd welcome a PR on this. |
Your approach to extract the soil springs from the model is correct, however in both cases you'll get a spring in kN/m length of pile for 'p' and meters for 'y'. As of today, the difference with respect to the 'kind' argument is minimal and can be neglected. I will deprecate it cause it was something else I had in mind than what is currently implemented. The idea will be in the future to have different units when extracting the springs 'p' values, either kN/m length of pile (as it is currently the case, which would not be affected by the mesh discretisation), or kN (the latter being the raw springs used in the model) |
How does one extract the p-y curves used in the model?
Is it correct to just call the py curves from the utils module, say
from openpile.utils.py_curves import api_sand
y, p = api_sand(...)
But I want to get the py curves that the winkler() function used. like model.get_py_springs()? What is the difference when setting kind=element or node differ in formulating the p-y curves? I would imagine model coarseness/distance between the node mesh shouldn't affect the py curves?
I'll share some test cases
The text was updated successfully, but these errors were encountered: