No. See below for example. Again, this is clearly defined in the Abaqus Documentation, which you clearly did not read or did not understand.
Also, you script is very clearly just a copied dump of the .rpy file, so you could also open CAE and make the change in there and then copy the relevant...
When you create the step abaqus automatically creates a field output and a history output object. By default, these will write output for a bunch of variables at every single increment at every single node/element (whole model). You need to modify this to only select whatever variable is of...
A more serious problem is that Abaqus will fail to mesh that part with the current settings, as indicated by the orange color. In order to produce a mesh of sufficient quality you will need to do some careful and clever partitioning (which is difficult but doable with python), or use tets.
The documentation quite clearly tells you how to add execution options via the .execute command, I doubt this is new in recent version(s)....
Abaqus 2016 Analysis User's Guide - 20.2.4 - aStudy.execute():
So, this would look like: aStudy.execute(token, execOptions='cpus=X')
I have tried similar in the past and was also unsuccessful, although it was more of fiddling around for me and not a requirement so I dropped it.
You may try contacting Abaqus support who are usually quite responsive, surely they will give you a definitive answer.
Hi,
So I've successfully used a series of commands to generate a native solid hexahedral mesh (nodes and elements) by first creating nodes and then using Mesh->Between(F11) to define connectivity and generate the elements. However then when trying to automate the process with as an API, I get...
Can't comment much on your failure criteria, you will have to figure that out. Reason for negative principal stress is because your beam is bending, and you have axial (along the length of the beam) compression on the top surface.
Your mesh is not suitable for this, both element type and...
Maybe I'm missing something, but doesn't this model exhibit quarter symmetry? You could model one quarter and just use appropriate boundary conditions?
I have done it manually with python by using the surface.elements connectivity, then screening out the nodes that aren't in surface.nodes.
This won't guarantee that the final numbering is in any particular order that would correspond to a 2D element though.
