Hi,
Just wondering whether you can share the following:
- the rationale behind changing some of the API/Plaxis keywords between versions*.
- a list of the changes from V21 to V22, so that it is more apparent what functionality has changed?
*Changing the keywords, e.g. in this instance soilmat naming was done via "MaterialName" in V21 - but is now "Identification" in V22.
The reason I ask, is for interoperability between Plaxis versions. As the logic for creating/changing properties for a soilmat (and presumably other features) needs to vary based on a Plaxis version.
Dear Matthew,
We have created this dedicated page for the material changes in V22: Material Property changes for Python scripting
The changes in V22 were part of the major overhaul of the data structure of the material database. This meant changes in the way properties are shown in GUI and also how they are considered in the scripting layer.
We are aware that this change would cause Python scripts to fail, however, the benefits of this change will help us at PLAXIS deliver better code and services in the future.
Sorry that this has caused some confusion but we are doing our best to assist everyone who has questions or needs help. Feel free to submit a Service Request if you need help on a specific topic: https://apps.bentley.com/srmanager/ProductSupport
Answer Verified By: Matthew Johnson
Stefanos,
Many thanks for your quick reply - and I suppose my bad for not looking further! That post seems very handy. Cheers!
No worries, that is why we are here!
Let me know if you have any problems!
Hi Stefanos. Do you think was the changes in Python really necessary? I understand you wanted to keep the Python structure same with the Plaxis structure, but how often should we expect these? Because, now I have to go through a lot of scripts that I prepared. The reasoning behind spending the time to automate the task is re-using the code. Now, we lost it with V22. That's why I am not deleting the V21 still.
Hello Berk,
Happy New Year!
Yes, the changes were unavoidable as we had a major overhaul of the data structure of the material database. This not only made it easier to define the materials but actually was necessary if we wanted to improve our code and allow for easy changes when adding (or fixing) material code in the backend.
I fully understand that nobody likes any changes like these (we had to change many of our scripts, too), but it was the only way to move forward with our main PLAXIS code and it comes with nice improvements on the user side, too.
I hope that you have all your material definitions based on a list (more Pythonic way), which then leaves only a search & replace task for the changes in names as mentioned on the page: Material Property changes for Python scripting