Difference between revisions of "HowTo Adding a new boundary condition"
From OpenFOAMWiki
m |
m |
||
(One intermediate revision by one other user not shown) | |||
Line 3: | Line 3: | ||
# Choose a boundary condition that is close to the one you want - we'll call it <tt>originalFvPatchField</tt>. | # Choose a boundary condition that is close to the one you want - we'll call it <tt>originalFvPatchField</tt>. | ||
# Copy the directory contents to anywhere (say <tt>run/myCode</tt>). | # Copy the directory contents to anywhere (say <tt>run/myCode</tt>). | ||
− | # Rename all the copied files to a new name (say <tt>customFvPatchField</tt>). | + | # Rename all the copied files to a new name (say <tt>customFvPatchField</tt>). <bash>for i in `ls`; do mv $i `echo $i|sed s/originalFvPatchField/customFvPatchField/g`;done</bash> |
− | + | # Search & replace all text in all the new files old name for new name (<tt>originalFvPatchField</tt> replaced with <tt>customFvPatchField</tt>) <bash> for i in `ls`; do sed -i s/originalFvPatchField/customFvPatchField/g $i;done</bash> | |
− | # Search & replace all text in all the new files old name for new name (<tt>originalFvPatchField</tt> replaced with <tt>customFvPatchField</tt>) | + | |
− | + | ||
# Modify the code to suit your needs. | # Modify the code to suit your needs. | ||
# Create the directory structure: <tt>myCode/Make</tt>, and create <tt>files</tt> and <tt>options</tt> in it. | # Create the directory structure: <tt>myCode/Make</tt>, and create <tt>files</tt> and <tt>options</tt> in it. | ||
Line 21: | Line 19: | ||
With reference to [http://www.cfd-online.com/Forums/openfoam/72434-custom-boundary-condition-openfoam.html]. | With reference to [http://www.cfd-online.com/Forums/openfoam/72434-custom-boundary-condition-openfoam.html]. | ||
+ | See also [http://www.tfd.chalmers.se/~hani/kurser/OS_CFD/implementBoundaryCondition.pdf]. | ||
[[User:Marupio|Marupio]] 17:00, 26 February 2010 (UTC) | [[User:Marupio|Marupio]] 17:00, 26 February 2010 (UTC) | ||
[[Category:Tutorials]] | [[Category:Tutorials]] |
Latest revision as of 16:54, 16 January 2014
First look at groovyBC. If this isn't suitable, follow these steps below.
- Choose a boundary condition that is close to the one you want - we'll call it originalFvPatchField.
- Copy the directory contents to anywhere (say run/myCode).
- Rename all the copied files to a new name (say customFvPatchField).
for i in `ls`; do mv $i `echo $i|sed s/originalFvPatchField/customFvPatchField/g`;done
- Search & replace all text in all the new files old name for new name (originalFvPatchField replaced with customFvPatchField)
for i in `ls`; do sed -i s/originalFvPatchField/customFvPatchField/g $i;done
- Modify the code to suit your needs.
- Create the directory structure: myCode/Make, and create files and options in it.
- Put the relevant info into files:
- Search for originalFvPatchField in finiteVolume/Make/files.
- Copy the relevant entry (entries) into your myCode/Make/files
- Rename the entries as necessary - rename it with your customFvPatchField naming (if there's an s on the end, keep it there).
- Tell it what the new library name will be. Use $(FOAM_USER_LIBBIN) instead of $(FOAM_LIBBIN), and add lib to the front of the new name. It should look something like: LIB = $(FOAM_USER_LIBBIN)/libcustomPatchField
- The options file should have EXE_INC (for any includes such as -I$(LIB_SRC)/finiteVolume/lnInclude for finiteVolume) and LIB_LIBS (for included libraries, such as -lfiniteVolume for finiteVolume). Look at other LIB_LIBS for examples.
- $wmake libso
- Add whatever new dictionary entries are needed to your initial conditions files, such as 0/U and 0/P files.
- Add libs ( "libcustomFvPatchField.so" "libOpenFOAM.so" ) to controlDict
- It should run now.
With reference to [1]. See also [2]. Marupio 17:00, 26 February 2010 (UTC)