Too many attempts made for this increment
浏览:156689 回答:4
Job被迫中止,出现这句话:Too many attempts made for this increment,是怎么回事?各位大侠,我是新手,大家多多指教。
---------------------------------------------------------------------------------------------------------------------------------------------
技术邻推荐:
1
Abaqus 6.10-1 Date 10-Jan-2013 Time 11:56:01
For use by TEAM TBE under license from Dassault Systemes or its subsidiary.
The Abaqus Software is a product of:
Dassault Systemes Simulia Corp.
Rising Sun Mills
166 Valley Street
Providence, RI 02909-2499, USA
The Abaqus Software is available only under license
from Dassault Systemes or its subsidiary and may be
used or reproduced only in accordance with the terms
of such license.
On machine dell-PC
you are authorized to run
Abaqus/Standard until 11-Nov-2017
Your site id is: 20111111
For assistance or any other information you may
obtain contact information for your local office
from the world wide web at:
http://www.simulia.com/about/locations.html
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
* ***************** *
* * N O T I C E * *
* ***************** *
* *
* *
* Abaqus 6.10-1 *
* *
* BUILD ID: 2010_04_29-14.17.36 102575 *
* *
* *
* Please make sure you are using release 6.10manuals *
* plus the notes accompanying this release. *
* *
* *
* *
* *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
PROCESSING PART, INSTANCE, AND ASSEMBLY INFORMATION
*******************************************************
END PROCESSING PART, INSTANCE, AND ASSEMBLY INFORMATION
***********************************************************
OPTIONS BEING PROCESSED
***************************
*Heading
*Node
*Element, type=CPS4R
*Nset, nset=ASSEMBLY_PART-1-1__PICKEDSET2
*Elset, elset=ASSEMBLY_PART-1-1__PICKEDSET2
*Node
*Nset, nset=ASSEMBLY_PART-2-1_PART-2-1-REFPT_
*Nset, nset=ASSEMBLY__PICKEDSET10
*Nset, nset=ASSEMBLY__PICKEDSET8
*Nset, nset=ASSEMBLY__PICKEDSET9
*Elset, elset=ASSEMBLY__PICKEDSET9
*Elset, elset=ASSEMBLY__SURF-2_S1
*Elset, elset=ASSEMBLY__SURF-2_S3
*Elset, elset=ASSEMBLY__SURF-2_S4
*rigidbody, refnode=ASSEMBLY_PART-2-1_PART-2-1-REFPT_, analyticalsurface=ASSEMBLY_PART-2-1_SURF-1
*contactpair, interaction=INTPROP-1, type=SURFACETOSURFACE
*rigidbody, refnode=ASSEMBLY_PART-2-1_PART-2-1-REFPT_, analyticalsurface=ASSEMBLY_PART-2-1_SURF-1
*rigidbody, refnode=ASSEMBLY_PART-2-1_PART-2-1-REFPT_, analyticalsurface=ASSEMBLY_PART-2-1_SURF-1
*rigidbody, refnode=ASSEMBLY_PART-2-1_PART-2-1-REFPT_, analyticalsurface=ASSEMBLY_PART-2-1_SURF-1
*contactpair, interaction=INTPROP-1, type=SURFACETOSURFACE
*surface, type=SEGMENTS, name=ASSEMBLY_PART-2-1_SURF-1
*surface, type=ELEMENT, name=ASSEMBLY_SURF-2
*surface, type=SEGMENTS, name=ASSEMBLY_PART-2-1_SURF-1
*surface, type=ELEMENT, name=ASSEMBLY_SURF-2
*contactpair, interaction=INTPROP-1, type=SURFACETOSURFACE
*surfaceinteraction, name=INTPROP-1
*surfacebehavior, pressure-overclosure=HARD
*contactpair, interaction=INTPROP-1, type=SURFACETOSURFACE
*rigidbody, refnode=ASSEMBLY_PART-2-1_PART-2-1-REFPT_, analyticalsurface=ASSEMBLY_PART-2-1_SURF-1
*material, name=MATERIAL-STEEL
*density
*elastic
*surfaceinteraction, name=INTPROP-1
*friction
*surfacebehavior, pressure-overclosure=HARD
*surfaceinteraction, name=INTPROP-1
*solidsection, elset=ASSEMBLY_PART-1-1__PICKEDSET2, material=MATERIAL-STEEL
*rigidbody, refnode=ASSEMBLY_PART-2-1_PART-2-1-REFPT_, analyticalsurface=ASSEMBLY_PART-2-1_SURF-1
*rigidbody, refnode=ASSEMBLY_PART-2-1_PART-2-1-REFPT_, analyticalsurface=ASSEMBLY_PART-2-1_SURF-1
*boundary
*boundary
*contactpair, interaction=INTPROP-1, type=SURFACETOSURFACE
***WARNING: PATH BASED TRACKING IS DEFINED IN CONTACT PAIR
(ASSEMBLY_SURF-2,ASSEMBLY_PART-2-1_SURF-1). PATH BASED TRACKING
CANNOT BE USED WITH ANALYTICAL RIGID MASTER SURFACES, THE STATE
BASED TRACKING ALGORITHM WILL BE USED INSTEAD.
*solidsection, elset=ASSEMBLY_PART-1-1__PICKEDSET2, material=MATERIAL-STEEL
*surfaceinteraction, name=INTPROP-1
*contactpair, interaction=INTPROP-1, type=SURFACETOSURFACE
*rigidbody, refnode=ASSEMBLY_PART-2-1_PART-2-1-REFPT_, analyticalsurface=ASSEMBLY_PART-2-1_SURF-1
*surface, type=SEGMENTS, name=ASSEMBLY_PART-2-1_SURF-1
*surface, type=ELEMENT, name=ASSEMBLY_SURF-2
*output, field, variable=PRESELECT
*output, history
*output, field, variable=PRESELECT
*output, history
*output, field, variable=PRESELECT
*output, history
*rigidbody, refnode=ASSEMBLY_PART-2-1_PART-2-1-REFPT_, analyticalsurface=ASSEMBLY_PART-2-1_SURF-1
*Step, name=Step-1, nlgeom=YES, inc=1000
*output, field, variable=PRESELECT
*output, history
*Step, name=Step-1, nlgeom=YES, inc=1000
*Step, name=Step-1, nlgeom=YES, inc=1000
*static
*boundary
*boundary
*output, field, variable=PRESELECT
*output, history
*contactoutput, master=ASSEMBLY_PART-2-1_SURF-1, slave=ASSEMBLY_SURF-2
*endstep
*Step, name=Step-1, nlgeom=YES, inc=1000
*static
*boundary
*boundary
*cload
*output, field, variable=PRESELECT
*output, history
*endstep
P R O B L E M S I Z E
NUMBER OF ELEMENTS IS 424
NUMBER OF ELEMENTS DEFINED BY THE USER AND *TIE 383
NUMBER OF INTERNAL ELEMENTS GENERATED FOR CONTACT 40
NUMBER OF NODES IS 505
NUMBER OF NODES DEFINED BY THE USER 425
NUMBER OF INTERNAL NODES GENERATED BY THE PROGRAM 80
TOTAL NUMBER OF VARIABLES IN THE MODEL 931
(DEGREES OF FREEDOM PLUS MAX NO. OF ANY LAGRANGE MULTIPLIER
VARIABLES. INCLUDE *PRINT,SOLVE=YES TO GET THE ACTUAL NUMBER.)
END OF USER INPUT PROCESSING
JOB TIME SUMMARY
USER TIME (SEC) = 0.0000
SYSTEM TIME (SEC) = 0.0000
TOTAL CPU TIME (SEC) = 0.0000
WALLCLOCK TIME (SEC) = 0
1
Abaqus 6.10-1 Date 10-Jan-2013 Time 11:56:02
For use by TEAM TBE under license from Dassault Systemes or its subsidiary.
STEP 1 INCREMENT 1
TIME COMPLETED IN THIS STEP 0.00
S T E P 1 S T A T I C A N A L Y S I S
AUTOMATIC TIME CONTROL WITH -
A SUGGESTED INITIAL TIME INCREMENT OF 1.000E-10
AND A TOTAL TIME PERIOD OF 1.00
THE MINIMUM TIME INCREMENT ALLOWED IS 1.000E-10
THE MAXIMUM TIME INCREMENT ALLOWED IS 1.00
LINEAR EQUATION SOLVER TYPE DIRECT SPARSE
LARGE DISPLACEMENT THEORY WILL BE USED
M E M O R Y E S T I M A T E
PROCESS FLOATING PT MINIMUM MEMORY MEMORY TO
OPERATIONS REQUIRED MINIMIZE I/O
PER ITERATION (MBYTES) (MBYTES)
1 9.78E+005 17 24
NOTE:
(1) SINCE ABAQUS DOES NOT PRE-ALLOCATE MEMORY AND ONLY ALLOCATES MEMORY AS NEEDED DURING THE ANALYSIS,
THE MEMORY REQUIREMENT PRINTED HERE CAN ONLY BE VIEWED AS A GENERAL GUIDELINE BASED ON THE BEST
KNOWLEDGE AVAILABLE AT THE BEGINNING OF A STEP BEFORE THE SOLUTION PROCESS HAS BEGUN.
(2) THE ESTIMATE IS NORMALLY UPDATED AT THE BEGINNING OF EVERY STEP. IT IS THE MAXIMUM VALUE OF THE
ESTIMATE FROM THE CURRENT STEP TO THE LAST STEP OF THE ANALYSIS, WITH UNSYMMETRIC SOLUTION TAKEN
INTO ACCOUNT IF APPLICABLE.
(3) SINCE THE ESTIMATE IS BASED ON THE ACTIVE DEGREES OF FREEDOM IN THE FIRST ITERATION OF THE
CURRENT STEP, THE MEMORY ESTIMATE MIGHT BE SIGNIFICANTLY DIFFERENT THAN ACTUAL USAGE FOR
PROBLEMS WITH SUBSTANTIAL CHANGES IN ACTIVE DEGREES OF FREEDOM BETWEEN STEPS (OR EVEN WITHIN
THE SAME STEP). EXAMPLES ARE: PROBLEMS WITH SIGNIFICANT CONTACT CHANGES, PROBLEMS WITH MODEL
CHANGE, PROBLEMS WITH BOTH STATIC STEP AND STEADY STATE DYNAMIC PROCEDURES WHERE ACOUSTIC
ELEMENTS WILL ONLY BE ACTIVATED IN THE STEADY STATE DYNAMIC STEPS.
(4) FOR MULTI-PROCESS EXECUTION, THE ESTIMATED VALUE OF FLOATING POINT OPERATIONS FOR EACH PROCESS
IS BASED ON AN INITIAL SCHEDULING OF OPERATIONS AND MIGHT NOT REFLECT THE ACTUAL FLOATING
POINT OPERATIONS COMPLETED ON EACH PROCESS. OPERATIONS ARE DYNAMICALY BALANCED DURING EXECUTION,
SO THE ACTUAL BALANCE OF OPERATIONS BETWEEN PROCESSES IS EXPECTED TO BE BETTER THAN THE ESTIMATE
PRINTED HERE.
(5) THE UPPER LIMIT OF MEMORY THAT CAN BE ALLOCATED BY ABAQUS WILL IN GENERAL DEPEND ON THE VALUE OF
THE "MEMORY" PARAMETER AND THE AMOUNT OF PHYSICAL MEMORY AVAILABLE ON THE MACHINE. PLEASE SEE
THE "ABAQUS ANALYSIS USER'S MANUAL" FOR MORE DETAILS. THE ACTUAL USAGE OF MEMORY AND OF DISK
SPACE FOR SCRATCH DATA WILL DEPEND ON THIS UPPER LIMIT AS WELL AS THE MEMORY REQUIRED TO MINIMIZE
I/O. IF THE MEMORY UPPER LIMIT IS GREATER THAN THE MEMORY REQUIRED TO MINIMIZE I/O, THEN THE ACTUAL
MEMORY USAGE WILL BE CLOSE TO THE ESTIMATED "MEMORY TO MINIMIZE I/O" VALUE, AND THE SCRATCH DISK
USAGE WILL BE CLOSE-TO-ZERO; OTHERWISE, THE ACTUAL MEMORY USED WILL BE CLOSE TO THE PREVIOUSLY
MENTIONED MEMORY LIMIT, AND THE SCRATCH DISK USAGE WILL BE ROUGHLY PROPORTIONAL TO THE DIFFERENCE
BETWEEN THE ESTIMATED "MEMORY TO MINIMIZE I/O" AND THE MEMORY UPPER LIMIT. HOWEVER ACCURATE
ESTIMATE OF THE SCRATCH DISK SPACE IS NOT POSSIBLE.
(6) USING "*RESTART, WRITE" CAN GENERATE A LARGE AMOUNT OF DATA WRITTEN IN THE WORK DIRECTORY.
THE ANALYSIS IS ENDED BECAUSE OF THE PROBLEMS ENCOUNTERED
LOOK AT THE MSG FILE FOR THE CAUSE OF THE TERMINATION
ANALYSIS COMPLETE
WITH 1 ERROR MESSAGES ON THE MSG FILE
AND 1 WARNING MESSAGES ON THE DAT FILE
AND 101 WARNING MESSAGES ON THE MSG FILE
90 WARNINGS ARE FOR NUMERICAL PROBLEMS
JOB TIME SUMMARY
USER TIME (SEC) = 3.3000
SYSTEM TIME (SEC) = 0.30000
TOTAL CPU TIME (SEC) = 3.6000
WALLCLOCK TIME (SEC) = 4