Simplify the export of ABAQUS part files to one of several CAD formats, with the option to scale the output to units of your choice and store to a user selected folder. I have been distracted from blog posts by other things, I would love to say life, but other coding things which I hope to announce very soon. So today a simple one – a very brief dash through using the incredibly easy Really Simple GUI addon for ABAQUS to create a handy little plugin that makes exporting your

ABAQUS CAE lets you permanently store user data within the model and output files, the trick is how to access it again… Introduction The goal is to obtain information or setting values from the user and store them, permanently, with the model data such that they can be retrieved and reused, loaded back into a plugin for a future user to check or edit. Getting the data into the model or odb files is simple. Extracting it from a saved file and repopulating a plugin dialog needs

Arranging and renaming your ABAQUS plugins without editing the code. Accessing your plugins collection is made easy using the plugins menu. When you have lots of plugins then it becomes a chore to arrange your menus to suit yourself so that they appear in a logical way that makes them easy to find, with a clear name indicating what they do and when to use them. I have found the following tips have made my user experience more efficient. Limit Visibility When you write your pl

Another brief blog post this week as I have been busy on both a coding course and a programming exercise, which, when I get it working, I shall share. Going back to my roots with a simple fluid dynamics code. So for this week I shall simply share the templates that I have made and use, with reminders in place, for making different kinds of ABAQUS scripts. Templates are great. They save you time hammering out the boilerplate and forgetting that basic detail that you are so use

Sometimes user input is essential for your script... the next best to no GUI is a simple GUI. I stated in a previous post that user interfaces for your ABAQUS scripts should be avoided wherever possible because they complicate the code and make it more time consuming to change. If you really must have a GUI then the simplest one possible should be used. The most basic is a kernel dialog where the user enters data into a text box, without any kind of feedback. This was used in

Article about a script demonstrating the efficiency gains that can be achieved by fluency in scripting and automation for ABAQUS.

Article demonstrating how to create interactive graphics on an ABAQUS dialog box - working example with a stick figure walking off the end of the world.