TifoTafi
Bioengineer
- Jul 22, 2014
- 2
Hi Abaqus experts out there,
I am trying to create custom Field Output in Abaqus, where I relate two types of stress invariants to each other, for example MISES and PRESSURE, e.g.:
[tt]s15f1_MISESMAX - 0.35 * s15f1_PRESSONLY[/tt] (--> s15f1 = step 15 frame 1)
I know how to do this inside the Visualization module using the Create Field Output dialog box (Tools > Create Field Output > From Fields): this creates a Field Output object, but with the following limitations:
- Only stored as temporary step (by default: "Session Step") and not permanently saved to the ODB.
- Only applicable for 1 step and 1 frame (by default: last step and last frame) and not for more/all steps/frames.
I would like to overcome the above limitations, and make this custom Field Output 1) permanently available in the ODB, and 2) have this available for all analysis steps. However, at this point I do not know how to do this or where to even start (as I am a scripting newbie), and this is where I need your help...
My questions:
1) Should the focus be to manipulate the job input file (*.INP) or output database (*.ODB) to create this additional custom Field Output in the ODB?
2) Is it required to create a macro which records a sequence of Abaqus Scripting Interface commands or write a custom Python script for this? Or is there a more simple straightforward solution (like e.g. adding lines of Abaqus keyword commands to the job input file)?
Any help or suggestions are highly appreciated!
Kind regards,
David
I am trying to create custom Field Output in Abaqus, where I relate two types of stress invariants to each other, for example MISES and PRESSURE, e.g.:
[tt]s15f1_MISESMAX - 0.35 * s15f1_PRESSONLY[/tt] (--> s15f1 = step 15 frame 1)
I know how to do this inside the Visualization module using the Create Field Output dialog box (Tools > Create Field Output > From Fields): this creates a Field Output object, but with the following limitations:
- Only stored as temporary step (by default: "Session Step") and not permanently saved to the ODB.
- Only applicable for 1 step and 1 frame (by default: last step and last frame) and not for more/all steps/frames.
I would like to overcome the above limitations, and make this custom Field Output 1) permanently available in the ODB, and 2) have this available for all analysis steps. However, at this point I do not know how to do this or where to even start (as I am a scripting newbie), and this is where I need your help...
My questions:
1) Should the focus be to manipulate the job input file (*.INP) or output database (*.ODB) to create this additional custom Field Output in the ODB?
2) Is it required to create a macro which records a sequence of Abaqus Scripting Interface commands or write a custom Python script for this? Or is there a more simple straightforward solution (like e.g. adding lines of Abaqus keyword commands to the job input file)?
Any help or suggestions are highly appreciated!
Kind regards,
David