Is using a .mechdb best practice for loading simulation already setup in mechanical GUI? #1250
-
|
I'm wondering what the best way is to use pymechanical to parametrize and run a simulation that was set up in the mechanical GUI. I want to set up material data and geometry in workbench, and then create connections, mesh, and define most boundary conditions in mechanical GUI. I then want to use pymechanical to parametrize/automate, and also do some postprocessing functions. Its a complex geometry so as far as I know, creating geometry/connections/mesh in code would be difficult. It's a work in progress but I believe I've accomplished my goal by saving the project as a .mechdb and pointing to that file in my script. Is that best practice? Or are there better ways to do this. From limited research it seems I can't point to simulation that I have open and say "use that". license is mechanical 2024 r1 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Yes, since making all connections and handling complex geometry or meshing through code can be difficult, it's better to use the |
Beta Was this translation helpful? Give feedback.
Yes, since making all connections and handling complex geometry or meshing through code can be difficult, it's better to use the
.mechdbfile. This approach aligns well with the purpose of PyMechanical, which is to help automate tasks such as parameterization, running simulations, and postprocessing.