Architectural changes in Abaqus user profile from HyperMesh 2022
Altair EmployeeAltair commitments
As a starter, some of the modifications changed the way we write the inp file.
Our choices for the format of the inp file are driven by development decisions, considering not only Abaqus, but also the consistency and the ease of conversion with other solvers supported in HyperMesh.
As Abaqus supports multiple ways for modeling some entities, starting with sets, our internal Q&A process focus on ensuring that the modifications we brought to Abaqus:
- still produces a valid inp file (the inp file runs fine with Abaqus)
- and that the results obtained with the new inp file are the same as for the former one, as soon as both inp are run with the same version of Abaqus.
That said, we do not commit to preserve the ascii structure/organization of the inp file.
Please report to our support team asap if one (or multiple) of your models is not running anymore with Abaqus or returns different results.
In case you authored some automation on Abaqus pre and/or post-processing, please contact us so that we can provide you guidance about how to adjust your automations to consider the new model structure.
What changed?
Please review the video below for having a first glance at the main changes introduced between 2019 and 2022:
https://www.youtube.com/watch?v=_F5owJKw5r4
About the main changes:
Some of the changes shown in the video require some in-depth explanations. The links below explain what changed for some of the entities detailed in the introduction video.
Comments
-
I don't see any benefits out of these changes for the Abaqus users, but on the other side I see added difficulty in setting up the deck, modifying and updating the deck for new cases.
Let me know if any other Abaqus users feel the same.
0
