NX 7.5 Simulation No Results Found

[mhinrich]

I am having issues with a 2D simulation I am trying to run. Everything has been mid-surfaced and I have fixed all of my meshing errors. Now when I run the simulation and click on my results, it comes back with "No Results Found". I checked my F06 file for "fatal" and this is what popped up:

*** USER FATAL MESSAGE 3000 (SITDELC)
INSUFFICIENT MEMORY SPECIFIED FOR THE ITERATIVE SOLVER. INCREASE
THE MEMORY LIMIT BY 8471 MB

My solver is initially set to run with 4000 MB. So I increased the memory by the said amount and the simulation would just quit on its own and not even write a f06 file. Does anyone have any clue as to what I can do about this? If it helps I am running Windows 7 Enterprise 64 bit with 48 GB of ram, and the model check comes back with no errors or warnings.

 

[BlasMolero]

Hello!,
Disable the iterative solver, then you will use the DIRECT SPARSE SOLVER, that is more effective when dealing with SHELL models. Also, in the solver properties, set minimum 1024 MB.
Best regards,
Blas.

~~~~~~~~~~~~~~~~~~~~~~
Blas Molero Hidalgo
Ingeniero Industrial
Director

IBERISA
48011 BILBAO (SPAIN)
WEB:

http://www.iberisa.com

Blog de FEMAP & NX Nastran:

http://iberisa.wordpress.com/

 

[mhinrich]

I did as you said and got the analysis to start running, but then it ran into another error.

*** USER FATAL MESSAGE 1012 (GALLOC)
DBSET SCRATCH IS FULL AND NEEDS TO BE EXPANDED.
USER ACTION: SEE THE NX NASTRAN INSTALLATION AND OPERATIONS GUIDE OR
TAN 4893 ON THE UGS WEB SITE FOR METHODS TO MAKE LARGER DATABASES.
BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GALLOC , FILE INDEX = 0.
STATUS = 0

 

[BlasMolero]

Hello!,
You run out of disk space in the scratch directory, check your instalation, ask your local VAR to revise your installation, check the settings in your RCF file nastran keywords, one of them is SDIR keyword, it specifies the default scratch directory, check you have space & rights to write.

Also, I note you mention you have NX Nastran installed on a 64-bit system, then you will activate the NX NASTRAN ILP-64bit, this option will instruct NX Nastran to solve using the “ILP” version of 64-bit Nastran. “ILP” is able to allocate more memory than “regular” 64-bit Nastran by using a 64-bit word size and 64-bit memory pointer, while integers are 64-bits and floating point uses one 64-bit word. The "regular" NX NASTRAN only address 8 GB RAM memory, not matter you have 48 GB ram installed in your system.

The "regular" 32-bit integer executable can allocate up to 8 Gb of memory, while the executable compiled with a 64-bit integer size can allocate approximately 20 million terabytes. Practically speaking, there are no machines currently supporting more than half a terabyte, thus the amount of memory these executables can allocate is only limited by the amount of memory installed on the machine.

Exactly there are 3 different executable types available for NX Nastran:

• 32-bit word size and 32-bit memory pointer size, designated ILP-32. Integers are 32-bits and floating point uses two 32-bit words.
• 32-bit word size and 64-bit memory pointer size, designated LP-64. Integers are 32-bits and floating point uses two 32-bit words.
• 64-bit word size and 64-bit memory pointer size, designated ILP-64. Integers are 64-bits and floating point uses one 64-bit word.

When the ILP-32 and LP-64 executables are used, the bytes_per_word is 4. When the ILP-64 executable is used, the bytes_per_word is 8. This difference is important when you are specifying memory with the “memory” keyword. See the “memory” keyword in the NX Nastran Quick Reference Guide for more information.

Best regards,
Blas.



~~~~~~~~~~~~~~~~~~~~~~
Blas Molero Hidalgo
Ingeniero Industrial
Director

IBERISA
48011 BILBAO (SPAIN)
WEB:

http://www.iberisa.com

Blog de FEMAP & NX Nastran:

http://iberisa.wordpress.com/