For example I went the Abaqus/python way... But only using python as a iterative pre and post, for .inp generation - letting Abaqus solve its thing. If I understand correctly you are trying to develope a new constitutive relationship. If the inbuild abaqus models are not sufficient than UMAT is...
Try searching on github... Some crazy UMAT things lurk there.. But anyway diving into UMAT and making significant changes greatly increases your change to become unstable.
I am experiencing a strange error from the when I submit the job. "Error in job Job-1: in keyword *NODE, file "Job-1.inp", line 9: Invalid nodal coordinate values were specified for the following nodes: 1 2 3 ..." and so on. I am running the Abaqus 2021 version on Arch/Linux and the Job-1.inp...
I have finaly came up with a solution. The problem was in my argument to define initial stress to a defined set of elements Set-all. Abaqus seems to do that automatically (if meshes are the same), therefore leaving the argument blank successfully applies the initial stress imported from a...
I am trying to define a stress field as a initial condition. My procedure
Analysis 1 - Job-1:
Step-1: load "elasto-plastic deformation"
Step-2: unload "residual stress visible"
Created a set of all elements:
*Elset, elset=Set-all, instance=Part-1-1, generate
1, 100, 1
Analysis 2 -...
I would like to export Cauchy stresses and Element IDs from a generic .odb
I have written this entry level Python script that writes stresses to a .txt file:
----------------------CODE START------------------------------------
from odbAccess import *
# open the result contatinig output...
I believe that what you are trying to achieve can be done by first sectioning the part and than appliying mesh controls in the meshing module of abaqus. I attached some screen shots.
http://files.engineering.com/getfile.aspx?folder=166e333b-0438-4ce4-acfd-f02000328f28&file=1.PNG...
I am still quite new to Abaqus and FEM in general so take my advice with a pinch of salt.
If you are simulating a sequence of applied loads try a static/general step for each applied load. In that way you include the loading history of each applied torque.