Search results for query: *

I think CDISP has 3 components (for 3D), 1 = COPEN , 2= CSLIP1, 3=CSLIP2. (Array indexing starts from 1 in FORTRAN).

Penalty method for enforcing contact allows for penetrations. You need to use the direct enforcement if want to see no penetration.

I believe Abaqus recently launched their own CFD code. http://www.simulia.com/products/abaqus_cfd.html http://www.simulia.com/products/abaqus_multiphysics.html

You can use Abaqus/CAE -> Visualization to create a new node field from U(step2)-U(step1) and plot it as any other quantity.

Are you running the script inside /CAE ? Abaqus Python scripts are not supposed to be run with the public Python distribution. Abaqus comes with its own Python compiler version which includes additional modules.

Look in the .dat file.

I might be wrong but I think your confusion relates to the following: Abaqus consists of 3 main -standalone- programs: Abaqus/CAE - pre/post processor (for creating models - more like a CAD software with meshing capabilities and for visualizing results.) Abaqus/Standard - implicit analysis code...

The User Subroutines Reference Manual has a section on printing messages to the message or status file. for example: write(6,*) 'test' will print 'test' in the .dat file write(7,*) 'test' will print 'test' in the .msg file etc.

I suspect the issue mentioned in the paragraph you cited is the default normal averaging at nodes. I think Abaqus tries to (automatically) establish the normal at nodes by using the orientation of beam elements specified by the user and in certain cases it does some averaging....

I suspect you can use *DSLOAD with a an ORIENTATION to define the components of a traction vector load. Some points: - pressure acts always normal to the surface - if you have a traction acting at an angle it can be decomposed in a normal component and a shear component.

Assuming the cylindrical roll is a rigid body, then it has 6 DOFS 3 translations and 3 rotations at a reference node. You can try to use the DISP user subroutine to prescribe these DOFS as you like.

You cannot mesh analytical rigid surfaces, only discrete rigid surfaces can be meshed. For each rigid surface you need to define a single reference point which can be used for applying loads/displacements. Typically the rigid parts interacts with other parts via contact interactions.

I think it might be possible using the old slide line or tube to tube contact elements. I do not remember the details. You should search the Abaqus documentation for *SLIDE LINE, slide line contact elements, tube-to-tube, *INTERFACE etc.

As an workaround, you can import the .inp file in /CAE. It will create an orphan mesh part defined in terms of elements and nodes.

I suspect you need to use *INITIAL CONDITIONS, TYPE=RATIO (to provide initial void ratio for a coupled pore-fluid diffusion/stress analysis). (this is similar to providing an initial temperature field for a heat transfer problem.)

In my opinion, continuum FE formulations are not very useful at nano-scale. However, if you are interested in modeling inter-atomic interactions using user-defined "structural-like" elements you might be interested in the user subroutine UEL. I think currently researchers are interested in...

There is some information in the Theory Manual. It is based on the Lagrange multipliers (LM) used to enforce the contact constraints. According to Analysis User's manual, Abaqus may do some further processing of LM (perhaps some averaging of the values provided by individual constraints) before...

Some recommendations: 1) try to replace your UMAT with a simple built-in material and see if the abort still occurs, if yes contact Abaqus support again. 2)use the model with a simple UMAT, from documentation 3)use your UMAT with a small model and put printout statements to .msg file (unit 7)...

1) You can use UMAT and store them in state variables (STATEV). State variables are available for plotting as SDV. Perhaps you might not even need UMAT but only SDVINI which is called at the beginning of the analysis to initialize the state variables. 2)If the materials properties are only...

Does this happen with a particular model or with any model ? Do you get any error message in .log / .msg about abort? Running jobs with 3 cores is kind of unusual. Does is run with 2 cores? Does the HD undergo automatic back-up?