overflow during writing result

adam2008 · March 20, 2011, 00:05

Hi,
just got frustrated with overflow problem. The simulation looks alright during solving and is converging. But once the simulation is terminated or to write a backup result file, it gives overflow error and crashes. The simulation is a SST turbulence, fluid-solid conjugate simulation. The mesh quality is not good, I got a A negative SECTOR (ERROR #002100011) error, but simulation can run.

I have no idea how to fix it because the error happens during writing results instead of a typical divergence. What should I check? thanks a lot

+--------------------------------------------------------------------+
| ERROR #001100279 has occurred in subroutine ErrAction. |
| Message: |
| Floating point exception: Zero divide |
|
+--------------------------------------------------------------------+
+--------------------------------------------------------------------+
| Writing crash recovery file |
+--------------------------------------------------------------------+

+--------------------------------------------------------------------+
| ERROR #001100279 has occurred in subroutine ErrAction. |
| Message: |
| Stopped in routine C_FPX_HANDLER: |
+--------------------------------------------------------------------+

joey2007 · March 20, 2011, 14:11

You have to improve the mesh.

adam2008 · March 21, 2011, 09:11

problem solved. I traced to the location where the CFX indicates sector negative volume, and manually corrected local mesh. Then it went alright. Thanks for any attention.

March 20, 2011, 00:05	overflow during writing result	#1
adam2008 New Member Join Date: Jul 2009 Posts: 25 Rep Power: 17	Hi, just got frustrated with overflow problem. The simulation looks alright during solving and is converging. But once the simulation is terminated or to write a backup result file, it gives overflow error and crashes. The simulation is a SST turbulence, fluid-solid conjugate simulation. The mesh quality is not good, I got a A negative SECTOR (ERROR #002100011) error, but simulation can run. I have no idea how to fix it because the error happens during writing results instead of a typical divergence. What should I check? thanks a lot +--------------------------------------------------------------------+ \| ERROR #001100279 has occurred in subroutine ErrAction. \| \| Message: \| \| Floating point exception: Zero divide \| \| +--------------------------------------------------------------------+ +--------------------------------------------------------------------+ \| Writing crash recovery file \| +--------------------------------------------------------------------+ +--------------------------------------------------------------------+ \| ERROR #001100279 has occurred in subroutine ErrAction. \| \| Message: \| \| Stopped in routine C_FPX_HANDLER: \| +--------------------------------------------------------------------+

March 20, 2011, 14:11		#2
joey2007 Senior Member Join Date: Mar 2009 Location: Europe Posts: 169 Rep Power: 17	You have to improve the mesh. __________________ - - - - - ------------------------------------------------------------------------ Please do not forget: I am not paid for answering your questions. Thousands of issues can cause a division by zero. Please do not capture a thread, with the argument: "I have the same issue ...."

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Comparison the airfoil 0012 experimental result and simulation result	harrislcy	FLUENT	30	August 29, 2013 11:27
Read Result Files or User Defined Result	Aquilaris	ANSYS	0	February 9, 2011 06:25
Solution variables goes outside upper limit -how to localize fatal overflow occurance	Dimone	CFX	2	January 21, 2011 07:35
In a distance above the ground, my LES result is not good	panda60	OpenFOAM	2	January 22, 2010 08:52
overflow when interpolate initial result	richard	CFX	1	June 11, 2008 08:36

March 21, 2011, 09:11		#3
adam2008 New Member Join Date: Jul 2009 Posts: 25 Rep Power: 17	problem solved. I traced to the location where the CFX indicates sector negative volume, and manually corrected local mesh. Then it went alright. Thanks for any attention.