|
[Sponsors] |
[swak4Foam] GroovyBC the dynamic cousin of funkySetFields that lives on the suburb of the mesh |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
February 19, 2009, 18:10 |
GroovyBC the dynamic cousin of funkySetFields that lives on the suburb of the mesh
|
#1 |
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Hi!
Those who find funkySetFields useful might find this interesting: http://openfoamwiki.net/index.php/Contrib_groovyBC Basically it is a mixed-boundary condition where value, gradient and valueFraction can be specified using expressions. Bernhard PS: Starting from now I will answer all questions concerning setParabolicInlet.C with "Use groovyBC". That was the main reason for writing that boundary condition: setParabolicInlet on steroids
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request |
|
February 20, 2009, 05:36 |
Bernhard,
You're the man!
|
#2 |
Senior Member
|
Bernhard,
You're the man! Funky + pyFoam + Groovy is the trifecta of OpenFOAM! I officially nominate you for the 2009 OpenFOAM MVP award, which will be presented at the 2009 Workshop in Montreal by the AOFAS (Academy of OpenFOAM Arts and Sciences) ;-) Any ideas for a prize worthy of this award?? On a serious note: good job, and thanks for contributions! Eric |
|
February 25, 2009, 10:35 |
Hi Bernhard
I have tried
|
#3 |
Senior Member
Alexandre Pereira
Join Date: Mar 2009
Posts: 155
Rep Power: 17 |
Hi Bernhard
I have tried groovyBC, nice tool... :-D BTW I have checked your posting in SVN, and I have a question : Supposing I want to calculate the total ammount of NO2 in a dieselEngineFoam simulation in each time slice of my simulation, how could i use the volumeFieldFunctionObject that you posted in the SVN repository...? I mean, that is what that library is for, tight...?! Best regards Alex |
|
February 26, 2009, 10:31 |
Hi Alex!
Did you have a loo
|
#4 |
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Hi Alex!
Did you have a look at the README there? It refers you to http://openfoamwiki.net/index.php/Co...unctionObjects (which is for my standards a quite exhaustive documentation) Yes. Something like NO2Total { type volumeIntegrate; functionObjectLibs ( "libsimpleFunctionObjects.so" ); verbose true; fields ( NO2 ); } should do that. BUT as you are propably aware NO2 is the Mass-fraction and integrating that is only meaningful if the density is constant (IMHO). So what you'd need is something like fields ( NO2*rho ); and that is currently not possible (it would mean marrying the funkySetFields-function parser with a function object - not that difficult, basically one would have to tell the parser "get the files from the database not the disk", but it still needs some time) Bernhard
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request |
|
February 26, 2009, 11:00 |
Hi Bernhard
Thx for the hin
|
#5 |
Senior Member
Alexandre Pereira
Join Date: Mar 2009
Posts: 155
Rep Power: 17 |
Hi Bernhard
Thx for the hint... :-) BRGDS Alex |
|
February 26, 2009, 11:47 |
Hi Again Bernhard,
As long
|
#6 |
Senior Member
Alexandre Pereira
Join Date: Mar 2009
Posts: 155
Rep Power: 17 |
Hi Again Bernhard,
As long as my ( tiny ) C++ knowledge does not allow for more, I will resort to a "crude" but effective solution : For each time, write the volScalarField rho*[NO2] and after the simulation use the volumeIntegrate functionObject to query the FOAM database and understand if Mr Yakov Borisovich Zeldovich will allow me to design a low emission high compression ratio HCCI engine... !! I think tha dieselEngineFoam is the right app to do this... since I will use a blend of DME and isoOctane, with high fraction of exhaust recycle gas and a very lean burn stoichiometry, I can assume tha most of my fuel droplets will be evaporated at time of ignition, leading to Homogeneous charge premixed flame combustion... ( This is what i think... ) Tyx anyway BRGDS Alex |
|
February 26, 2009, 13:28 |
Hi Alex!
I was thinking to
|
#7 |
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Hi Alex!
I was thinking to complicated (funkyFieldsFunctionObject). Of course, if you're willing to to modify your solver then you don't even have to write to disk. Just create (outside the timeloop!) a field named "NO2mass" (not the variable name. The name in the IOobject-part is important). Update it at every timestep. If you add it to the fields list the function object will find it (praise to the objectRegistry and to its implementor) Bernhard
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request |
|
February 27, 2009, 10:12 |
Hi Bernhard
I changed the s
|
#8 |
Senior Member
Alexandre Pereira
Join Date: Mar 2009
Posts: 155
Rep Power: 17 |
Hi Bernhard
I changed the solver, and now i can access volumeIntegrated quantities.. nice piece of code your simpleFunctionObjects... :-) Now for one more question , simpleFunctionObjects compiles trivially in Linux gcc, I ported it ( at least tried to ) to win32 using the cross compiler mingw32, so that ppl at mechanical engineering department in my university can use it in win simulations with OpenFOAM; You see. at my department ppl are very ..."conservative" meaning that they have the "Microsoft mindset" so... convincing them to shift to Linux is not an easy task... Anyway, I tried to build the dll under mingw32 compiler, and it reports that HUGE, which is refered to in panicDump.C is not defined within that scope... Since i do not know enough of the class hierarchy in OpenFOAM, which #include should i add to panicDump.H in order to the linker to find "HUGE"...? were is it defined... ? mingw32 linker is not as "smart" as g++, i guess.. :-( Thx for yr help :-) Alex |
|
March 2, 2009, 05:50 |
Hi Bernhard!
Question to Yo
|
#9 |
Member
Marco Müller
Join Date: Mar 2009
Location: Germany
Posts: 94
Rep Power: 17 |
Hi Bernhard!
Question to Your groovyBC: Can I create boundary conditions for dynamicFvMesh solver (e. g. displacementLaplacian) with this tool? Propably not, because a pointScalarField has to be defined?!... Is there a way to do this? How long do I have to wait until groovyBC is able to? ;) Thanks a lot Marco |
|
March 2, 2009, 07:24 |
@Alexandre:
The problem is no
|
#10 |
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
@Alexandre:
The problem is not the compiler. It is that from math.h the line # define HUGE 3.40282347e+38F seems to be missing for the mingw-headers. As a quick fix just insert this line into panicDump.H @marco: Way ahead of you. Last week I checked the groovyBCPointPatch-class into the svn. I just didn't announce it. There is also a small demo for that there (an addaption of the icoDyMFoam/movingCone). Just do a "svn update", recompile and you should be set .
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request |
|
March 2, 2009, 08:27 |
Hi Bernhard
Thanks a lot :-
|
#11 |
Senior Member
Alexandre Pereira
Join Date: Mar 2009
Posts: 155
Rep Power: 17 |
Hi Bernhard
Thanks a lot :-) I will try this BRGDS Alexandre |
|
March 3, 2009, 03:29 |
Hi Bernhard,
thanks a lot,
|
#12 |
Member
Marco Müller
Join Date: Mar 2009
Location: Germany
Posts: 94
Rep Power: 17 |
Hi Bernhard,
thanks a lot, too. (Das müsste meiner Diplomarbeit ziemlich gut helfen... ;) Marco |
|
March 3, 2009, 11:05 |
Hi Bernhard
Thanks for your c
|
#13 |
Senior Member
Hua Zen
Join Date: Mar 2009
Posts: 138
Rep Power: 17 |
Hi Bernhard
Thanks for your contribution. I have a feature request and wonder whether it's possible. It seems that both funkySetFields and GroovyBC are only for analytical expressions.I wonder whether these utilities could read in data from a file instead of expression.Then the user could use any programming language to generate more complicated fields for the initial and boundary conditions and then use these utilities to start running. |
|
March 3, 2009, 12:23 |
Hi Hua!
For boundary condit
|
#14 |
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Hi Hua!
For boundary conditions the timeVaryingMappedFixedValue-condition might be just what you need (haven't used it myself; have a look at the board for that). For initial-conditions I don't see the point: a) if you get the data from another program/solver foo then you'll have to write a data-convert for that format: fooToFoam (have a look maybe the converter is already there) b) if you write a custom-built program, then you might as well write it in OpenFOAM-C++ because that situation boils down to case a) So: no. There are currently no plans for that, unless the need for that arises in one of the projects I get paid for. Bernhard
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request |
|
March 3, 2009, 15:01 |
Hi Bernhard
Thanks for you
|
#15 |
Senior Member
Hua Zen
Join Date: Mar 2009
Posts: 138
Rep Power: 17 |
Hi Bernhard
Thanks for your reply and useful infomation. |
|
March 5, 2009, 07:24 |
Hi Bernhard,
just tried com
|
#16 |
Member
Marco Müller
Join Date: Mar 2009
Location: Germany
Posts: 94
Rep Power: 17 |
Hi Bernhard,
just tried compiling groovyBC, seems that there are (at least) two files missing: could not open file PatchValueExpressionParser.tab.hh for source file groovyBCPointPatchFields.C could not open file pointPatchFieldMapper.H for source file groovyBCPointPatchFields.C Maybe you can help? Thanks Marco |
|
March 5, 2009, 08:27 |
Hi Marco!
PatchValueExpress
|
#17 |
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Hi Marco!
PatchValueExpressionParser.tab.hh is generated from the yy-File and will live in the Make-directory. According to groovyBCPointPatchFields.dep the other file should reside here: $(WM_PROJECT_DIR)/src/OpenFOAM/lnInclude/pointPatchFieldMapper.H Which version are you using? I compiled and tested that BC with a vanilla-1.5. I quickly checked and it seems to me that this file is not present in the dev-version. Maybe it's called differently or resides somewhere else. Don't know (there seems to be a number of other stuff missing from the dev that is needed for the point-BC) I think for the time being you'll have to remove groovyBCPointPatchFields.C from Make/files and live without the point variant. Or you try to cheat: copy the files that compiler is missing from a vailla/git-version to the directory of the library and compile (the compiler should find them now). Repeat until the compiler runs out of complaints. But even if it compiles I can't guarantee that it will work. Bernhard
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request |
|
May 21, 2009, 08:48 |
|
#18 |
New Member
Luther Terblanche
Join Date: May 2009
Posts: 15
Rep Power: 16 |
Hallo Bernard
My text in bold blue. I have the same problem as Marco (I think). I am new to OpenFOAM, but this is what I did: luther@luther-laptop:~/OpenFOAM/OpenFOAM-1.5/src$ svn checkout https://openfoam-extend.svn.sourcefo...aries/groovyBC A groovyBC/PatchResult.C A groovyBC/PatchValueExpressionLexer.ll A groovyBC/groovyBCFvPatchFields.H A groovyBC/PatchResult.H A groovyBC/PatchValueExpressionDriverI.H A groovyBC/PatchValueExpressionParser.yy A groovyBC/groovyBCFvPatchField.C A groovyBC/groovyBCPointPatchFields.C A groovyBC/PatchResultI.H A groovyBC/README A groovyBC/groovyBCFvPatchField.H A groovyBC/groovyBCPointPatchFields.H A groovyBC/Demos A groovyBC/Demos/circulatingSplash A groovyBC/Demos/circulatingSplash/0 A groovyBC/Demos/circulatingSplash/0/gamma A groovyBC/Demos/circulatingSplash/0/pd A groovyBC/Demos/circulatingSplash/0/U A groovyBC/Demos/circulatingSplash/system A groovyBC/Demos/circulatingSplash/system/fvSchemes A groovyBC/Demos/circulatingSplash/system/controlDict A groovyBC/Demos/circulatingSplash/system/decomposeParDict A groovyBC/Demos/circulatingSplash/system/fvSolution A groovyBC/Demos/circulatingSplash/customRegexp A groovyBC/Demos/circulatingSplash/constant A groovyBC/Demos/circulatingSplash/constant/polyMesh A groovyBC/Demos/circulatingSplash/constant/polyMesh/boundary A groovyBC/Demos/circulatingSplash/constant/polyMesh/blockMeshDict A groovyBC/Demos/circulatingSplash/constant/RASProperties A groovyBC/Demos/circulatingSplash/constant/dynamicMeshDict A groovyBC/Demos/circulatingSplash/constant/transportProperties A groovyBC/Demos/circulatingSplash/constant/environmentalProperties A groovyBC/Demos/movingConeDistorted A groovyBC/Demos/movingConeDistorted/0 A groovyBC/Demos/movingConeDistorted/0/p A groovyBC/Demos/movingConeDistorted/0/cellMotionUx A groovyBC/Demos/movingConeDistorted/0/U A groovyBC/Demos/movingConeDistorted/0/pointMotionUx A groovyBC/Demos/movingConeDistorted/system A groovyBC/Demos/movingConeDistorted/system/tetFemSolution A groovyBC/Demos/movingConeDistorted/system/fvSchemes A groovyBC/Demos/movingConeDistorted/system/controlDict A groovyBC/Demos/movingConeDistorted/system/fvSolution A groovyBC/Demos/movingConeDistorted/constant A groovyBC/Demos/movingConeDistorted/constant/polyMesh A groovyBC/Demos/movingConeDistorted/constant/polyMesh/boundary A groovyBC/Demos/movingConeDistorted/constant/polyMesh/blockMeshDict A groovyBC/Demos/movingConeDistorted/constant/dynamicMeshDict A groovyBC/Demos/movingConeDistorted/constant/transportProperties A groovyBC/Demos/pulsedPitzDaily A groovyBC/Demos/pulsedPitzDaily/0 A groovyBC/Demos/pulsedPitzDaily/0/nuSgs A groovyBC/Demos/pulsedPitzDaily/0/p A groovyBC/Demos/pulsedPitzDaily/0/nuTilda A groovyBC/Demos/pulsedPitzDaily/0/B A groovyBC/Demos/pulsedPitzDaily/0/U A groovyBC/Demos/pulsedPitzDaily/0/k A groovyBC/Demos/pulsedPitzDaily/system A groovyBC/Demos/pulsedPitzDaily/system/fvSchemes A groovyBC/Demos/pulsedPitzDaily/system/controlDict A groovyBC/Demos/pulsedPitzDaily/system/fvSolution A groovyBC/Demos/pulsedPitzDaily/constant A groovyBC/Demos/pulsedPitzDaily/constant/LESProperties A groovyBC/Demos/pulsedPitzDaily/constant/polyMesh A groovyBC/Demos/pulsedPitzDaily/constant/polyMesh/boundary A groovyBC/Demos/pulsedPitzDaily/constant/polyMesh/blockMeshDict A groovyBC/Demos/pulsedPitzDaily/constant/transportProperties A groovyBC/Demos/runSplash.py A groovyBC/Demos/wobbler A groovyBC/Demos/wobbler/0 A groovyBC/Demos/wobbler/0/D A groovyBC/Demos/wobbler/0/T A groovyBC/Demos/wobbler/system A groovyBC/Demos/wobbler/system/fvSchemes A groovyBC/Demos/wobbler/system/controlDict A groovyBC/Demos/wobbler/system/fvSolution A groovyBC/Demos/wobbler/impulse.data A groovyBC/Demos/wobbler/constant A groovyBC/Demos/wobbler/constant/polyMesh A groovyBC/Demos/wobbler/constant/polyMesh/boundary A groovyBC/Demos/wobbler/constant/polyMesh/blockMeshDict A groovyBC/Demos/wobbler/constant/mechanicalProperties A groovyBC/Demos/wobbler/constant/thermalProperties A groovyBC/PatchValueExpressionDriver.C A groovyBC/groovyBCPointPatchField.C A groovyBC/Make A groovyBC/Make/mybison A groovyBC/Make/files A groovyBC/Make/myflex A groovyBC/Make/options A groovyBC/groovyBCFvPatchFields.C A groovyBC/PatchValueExpressionDriver.H A groovyBC/groovyBCPointPatchField.H Checked out revision 1241. luther@luther-laptop:~/OpenFOAM/OpenFOAM-1.5/src$ luther@luther-laptop:~/OpenFOAM/OpenFOAM-1.5/src$ cd groovyBC luther@luther-laptop:~/OpenFOAM/OpenFOAM-1.5/src/groovyBC$ wmake libso wmakeLnInclude: linking include files to /home/luther/OpenFOAM/OpenFOAM-1.5/src/groovyBC/lnInclude Making dependency list for source file PatchResult.C Making dependency list for source file PatchValueExpressionParser.yy could not open file PatchValueExpressionParser.tab.hh for source file PatchValueExpressionParser.yy Making dependency list for source file PatchValueExpressionLexer.ll could not open file PatchValueExpressionParser.tab.hh for source file PatchValueExpressionLexer.ll Making dependency list for source file PatchValueExpressionDriver.C could not open file PatchValueExpressionParser.tab.hh for source file PatchValueExpressionDriver.C Making dependency list for source file groovyBCFvPatchFields.C could not open file PatchValueExpressionParser.tab.hh for source file groovyBCFvPatchFields.C Making dependency list for source file groovyBCPointPatchFields.C could not open file MixedPointPatchField.H for source file groovyBCPointPatchFields.C could not open file PatchValueExpressionParser.tab.hh for source file groovyBCPointPatchFields.C could not open file PointPatchFieldMapper.H for source file groovyBCPointPatchFields.C SOURCE=PatchResult.C ; g++ -m32 -Dlinux -DDP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -O3 -DNoRepository -ftemplate-depth-40 -IMake/linuxGccDPOpt -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/finiteVolume/lnInclude -IlnInclude -I. -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/OpenFOAM/lnInclude -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/OSspecific/Unix/lnInclude -fPIC -pthread -c $SOURCE -o Make/linuxGccDPOpt/PatchResult.o PatchResult.C: In member function ‘void Foam::PatchResult::uglyDelete()’: PatchResult.C:97: warning: deleting ‘void*’ is undefined SOURCE=PatchValueExpressionParser.yy ; rm -f Make/linuxGccDPOpt/PatchValueExpressionParser.C Make/linuxGccDPOpt/PatchValueExpressionParser.tab.hh; bison -ra -v -d $SOURCE ; mv *.tab.cc Make/linuxGccDPOpt/PatchValueExpressionParser.C ; mv *.tab.hh Make/linuxGccDPOpt/PatchValueExpressionParser.tab.hh ; mv *.hh Make/linuxGccDPOpt ; g++ -m32 -Dlinux -DDP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -O3 -DNoRepository -ftemplate-depth-40 -IMake/linuxGccDPOpt -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/finiteVolume/lnInclude -IlnInclude -I. -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/OpenFOAM/lnInclude -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/OSspecific/Unix/lnInclude -fPIC -pthread -c Make/linuxGccDPOpt/PatchValueExpressionParser.C -o Make/linuxGccDPOpt/PatchValueExpressionParser.o bison: invalid option -- 'r' Usage: bison [-dltvyVu] [-b file-prefix] [-p name-prefix] [-o outfile] [-h headerfile] [-S skeleton] [-H header-skeleton] [--debug] [--defines] [--fixed-output-files] [--no-lines] [--verbose] [--version] [--yacc] [--usage] [--help] [--file-prefix=prefix] [--name-prefix=prefix] [--skeleton=skeletonfile] [--headerskeleton=headerskeletonfile] [--output=outfile] [--header-name=header] grammar-file mv: cannot stat `*.tab.cc': No such file or directory mv: cannot stat `*.tab.hh': No such file or directory mv: cannot stat `*.hh': No such file or directory g++: Make/linuxGccDPOpt/PatchValueExpressionParser.C: No such file or directory g++: no input files make: *** [Make/linuxGccDPOpt/PatchValueExpressionParser.o] Error 1 luther@luther-laptop:~/OpenFOAM/OpenFOAM-1.5/src/groovyBC$ I have also remove the line "groovyBCPointPatchFields.C" from "Make/files" and ran "wmake libso" again but got pretty much the same thing. Shown below: luther@luther-laptop:~/OpenFOAM/OpenFOAM-1.5/src/groovyBC$ wmake libso wmakeLnInclude: linking include files to /home/luther/OpenFOAM/OpenFOAM-1.5/src/groovyBC/lnInclude Making dependency list for source file PatchResult.C Making dependency list for source file PatchValueExpressionParser.yy could not open file PatchValueExpressionParser.tab.hh for source file PatchValueExpressionParser.yy Making dependency list for source file PatchValueExpressionLexer.ll could not open file PatchValueExpressionParser.tab.hh for source file PatchValueExpressionLexer.ll Making dependency list for source file PatchValueExpressionDriver.C could not open file PatchValueExpressionParser.tab.hh for source file PatchValueExpressionDriver.C Making dependency list for source file groovyBCFvPatchFields.C could not open file PatchValueExpressionParser.tab.hh for source file groovyBCFvPatchFields.C SOURCE=PatchResult.C ; g++ -m32 -Dlinux -DDP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -O3 -DNoRepository -ftemplate-depth-40 -IMake/linuxGccDPOpt -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/finiteVolume/lnInclude -IlnInclude -I. -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/OpenFOAM/lnInclude -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/OSspecific/Unix/lnInclude -fPIC -pthread -c $SOURCE -o Make/linuxGccDPOpt/PatchResult.o PatchResult.C: In member function ‘void Foam::PatchResult::uglyDelete()’: PatchResult.C:97: warning: deleting ‘void*’ is undefined SOURCE=PatchValueExpressionParser.yy ; rm -f Make/linuxGccDPOpt/PatchValueExpressionParser.C Make/linuxGccDPOpt/PatchValueExpressionParser.tab.hh; bison -ra -v -d $SOURCE ; mv *.tab.cc Make/linuxGccDPOpt/PatchValueExpressionParser.C ; mv *.tab.hh Make/linuxGccDPOpt/PatchValueExpressionParser.tab.hh ; mv *.hh Make/linuxGccDPOpt ; g++ -m32 -Dlinux -DDP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -O3 -DNoRepository -ftemplate-depth-40 -IMake/linuxGccDPOpt -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/finiteVolume/lnInclude -IlnInclude -I. -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/OpenFOAM/lnInclude -I/home/luther/OpenFOAM/OpenFOAM-1.5/src/OSspecific/Unix/lnInclude -fPIC -pthread -c Make/linuxGccDPOpt/PatchValueExpressionParser.C -o Make/linuxGccDPOpt/PatchValueExpressionParser.o bison: invalid option -- 'r' Usage: bison [-dltvyVu] [-b file-prefix] [-p name-prefix] [-o outfile] [-h headerfile] [-S skeleton] [-H header-skeleton] [--debug] [--defines] [--fixed-output-files] [--no-lines] [--verbose] [--version] [--yacc] [--usage] [--help] [--file-prefix=prefix] [--name-prefix=prefix] [--skeleton=skeletonfile] [--headerskeleton=headerskeletonfile] [--output=outfile] [--header-name=header] grammar-file mv: cannot stat `*.tab.cc': No such file or directory mv: cannot stat `*.tab.hh': No such file or directory mv: cannot stat `*.hh': No such file or directory g++: Make/linuxGccDPOpt/PatchValueExpressionParser.C: No such file or directory g++: no input files make: *** [Make/linuxGccDPOpt/PatchValueExpressionParser.o] Error 1 Please can you see if you can help me? Kind Regards Luther |
|
May 21, 2009, 11:20 |
|
#19 | |
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Hi Luther!
The problem lies in this part of the output: Quote:
There are two options:
Bernhard |
||
May 22, 2009, 04:41 |
|
#20 | |
New Member
Luther Terblanche
Join Date: May 2009
Posts: 15
Rep Power: 16 |
Quote:
Thank you for your response. I very much appreciate it. I have downloaded version 2.4.1 of bison on the page you recommended. I did a ./configure; make; make install; However I still get the old version displayed when I type "bison -V". Don't know if it maybe have not installed correctly: luther@luther-laptop:~/OpenFOAM/luther-1.5/run/groovyWaveTank$ bison -V bison++ Version 1.21.9-1, adapted from GNU bison by coetmeur@icdc.fr Maintained by Magnus Ekdahl <magnus@debian.org> However, I then did a "wmake libso" again in the sources of groovyBC and some warnings came out, but at the end it said that groovyBC.so is up to date. I run a few of the Demos in the Demos directory and thay seemed to have worked whithout error. But when I run interFoam on groovyWaveTank I got an error. Do you perhaps know how I can fix it? Sorry if the questions are trivial, but I am new to openFOAM and appreciate your help alot. Here is the error: luther@luther-laptop:~/OpenFOAM/luther-1.5/run/groovyWaveTank$ interFoam /*---------------------------------------------------------------------------*\ | ========= | | | \\ / F ield | OpenFOAM: The Open Source CFD Toolbox | | \\ / O peration | Version: 1.5 | | \\ / A nd | Web: http://www.OpenFOAM.org | | \\/ M anipulation | | \*---------------------------------------------------------------------------*/ Exec : interFoam Date : May 22 2009 Time : 10:18:57 Host : luther-laptop PID : 19035 Case : /home/luther/OpenFOAM/luther-1.5/run/groovyWaveTank nProcs : 1 // * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * // Create time Create mesh for time = 0 Reading environmentalProperties Reading field pd Reading field gamma Reading field U Reading/calculating face flux field phi Reading transportProperties Selecting incompressible transport model Newtonian Selecting incompressible transport model Newtonian Calculating field g.h time step continuity errors : sum local = 0, global = 0, cumulative = 0 Attempt to return dictionary entry as a primitive file: /home/luther/OpenFOAM/luther-1.5/run/groovyWaveTank/system/fvSolution:corr:reconditioner from line 23 to line 35. From function ITstream& primitiveEntry::stream() const in file db/dictionary/dictionaryEntry/dictionaryEntry.C at line 83. FOAM aborting #0 Foam::error:rintStack(Foam::Ostream&) in "/home/luther/OpenFOAM/OpenFOAM-1.5/lib/linuxGccDPOpt/libOpenFOAM.so" #1 Foam::IOerror::abort() in "/home/luther/OpenFOAM/OpenFOAM-1.5/lib/linuxGccDPOpt/libOpenFOAM.so" #2 Foam::dictionaryEntry::stream() const in "/home/luther/OpenFOAM/OpenFOAM-1.5/lib/linuxGccDPOpt/libOpenFOAM.so" #3 Foam::dictionary::lookup(Foam::word const&, bool) const in "/home/luther/OpenFOAM/OpenFOAM-1.5/lib/linuxGccDPOpt/libOpenFOAM.so" #4 Foam::PCG::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const in "/home/luther/OpenFOAM/OpenFOAM-1.5/lib/linuxGccDPOpt/libOpenFOAM.so" #5 Foam::fvMatrix<double>::solve(Foam::Istream&) in "/home/luther/OpenFOAM/OpenFOAM-1.5/lib/linuxGccDPOpt/libfiniteVolume.so" #6 main in "/home/luther/OpenFOAM/OpenFOAM-1.5/applications/bin/linuxGccDPOpt/interFoam" #7 __libc_start_main in "/lib/tls/i686/cmov/libc.so.6" #8 Foam::regIOobject::readIfModified() in "/home/luther/OpenFOAM/OpenFOAM-1.5/applications/bin/linuxGccDPOpt/interFoam" Aborted luther@luther-laptop:~/OpenFOAM/luther-1.5/run/groovyWaveTank$ Kind Regards Luther Kind Regards Luther |
||
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Ship resistance shows wiggles when using Overset mesh and dynamic mesh in Fluent | Qingsong | FLUENT | 2 | March 21, 2022 15:08 |
sliding mesh problem in CFX | Saima | CFX | 46 | September 11, 2021 07:38 |
[ICEM] Dynamic mesh setup with ICEM | David121284 | ANSYS Meshing & Geometry | 0 | April 11, 2014 04:19 |
Dynamic Mesh "Shadow Wall" | thezack | FLUENT | 0 | June 4, 2013 22:09 |
dynamic mesh for drop interface | IndrajitW | FLUENT | 0 | March 30, 2013 08:03 |