Modify a BC & rename everything - issues

djh2 · June 22, 2014, 11:47

Hi everyone, I've been working on a modified mappedPatch boundary condition. Since I'm working on a shared cluster I can't modify the mappedPatch source code, so I tried to copy and rename the files, but now I'm getting build errors and warnings and things just aren't playing nicely.

Since I'm extending functionality of the mappedPatchFieldBase class, it seems reasonable to add an additional constructor and develop this source. However, I don't think I should be modifying the files in the shared source folder, rather I should have my own files build to my $FOAM_USER_LIBBIN

I'm not sure if I'll be able to compile my own "local" OpenFOAM build, because I tried last night and had some problems with that.

So now I stand at a fork in the road: Do I pursue the renaming & reimplementation of the mappedPatch boundary condition as something similar with extended functionality? Or should I put my efforts into compiling my own OpenFOAM with the extended mappedPatchFieldBase class?

djh2 · June 22, 2014, 17:03

I was able to track down the source of some pain for this compilation, to this:

Code:

#ifdef NoRepository
#   include "turbulentMappedFieldFvPatchField.C"
#endif

Looking into NoRepository a bit more on the forums, such as: http://www.cfd-online.com/Forums/ope...epository.html

I was including several files in Make/files. After doing some investigating, it seems that I only need "turbulentMappedFieldFvPatchFields.C" in there, because it gets the others through dependencies.

However, I'm having some issues with running a simulation using the new boundary condition. I'm not very familiar with C++ and make files, so I'm sure its something little.

I get this error when compiling to LIB = $(FOAM_USER_LIBBIN)/libturbulentMappedField

Code:

symbol lookup error: /home/dave/OpenFOAM/dave-2.3.0/platforms/linux64GccDPOpt/lib/libturbulentMappedField.so: undefined symbol: Foam::turbulentMappedFieldFvPatchField<Foam::Vector<double> >::turbulentMappedFieldFvPatchField(Foam::fvPatch const&, Foam::DimensionedField<Foam::Vector<double>, Foam::volMesh> const&, Foam::dictionary const&)

Reading about the forums, tends to point me toward a bad order of linking or some other problem with my Make/files or options.

If you have the time to help, I have attached the files and the test case I've been using to debug. This started off as just a hack of a modification to the mappedPatch boundary condition, but now I'd like to separate it out and run it on my case for my M.S. thesis research. If it ends up providing good results, it is my intention to finish the implementation properly and provide it to the community.

djh2 · June 24, 2014, 00:03

After a lot of messing around, trial & error, or carefully planned software development, I made some changes that got things to compile. It could have been one of a few changes,

I've been regularly committing to my github on this project, so you could check it out if you'd like : https://github.com/henseldavidj/turbulentMappedField

I think this summarizes what made things work: https://github.com/henseldavidj/turb...a4adfdb09f923f

Anyways, at the current moment, it compiled and runs without error. I appreciate your views as motivation to keep searching and working toward this.

June 22, 2014, 11:47	Boundary Condition - symbol not found ( problem with links ? )	#1
djh2 New Member David H. Join Date: Oct 2013 Posts: 25 Rep Power: 12	Hi everyone, I've been working on a modified mappedPatch boundary condition. Since I'm working on a shared cluster I can't modify the mappedPatch source code, so I tried to copy and rename the files, but now I'm getting build errors and warnings and things just aren't playing nicely. Since I'm extending functionality of the mappedPatchFieldBase class, it seems reasonable to add an additional constructor and develop this source. However, I don't think I should be modifying the files in the shared source folder, rather I should have my own files build to my $FOAM_USER_LIBBIN I'm not sure if I'll be able to compile my own "local" OpenFOAM build, because I tried last night and had some problems with that. So now I stand at a fork in the road: Do I pursue the renaming & reimplementation of the mappedPatch boundary condition as something similar with extended functionality? Or should I put my efforts into compiling my own OpenFOAM with the extended mappedPatchFieldBase class? Last edited by djh2; June 23, 2014 at 19:01.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
how to set periodic boundary conditions	Ganesh	FLUENT	15	November 18, 2020 06:09
UDF to modify gravity via M_gravity[ND_ND] or DEFINE_ADJUST	jpo	Fluent UDF and Scheme Programming	19	March 20, 2020 14:34
Is it possible to modify Janaf Model in OpenFoam 2.1.1?	Traib	OpenFOAM	2	December 28, 2012 05:35
[General] Some Paraview Issues I can not solve	MR_Chicho	ParaView	1	September 24, 2012 05:03
fluent add additional zones for the mesh file	SSL	FLUENT	2	January 26, 2008 11:55

June 24, 2014, 00:03		#3
djh2 New Member David H. Join Date: Oct 2013 Posts: 25 Rep Power: 12	After a lot of messing around, trial & error, or carefully planned software development, I made some changes that got things to compile. It could have been one of a few changes, I've been regularly committing to my github on this project, so you could check it out if you'd like : https://github.com/henseldavidj/turbulentMappedField I think this summarizes what made things work: https://github.com/henseldavidj/turb...a4adfdb09f923f Anyways, at the current moment, it compiled and runs without error. I appreciate your views as motivation to keep searching and working toward this.