Write a script that queries those information in Abaqus/CAE and writes into an ASCII file. Such scripts can run in noGui-mode.
Add a OS Command adapter, provide the .odb and .py, run the script and afterwards parse those data from the ASCII file.
Your starting condition is not in equilibrium and Abaqus calculates that within the first step. This will generate the stresses. Add an additional static step at the beginning if you want to see this separately.
Or you calculate the stresses yourselves with the stress-strain curve and also...
3 and 8 are the IDs of the vertices, not node numbers.
Based on what criteria shall the script get the vertices when you do not want to use the IDs? Is the user clicking on them in a plugin or do you want to find them based on coordinates? Or something else?
It's ok that way.
Quote from the documentation:
"The *FILE FORMAT option can be given as model data or as history data, but it can appear only once in the input file."
Weird approach. In a nonlinear analysis you typically cannot predict precisely how many increments are needed.
It's quite simple in my opinion:
Apply the pressure linear over time, request P as field output, run the analysis and then look at the result frame that shows the first contact of the...
Try this:
When you create a tet mesh with the option "Mesh Region", you can use the selection filter to create a boundary mesh on individual surfaces. Do that for one of the two faces. Then go to Mesh->Edit->Copy mesh pattern to copy that mesh to the second face. In that process you have to...
First check if the displacement variable U is in the field output request.
Next check the contact normals at the contact faces. They have to point toward each other. In postprocessing: Options->Common->Normals->Show Normals-> On Surfaces
My general opinion:
When you see a significant difference between averaged and non-averaged results, then it means that your mesh is not fine enough that area.
Glad you've worked it out.
You can reduce the many import lines at the beginning to those three:
from abaqus import *
from abaqusConstants import *
from caeModules import *
My examples were not intended to be the complete script. The intention was to show you how to do certain things and you apply that knowledge.
In your latest example you destroyed the code where you use the two curves and combine them to a new one.
Also the line "temp = xname.odb" should be...
Ok, your node set is one node and you extract RF2 and U2 from the field output of that node. When this process happens, these two xy data will become part of the session data of that A/CAE session. That means it is not part of the odb, but the CAE session. You could close the odb and still work...
Yes, but you have to explain more details.
You've mentioned that you want to do this process with multiple odbs. Is Abaqus/CAE closed between those operations or does it stay open and you just open&close the odbs?
Is it always that you open the odb manually and then run the script?
So for...
When you already have opened the odb manually and just want to automate the rest, then you only need this to identify the opened odb:
vps = session.viewports[session.currentViewportName]
odbName = vps.displayedObject.name
odb = session.odbs[odbName]
Create an additional field output request in Abaqus with the variable COORD and make sure you request it for location "nodes". This will allow to export the nodal coordinates in postprocessing.
To give some short answers:
>What would happen (stability/convergence/computational cost)if we use:
>1) large time steps for explicit approach
The simulation would abort pretty soon, since elements would collapse or invert itself.
>2) small time step for implicit approach
The computational...
I think the main issue is the critical mass of people that would participate in such a development.
You need people that are familiar with FEA, continuum mechanics and software development. There are probably not too many who can do this. When we assume that only 0.1% of those people are willing...
