XANSYS Message: 38708 [Go back to message list]
[bookmark on del.icio.us]
No rating yet
Rate item:

Subject: Re: [struct] Sparse solver failure
Author: Peter Attar
Date: 2002-06-12 11:03:00

On Wed, 12 Jun 2002, Riccardo Testi wrote:
Looks like a memory problem like you've stated..
I'm surprised the error diagnostics are not better
for memory errors like this. Returning an ier
value when we as users don't have access to
the subroutines is kind of useless(unless of
course these ier values are published somewhere)

> Hello everybody.
> My model's features are:

> element types:
> SOLID95
> SHELL93
> TARGE170
> CONTA174
> number of elements: 46993
> number of nodes: 168161
> solver: sparse

> The solver crashes. The output and error files at the crashing moment look
> like this:

> OUTPUT FILE

> *** ELEMENT MATRIX FORMULATION TIMES
> TYPE NUMBER ENAME TOTAL CP AVE CP

> 1 36400 SOLID95 40.500 0.001113
> 2 1 TARGE170 0.000 0.000000
> 3 4210 CONTA174 3.109 0.000739
> 4 1832 SHELL93 1.969 0.001075
> Time at end of element matrix formulation CP= 81.21875.
> FORCE CONVERGENCE VALUE = 116.3 CRITERION= 1.170
> MOMENT CONVERGENCE VALUE = 0.000 CRITERION= 1.389

> SPARSE MATRIX DIRECT SOLVER.
> Number of equations = 506236, Maximum wavefront = 31274
> Memory available for solver = 643.82 MB
> Memory required for in-core = 4263.52 MB
> Optimal memory required for out-of-core = 183.21 MB
> Minimum memory required for out-of-core = 46.00 MB

> *** ERROR *** CP= 973.672 TIME= 16:30:19
> Sparse Matrix Solver failure. Please check the error file (file.err)
> for possible causes.

> *** ERROR *** CP= 973.672 TIME= 16:30:19
> Bisection may be activated if it is a nonlinear analysis.

> ERROR FILE

> *** WARNING *** CP= 21.875 TIME= 16:11:59
> Previous testing revealed that 1179 of the 46993 selected elements
> violate shape warning limits. To review warning messages, please see
> the output or error file, or issue the CHECK command.

> *** WARNING *** CP= 28.734 TIME= 16:12:06
> An initial contact closure factor (ICONT) of 2.7471381E-04 has been
> selected for real constant set 2.
> 0***** process error reported by subroutine xdslfa
> see xdslfa abstract (ier = -505)

> 0***** process error reported by subroutine xdslsv
> see xdslsv abstract (ier = -702)

> 0***** process error reported by subroutine xdslsl
> see xdslsl abstract (ier = -600)

> *** ERROR *** CP= 973.672 TIME= 16:30:19
> Sparse Matrix Solver failure. Please check the error file (file.err)
> for possible causes.

> Since strange subroutines are getting angry, I'm thinking everything's due
> to insufficient workspace. I've asked for 1200 megabytes total and 300 for
> database: NT doesn't allow me to ask for more, even if I've got 2 GB RAM.
> Can anybody please help me?
> P.S. = PGC runs (VERY slowly).

> Thank you very much

> Riccardo Testi
> R&D and Operations 2 Wheels/Engine Design
> Piaggio & C. spa
> v.le R. Piaggio, 25 - 56025 Pontedera (PI) - ITALY

Peter Attar
Graduate Student
Department of Mechanical Engineering
Duke University

Posts possibly associated with message #38708AuthorDateScore
38704[struct] Sparse solver failureRiccardo Testi2002/06/12 
38707Re: [struct] Sparse solver failureYan, Hong (Bolton) hyan@2002/06/12 
38708Re: [struct] Sparse solver failurePeter Attar2002/06/12 
38711Re: [struct] Sparse solver failureGene Poole2002/06/12 
38712Re: [struct] Sparse solver failureBogdan Balasa2002/06/12 
38754Re: [struct] Sparse solver failureRiccardo Testi2002/06/13