decomposePar memory corruption

lichmaster · July 1, 2011, 05:05

Hi Foamers,
this is my first post, and I'm also rather new to OpenFoam as well.

I've implemented an actuator disk solver as in
http://www.tfd.chalmers.se/~hani/kurser/OS_CFD/erikSvenning/erikSvenningReport.pdf

I had to change some minor things, for that tutorial was written for OF 1.5 dev and I've OF 1.71 and OF 2... however, it compiled fine and also seems to work fine on single processor (still have to test the results, though)

The problem is: if I try to run decomposePar, i get a memory corruption message, which never occurred before... Any ideas about what to check?
checkMesh gives no errors, and it's a simple "box" geometry with 512k cells created with blockMesh

Since it works correctly with other solvers, is there any chance that the error somehow comes from the new solver?

Thanks

lichmaster · July 4, 2011, 06:30

I've managed to solve this problem...
I didn't correctly set the I.C of VolumeForce: the object entry was still "U" instead of "VolumeForce".
However, I find it very strange that no "canonical" error messages are given for this kind of mistakes, and also that single processor simulations have no problems at all...

July 1, 2011, 05:05	[solved] decomposePar memory corruption	#1
lichmaster New Member Lorenzo A. Ricciardi Join Date: Mar 2011 Posts: 27 Rep Power: 15	Hi Foamers, this is my first post, and I'm also rather new to OpenFoam as well. I've implemented an actuator disk solver as in http://www.tfd.chalmers.se/~hani/kurser/OS_CFD/erikSvenning/erikSvenningReport.pdf I had to change some minor things, for that tutorial was written for OF 1.5 dev and I've OF 1.71 and OF 2... however, it compiled fine and also seems to work fine on single processor (still have to test the results, though) The problem is: if I try to run decomposePar, i get a memory corruption message, which never occurred before... Any ideas about what to check? checkMesh gives no errors, and it's a simple "box" geometry with 512k cells created with blockMesh Since it works correctly with other solvers, is there any chance that the error somehow comes from the new solver? Thanks Last edited by lichmaster; July 4, 2011 at 06:31. Reason: solved

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Fluent Parallel Memory Usage	David Christopher	FLUENT	1	March 3, 2011 03:20
How to optimize the memory usage when using FEM	vasilis	Main CFD Forum	11	August 25, 2009 00:57
Memory error?	Young	CFX	3	September 30, 2008 12:33
CFX CPU time & real time	Nick Strantzias	CFX	8	July 23, 2006 18:50
Run-Time memory conifguration Error	Graeme	CFX	1	February 21, 2006 00:04

July 4, 2011, 06:30		#2
lichmaster New Member Lorenzo A. Ricciardi Join Date: Mar 2011 Posts: 27 Rep Power: 15	I've managed to solve this problem... I didn't correctly set the I.C of VolumeForce: the object entry was still "U" instead of "VolumeForce". However, I find it very strange that no "canonical" error messages are given for this kind of mistakes, and also that single processor simulations have no problems at all...