Lack of Info statement blocks the code

Phicau · May 29, 2015, 12:12

Hi all,

I was just trying to update IHFOAM to work under OpenFOAM versions 2.3 and 2.4 and found the most puzzling programming glitch ever.

When I get to run a very simple example, the codes gets stuck updating one of the wave generation boundary conditions, inside an infinite loop because of some nan values. First strange thing: the same loop is used by the other BC that gets updated first, and works without any problems.

To assess what is happening and where, I place a bunch of Info statements, with which I detect the nan values. The most strange thing comes next, if I place any dummy Info statements much after where the initial code gets blocked, everything works flawlessly. The code works as intended, and no nan values are obtained.

The same code worked on previous versions and I am totally clueless on how a silly thing as an Info line in the future, may influence the past... Any ideas? Maybe a bug of the compiler?

I know this is little info for anyone to take any conclusion, but I will continue to struggle a couple of days and will post the code and example next week.

Best,

Pablo

Phicau · June 1, 2015, 05:51

Problem solved, my bad for using a variable without being initialized first. I will fix this bug and update the code very soon.

Cheers!

May 29, 2015, 12:12	Lack of Info statement blocks the code	#1
Phicau Senior Member Pablo Higuera Join Date: Jan 2011 Location: Auckland Posts: 627 Rep Power: 19	Hi all, I was just trying to update IHFOAM to work under OpenFOAM versions 2.3 and 2.4 and found the most puzzling programming glitch ever. When I get to run a very simple example, the codes gets stuck updating one of the wave generation boundary conditions, inside an infinite loop because of some nan values. First strange thing: the same loop is used by the other BC that gets updated first, and works without any problems. To assess what is happening and where, I place a bunch of Info statements, with which I detect the nan values. The most strange thing comes next, if I place any dummy Info statements much after where the initial code gets blocked, everything works flawlessly. The code works as intended, and no nan values are obtained. The same code worked on previous versions and I am totally clueless on how a silly thing as an Info line in the future, may influence the past... Any ideas? Maybe a bug of the compiler? I know this is little info for anyone to take any conclusion, but I will continue to struggle a couple of days and will post the code and example next week. Best, Pablo

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[ICEM] Advice on genetrating 2D blocks required	user_1	ANSYS Meshing & Geometry	0	December 3, 2014 05:46
[mesh manipulation] Combining multiple mesh blocks	ingojahn	OpenFOAM Meshing & Mesh Conversion	1	August 18, 2014 03:19
public CFD Code development	Heinz Wilkening	Main CFD Forum	38	March 5, 1999 11:44
What kind of Cmmercial CFD code you feel well?	Lans	Main CFD Forum	13	October 27, 1998 10:20
is there any info. about body-fitted code?	kuno	Main CFD Forum	1	July 28, 1998 19:14

June 1, 2015, 05:51		#2
Phicau Senior Member Pablo Higuera Join Date: Jan 2011 Location: Auckland Posts: 627 Rep Power: 19	Problem solved, my bad for using a variable without being initialized first. I will fix this bug and update the code very soon. Cheers!