Possible bug in reconstructPar with new BC

flavio_galeazzo · September 30, 2009, 12:11

Hello Foamers,

I am facing a problem using reconstructPar to reconstruct cases using a new developed BC. The new velocity BC is based on the turbulentInlet BC, having a reference field (vectorField), a fluctuation scale (vector) and some scalar parameters.

When I run the reconstructPar, it writes all parameters as expected, only the reference field is wrongly written as a scalarField with nonsense values.

I have tested versions 1.5.x and 1.6, the same problem appears.

Have someone an idea how to solve (or bypass) this problem?

mattijs · October 1, 2009, 15:40

Make sure you implement rmap and automap methods. Use any other fvPatchField that has a additional field, e.g. totalPressure.

flavio_galeazzo · October 2, 2009, 04:33

Hello Mattijs,

Thank you for the prompt reply. You were right, it was a problem with the automap and rmap methods. It is working well right now.

Thank you again!

peterW · December 6, 2009, 17:13

Hello,

it seems that I am facing a similar problem. I changed the inletOutlet fvPatch (from OF 1.6) by making the valueFraction() depending on a field value in the local patch cell. The new velocity BC works fine in serial and parallel computations.

However, when I have used it in parallel, I get the same problem as already described above with reconstructPar. I tried to use automap and rmap and I compiled the BC as part of the solver and alternatively as a dynamic library (is that necessary for reconstructPar?). But that did not change anything. When I set the name of the BC back to inletOutlet in all the processor directories reconstructPar works fine again.

Any ideas what I should look for or what I could have missed?

Thanks
Peter

mattijs · December 7, 2009, 06:11

reconstructPar does not 'know' your boundary condition - it only knows the boundary conditions from the libraries it is linked with. In your system/controlDict add a

libs ("libYourLibrary.so")

to make it 'know' your boundary conditions.

September 30, 2009, 12:11	Possible bug in reconstructPar with new BC	#1
flavio_galeazzo Member Flavio Galeazzo Join Date: Mar 2009 Location: Karlsruhe, Germany Posts: 34 Rep Power: 18	Hello Foamers, I am facing a problem using reconstructPar to reconstruct cases using a new developed BC. The new velocity BC is based on the turbulentInlet BC, having a reference field (vectorField), a fluctuation scale (vector) and some scalar parameters. When I run the reconstructPar, it writes all parameters as expected, only the reference field is wrongly written as a scalarField with nonsense values. I have tested versions 1.5.x and 1.6, the same problem appears. Have someone an idea how to solve (or bypass) this problem?

October 1, 2009, 15:40		#2
mattijs Senior Member Mattijs Janssens Join Date: Mar 2009 Posts: 1,419 Rep Power: 26	Make sure you implement rmap and automap methods. Use any other fvPatchField that has a additional field, e.g. totalPressure. belier1988 likes this.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
reconstructPar --> fileName::stripInvalid() called for invalid fileName commandtouse	adona058	OpenFOAM Bugs	34	December 8, 2022 21:27
Bug in reconstructPar	david	OpenFOAM Bugs	10	May 26, 2009 12:11
Problem with reconstructPar	fabianpk	OpenFOAM	5	August 14, 2007 09:17
Bug reports	Mattijs Janssens (Mattijs)	OpenFOAM	0	January 10, 2005 10:05
Forum y2k Bug	Jonas Larsson	Main CFD Forum	1	January 5, 2000 10:22

October 2, 2009, 04:33		#3
flavio_galeazzo Member Flavio Galeazzo Join Date: Mar 2009 Location: Karlsruhe, Germany Posts: 34 Rep Power: 18	Hello Mattijs, Thank you for the prompt reply. You were right, it was a problem with the automap and rmap methods. It is working well right now. Thank you again!

December 6, 2009, 17:13		#4
peterW New Member Peter Wulf Join Date: Oct 2009 Location: Hamburg, Germany Posts: 3 Rep Power: 16	Hello, it seems that I am facing a similar problem. I changed the inletOutlet fvPatch (from OF 1.6) by making the valueFraction() depending on a field value in the local patch cell. The new velocity BC works fine in serial and parallel computations. However, when I have used it in parallel, I get the same problem as already described above with reconstructPar. I tried to use automap and rmap and I compiled the BC as part of the solver and alternatively as a dynamic library (is that necessary for reconstructPar?). But that did not change anything. When I set the name of the BC back to inletOutlet in all the processor directories reconstructPar works fine again. Any ideas what I should look for or what I could have missed? Thanks Peter

December 7, 2009, 06:11		#5
mattijs Senior Member Mattijs Janssens Join Date: Mar 2009 Posts: 1,419 Rep Power: 26	reconstructPar does not 'know' your boundary condition - it only knows the boundary conditions from the libraries it is linked with. In your system/controlDict add a libs ("libYourLibrary.so") to make it 'know' your boundary conditions.