RIKS - Load Vs.

Displacement Curve
I want to plot load versus displacement curve from the static riks analysis I have performed for my
Buckling problem. Is it possible that abaqus generates such curve or I have to use arc lengths to
estimate "load applied" at each increment. please help me out

Answer :
There is no direct way to do this.

You can make a XY data of LPF ( Load Proportinality Factor) from History Output. Then create
another XY data for load by mutliplying this LPF with the load magnitude you have defined. This XY
Data will now be your Load Data.

Extract XY Data for the displacement you require. Now you have XY data for Load and
Displacement.

Goto Create->XY Data-> Operate on XY Data.

Use the combine() function to combine these two data. The resultant will be the load vs.
displacement curve.

Transformation of Results to Cylindrical Co-ordinate System
Is der any way that i can out put stress values in Cylindrical coordiantes instead of rectangular
cartesian coordiantes

Answer :
YES! You can.

1. Create a Cartesian Co-ordinate system in visualisation Mode.
2. Result->Options->Transformation->UserDefined. There you choose the Co-Ordnate System
you just now created.
Please note that only the Components of the Stress Tensor ( like S11, S22, etc.) will be transformed
to the new co-ordinate system. The Invariants like Von-Mises etc. cannot be changed as they are
scalar quantities.

Combine Restart Odb Files
I am running an analysis splitted into 10 restart analyses (ABAQUS/Standard). Now the problem is I
am not creating .fil file for the analysis. Is it possible to combine all the odb files into 1 single
ouputfile??? is it possible thru command line or do I need to go to python scripting???

Answer :
Starting from Abaqus 6.6 a execution procedure called restartjoin can be used to join different odb
files from restart analysis. The syntax is
abaqus restartjoin originalodb=odb-file-name

restartodb=odb-file-name
[copyoriginal]
[history]
[compressresult]

Prior to Abaqus 6.6, this execution procedure was not available. Butalmost the same functionality
can be availed by using example programs odbjoin.c and odbjoin.py. I use here almost the same
functionality because it seems that merging of history output is not the same between the
execution procedure and the example programs.

To use C program, follow these steps. ( For python program also the steps are similar, only that you
dont need to compile the program and should make use of abaqus python command)

Fetch the program
abq651 fetch job=odbJoin.C

Compile the program
abq651 make job=odbJoin.C

Use the compiled binary
abq651 odbJoin -writeOdb destination.odb -readOdbs restart.odb

The above command will join the restart.odb to Destination.odb

Q2.15 : How do I stop and re-start an analysis job?
Input file for the first run dynam.inp Include the line

*RESTART, WRITE, FREQ=1
in the second step of this input file and this will write the results of every
increment (FREQ = 1) to the re-start file.
The job is run from the command line as follows :

abaqus j=dynam
In this example the 2nd step is not completed.
Lets assume that in the re-started run the analysis is to be continued from
the end 10th increment of the second step.
This is done by including the following line after the *HEADING statement.

*RESTART, READ, STEP=2, INCREMENT=1, END STEP, WRITE
Failing to include the END STEP parameter would result in the re-started
run repeating the second step exactly and failing to complete in the same
way as the first run.
Note that since this is a re-start run all the model data part of the input
(F.E.Mesh data material properties etc) is omitted. The next statement after
the *RESTART statement consists of a *STEP statement.
Input file for the re-started run dynamr.inp
The job is submitted from the command line as follows :
abaqus oldjob=dynam j=dynamr
The following extract taken from dynamr.dat shows that the results are read
from the restart file up to the 10th increment and the analysis continuing
with the next step (STEP 3).
*HEADING
BISHOP AND DRUCKER -- SMALL DISPLACEMENT ANALYSIS B21

STEP 1 INCREMENT 1 HAS BEEN FOUND ON THE RESTART FILE

STEP 2 INCREMENT 1 HAS BEEN FOUND ON THE RESTART FILE

STEP 2 INCREMENT 2 HAS BEEN FOUND ON THE RESTART FILE
....

STEP 2 INCREMENT 8 HAS BEEN FOUND ON THE RESTART FILE

STEP 2 INCREMENT 9 HAS BEEN FOUND ON THE RESTART FILE

STEP 2 INCREMENT 10 HAS BEEN FOUND ON THE RESTART FILE
The analysis continuing wth the next step (STEP 3). Following is the extract
from the status file : dynamr.sta
Abaqus/Standard 6.9-1 DATE 01-Sep-2009 TIME 15:31:01
SUMMARY OF JOB INFORMATION:
MONITOR NODE: 11 DOF: 2
STEP INC ATT SEVERE EQUIL TOTAL TOTAL STEP INC OF
DOF IF
DISCON ITERS ITERS TIME/ TIME/LPF TIME/LPF
MONITOR RIKS
ITERS FREQ
3 1 1 0 1 1 1.11 0.0100 0.01000
19.3
3 2 1 0 1 1 1.12 0.0200 0.01000
10.1
3 3 1 0 1 1 1.13 0.0300 0.01000
0.116
3 4 1 0 1 1 1.14 0.0400 0.01000 -
10.7
3 5 1 0 1 1 1.15 0.0500 0.01000 -
20.5
3 6 1 0 1 1 1.16 0.0600 0.01000 -
26.7
3 7 1 0 1 1 1.17 0.0700 0.01000 -
29.3
.....
3 97 1 0 1 1 2.07 0.970 0.01000 -
11.6
3 98 1 0 1 1 2.08 0.980 0.01000 -
1.12
3 99 1 0 1 1 2.09 0.990 0.01000
9.46
3 100 1 0 1 1 2.10 1.00 0.01000
18.8

THE ANALYSIS HAS COMPLETED SUCCESSFULLY
If the ODB files from the first run and the re-started run needs to be
combined into a single ODB file for post-processing purposes, this is
achieved by typing the following line from the command line :
Execution procedure for joining output database (.odb) files from restarted
analyses
abaqus restartjoin originalodb=odb-file-name restartodb=odb-file-name
[copyoriginal].