CFD Online Discussion Forums
Page 2 of 2 1 2
Show 40 post(s) from this thread on one page

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   OpenFOAM Community Contributions (https://www.cfd-online.com/Forums/openfoam-community-contributions/)
-   -   [swak4Foam] funkySetFields compilation error (https://www.cfd-online.com/Forums/openfoam-community-contributions/106738-funkysetfields-compilation-error.html)

tayo September 10, 2012 12:45
Quote:
Originally Posted by gschaider (Post 381015)
The age is not a problem. I use 2.5.35 on the development version myself.The errors about the missing FixedValuePointPatchField.H should not concern you. That is only the dependency analysis for the sources which can not copy with some #ifdefs that are needed to make the sources compatible with the ext-version
Honestly, I'm not sure but everything seems fine except the stuff about FixedValuePointPatchField.H. I now notice that funkySetFields.dep was created and funkySetFields is also included in the FOAM_USER_APPBIN directory. I know this is meant to indicate that it is now compiled, could this be true? That would be great, finally!!! But when I tried to initialize a bubble from constant/polymesh directory for example using:

funkySetFields ‐field alpha1 ‐expression 1 ‐time 0 ‐keepPatches ‐condition "pow(pos().x,2) + pow(pos().y,2) < pow(0.0075,2) && pos().z <0.003"

I get the following below.

/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 2.1.1 |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 2.1.1-221db2718bbb
Exec : funkySetFields -field alpha1 -expression 1 -time 0 -keepPatches -condition pow(pos().x,2) + pow(pos().y,2) < pow(0.0075,2) && pos().z <0.003
Date : Sep 10 2012
Time : 11:27:43
Host : "ubuntu"
PID : 3987
Case : /home/tayo/OpenFOAM/tayo-2.1.1/run/mytestCases/risingBubble/constant/polyMesh
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
swakVersion: 0.2.0 - Friday the 13th (Release date: 2012-04-13)
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time



--> FOAM FATAL IO ERROR:
cannot find file

file: /home/tayo/OpenFOAM/tayo-2.1.1/run/mytestCases/risingBubble/constant/polyMesh/system/controlDict at line 0.

From function regIOobject::readStream()
in file db/regIOobject/regIOobjectRead.C at line 73.

FOAM exiting


I'm familiarizing myself with funkySetFields using a tutorial for now and even checked the examples given in swak4Foam website (where it was downloaded). As an example in the cavity case, you used the code below to set the velocity field to a "circle" around the center. Assuming I want to follow the driven-lid cavity as a basic example, do I just use this code and then follow the rest of the tutorial? I tried this and I obtained a similar error as above (this was hoping that funkySetFields has installed as I now assume). What do you think about this?

funkySetFields -case cavity -field U -expression '(grad(dist())^vector(0,0,-1))*mag(pos()-vector(0.05,0.05,0))/0.05' -time 0

gschaider September 10, 2012 14:33
Quote:
Originally Posted by tayo (Post 381090)
Honestly, I'm not sure but everything seems fine except the stuff about FixedValuePointPatchField.H. I now notice that funkySetFields.dep was created and funkySetFields is also included in the FOAM_USER_APPBIN directory. I know this is meant to indicate that it is now compiled, could this be true? That would be great, finally!!! But when I tried to initialize a bubble from constant/polymesh directory for example using:

funkySetFields ‐field alpha1 ‐expression 1 ‐time 0 ‐keepPatches ‐condition "pow(pos().x,2) + pow(pos().y,2) < pow(0.0075,2) && pos().z <0.003"

I get the following below.

/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 2.1.1 |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 2.1.1-221db2718bbb
Exec : funkySetFields -field alpha1 -expression 1 -time 0 -keepPatches -condition pow(pos().x,2) + pow(pos().y,2) < pow(0.0075,2) && pos().z <0.003
Date : Sep 10 2012
Time : 11:27:43
Host : "ubuntu"
PID : 3987
Case : /home/tayo/OpenFOAM/tayo-2.1.1/run/mytestCases/risingBubble/constant/polyMesh
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
swakVersion: 0.2.0 - Friday the 13th (Release date: 2012-04-13)
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time



--> FOAM FATAL IO ERROR:
cannot find file

file: /home/tayo/OpenFOAM/tayo-2.1.1/run/mytestCases/risingBubble/constant/polyMesh/system/controlDict at line 0.

From function regIOobject::readStream()
in file db/regIOobject/regIOobjectRead.C at line 73.

FOAM exiting


I'm familiarizing myself with funkySetFields using a tutorial for now and even checked the examples given in swak4Foam website (where it was downloaded). As an example in the cavity case, you used the code below to set the velocity field to a "circle" around the center. Assuming I want to follow the driven-lid cavity as a basic example, do I just use this code and then follow the rest of the tutorial? I tried this and I obtained a similar error as above (this was hoping that funkySetFields has installed as I now assume). What do you think about this?

funkySetFields -case cavity -field U -expression '(grad(dist())^vector(0,0,-1))*mag(pos()-vector(0.05,0.05,0))/0.05' -time 0
That is not a swak-problem but a simple PEBCAK (Problem exists between chair and keyboard): no OF-utiliy will work if you execute it in the polyMesh-directory. Go to the risingBubble-directory and it should work (or at least you get a different error)

tayo September 10, 2012 15:31
Like I said, I was following a tutorial. Here is the message I got when I ran the code from the main directory. First, I just want to make sure it's due to a swak4Foam compilation error or not.

/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 2.1.1 |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 2.1.1-221db2718bbb
Exec : funkySetFields -field alpha -expression 1 -time 0 -keepPatches -condition pow(pos().x,2) + pow(pos().y,2) < pow(0.0075,2) && pos().z <0.003
Date : Sep 10 2012
Time : 15:05:22
Host : "ubuntu"
PID : 2093
Case : /home/tayo/OpenFOAM/tayo-2.1.1/run/mytestCases/risingBubble
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
swakVersion: 0.2.0 - Friday the 13th (Release date: 2012-04-13)
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create mesh for time = 0



--> FOAM FATAL ERROR:
Cannot find file "points" in directory "polyMesh" in times 0 down to constant

From function Time::findInstance(const fileName&, const word&, const IOobject::readOption, const word&)
in file db/Time/findInstance.C at line 188.

FOAM exiting


Just to be sure, I also tried it on the basic driven-lid cavity tutorial. After blockMesh, I simply applied: funkySetFields -case cavity -field U -expression 'vector(0,0,0)' -time 0

and I still obtained

..........
--> FOAM FATAL ERROR:
funkySetFields: cannot open case directory "./cavity"


FOAM exiting

Similar error was obtained when the damBreak-tutorial was tried with the swak4Foam code after blockMesh was generated:

funkySetFields -case damBreak -time 0 -field gamma -expression " pos().x <= 0.1461 && pos().y <= 0.292 ? 1 : 0"

Error result is

--> FOAM FATAL ERROR:
funkySetFields: cannot open case directory "./damBreak"


Following this and previous conversation, can we tell if funkySetFields is properly installed or not. And if yes, what's the procedure to properly use it for initialization. Thanks

gschaider September 10, 2012 18:25
Quote:
Originally Posted by tayo (Post 381107)
Like I said, I was following a tutorial. Here is the message I got when I ran the code from the main directory. First, I just want to make sure it's due to a swak4Foam compilation error or not.

/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 2.1.1 |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 2.1.1-221db2718bbb
Exec : funkySetFields -field alpha -expression 1 -time 0 -keepPatches -condition pow(pos().x,2) + pow(pos().y,2) < pow(0.0075,2) && pos().z <0.003
Date : Sep 10 2012
Time : 15:05:22
Host : "ubuntu"
PID : 2093
Case : /home/tayo/OpenFOAM/tayo-2.1.1/run/mytestCases/risingBubble
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
swakVersion: 0.2.0 - Friday the 13th (Release date: 2012-04-13)
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create mesh for time = 0



--> FOAM FATAL ERROR:
Cannot find file "points" in directory "polyMesh" in times 0 down to constant

From function Time::findInstance(const fileName&, const word&, const IOobject::readOption, const word&)
in file db/Time/findInstance.C at line 188.

FOAM exiting


Just to be sure, I also tried it on the basic driven-lid cavity tutorial. After blockMesh, I simply applied: funkySetFields -case cavity -field U -expression 'vector(0,0,0)' -time 0

and I still obtained

..........
--> FOAM FATAL ERROR:
funkySetFields: cannot open case directory "./cavity"


FOAM exiting

Similar error was obtained when the damBreak-tutorial was tried with the swak4Foam code after blockMesh was generated:

funkySetFields -case damBreak -time 0 -field gamma -expression " pos().x <= 0.1461 && pos().y <= 0.292 ? 1 : 0"

Error result is

--> FOAM FATAL ERROR:
funkySetFields: cannot open case directory "./damBreak"


Following this and previous conversation, can we tell if funkySetFields is properly installed or not. And if yes, what's the procedure to properly use it for initialization. Thanks
Both problems are basic OF-usage problems:
- missing points: there is no mesh
- can not open case: there is on case in the location specified

tayo September 10, 2012 18:41
I don't get please kindly explain. I generated the mesh in the damBreak for example. And ofcourse, I'm working in the directory. Please explain how to use it right. Thank you

tayo September 10, 2012 19:09
Thanks all. I think I got it working using the damBreak-tutorial now. I simply specified the location of the case (thought it would automatically detect it since I'm in the case dir) and then included -create since the gamma function was not yet created. This confirms that funkySetFields is properly installed regardless of all the warnings msgs. Special thanks to Bernhard and co for writing the swak4Foam. I now have to figure out how to properly apply it to my different cases.

tayo@ubuntu:~/OpenFOAM/tayo-2.1.1/run/mytestCases/damBreak$ funkySetFields -create -case $FOAM_RUN/mytestCases/damBreak -time 0 -field gamma -expression " pos().x <= 0.1461 && pos().y <= 0.292 ? 1 : 0"
/*---------------------------------------------------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |
| \\ / O peration | Version: 2.1.1 |
| \\ / A nd | Web: www.OpenFOAM.org |
| \\/ M anipulation | |
\*---------------------------------------------------------------------------*/
Build : 2.1.1-221db2718bbb
Exec : funkySetFields -create -case /home/tayo/OpenFOAM/tayo-2.1.1/run/mytestCases/damBreak -time 0 -field gamma -expression pos().x <= 0.1461 && pos().y <= 0.292 ? 1 : 0
Date : Sep 10 2012
Time : 18:56:29
Host : "ubuntu"
PID : 3159
Case : /home/tayo/OpenFOAM/tayo-2.1.1/run/mytestCases/damBreak
nProcs : 1
sigFpe : Enabling floating point exception trapping (FOAM_SIGFPE).
fileModificationChecking : Monitoring run-time modified files using timeStampMaster
allowSystemOperations : Disallowing user-supplied system call operations

// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
swakVersion: 0.2.0 - Friday the 13th (Release date: 2012-04-13)
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Create time

Create mesh for time = 0

Time = 0
Using command-line options

Creating field gamma

Putting " pos().x <= 0.1461 && pos().y <= 0.292 ? 1 : 0" into field gamma at t = "0" if condition "true" is true

Setting 2268 of 2268 cells
Writing to "gamma"
End

Sagun October 3, 2012 12:46
Hello Tayo,

I just went through the entire thread since I'm also having some difficulties in implementing swak4Foam. Here is what I have done so far:

1. Installed OpenFOAM version 2.1.1 on Linux 11.10
2. Installed bison, flex and m4 macro processor
3. Installed swak4Foam as per the instructions given on the wikiPage

But whenever I try to implement funkySetFields, I get this error: command not found. :(

What would you advise me to do? Should I uninstall everything and start from scratch all over again?

I was also wondering if it is possible for you to summarize in steps how you were finally able to get swak4Foam work.

Thanks and regards,
Sagun

gschaider October 3, 2012 14:16
Quote:
Originally Posted by Sagun (Post 384752)
Hello Tayo,

I just went through the entire thread since I'm also having some difficulties in implementing swak4Foam. Here is what I have done so far:

1. Installed OpenFOAM version 2.1.1 on Linux 11.10
2. Installed bison, flex and m4 macro processor
3. Installed swak4Foam as per the instructions given on the wikiPage

But whenever I try to implement funkySetFields, I get this error: command not found. :(

What would you advise me to do? Should I uninstall everything and start from scratch all over again?

I was also wondering if it is possible for you to summarize in steps how you were finally able to get swak4Foam work.

Thanks and regards,
Sagun
About point 3: Compilation with ./Allwmake worked without a problem? Retry ./Allwmake. Basically there should be only a number of lines about things being "up to date". Otherwise please post the errors that are reported

tayo October 3, 2012 16:35
Yep I think you should follow what Bernard advised and provide some of the error messages. I've actually installed swak4Foam on two additional computers and I had no big issue again. Also make sue that flex is installed. If you've tried all these and it doesn't still work, then I would uninstall everything and install again. It only takes a few minutes.

Sagun October 4, 2012 04:33
Hello,

Thank you so much to both of you. So this is what I get when I run wmake all in my directory of sources:

root@iwpc178:/opt/openfoam211/src/swak4Foam# wmake all
No 'swakConfiguration'. Python etc won't work
Checking swak4Foam-version and generating file
./Allwmake: 9: [[: not found
./Allwmake: 17: [[: not found
Bison is version 2.4.1
./Allwmake: 33: cannot open 2.3: No such file
./Allwmake: 33: [[: not found
OpenFOAM-version: Major 2 Minor 1 Patch 1
./Allwmake: 67: [[: not found
No change to swak4FoamParsers/foamVersion4swak.H
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libswak4FoamParsers.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libgroovyBC.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libswakFunctionObjects.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libsimpleFunctionObjects.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libsimpleSwakFunctionObjects.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libswakTopoSources.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libswakSourceFields.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libgroovyStandardBCs.so' is up to date.
SWAK_PYTHON_INCLUDE not defined .... no Python-Integration
make[1]: Entering directory `/opt/openfoam211/src/swak4Foam/Utilities/funkyDoCalc'
make[1]: `/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/bin/funkyDoCalc' is up to date.
make[1]: Leaving directory `/opt/openfoam211/src/swak4Foam/Utilities/funkyDoCalc'
make[1]: Entering directory `/opt/openfoam211/src/swak4Foam/Utilities/funkySetBoundaryField'
make[1]: `/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/bin/funkySetBoundaryField' is up to date.
make[1]: Leaving directory `/opt/openfoam211/src/swak4Foam/Utilities/funkySetBoundaryField'
make[1]: Entering directory `/opt/openfoam211/src/swak4Foam/Utilities/funkySetFields'
make[1]: `/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/bin/funkySetFields' is up to date.
make[1]: Leaving directory `/opt/openfoam211/src/swak4Foam/Utilities/funkySetFields'
make[1]: Entering directory `/opt/openfoam211/src/swak4Foam/Utilities/replayTransientBC'
make[1]: `/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/bin/replayTransientBC' is up to date.
make[1]: Leaving directory `/opt/openfoam211/src/swak4Foam/Utilities/replayTransientBC'

I can see there are some errors but I am unable to understand what they mean. Please help.

Regards,
Sagun

gschaider October 4, 2012 10:47
Quote:
Originally Posted by Sagun (Post 384836)
Hello,

Thank you so much to both of you. So this is what I get when I run wmake all in my directory of sources:

root@iwpc178:/opt/openfoam211/src/swak4Foam# wmake all
No 'swakConfiguration'. Python etc won't work
Checking swak4Foam-version and generating file
./Allwmake: 9: [[: not found
./Allwmake: 17: [[: not found
Bison is version 2.4.1
./Allwmake: 33: cannot open 2.3: No such file
./Allwmake: 33: [[: not found
OpenFOAM-version: Major 2 Minor 1 Patch 1
./Allwmake: 67: [[: not found
No change to swak4FoamParsers/foamVersion4swak.H
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libswak4FoamParsers.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libgroovyBC.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libswakFunctionObjects.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libsimpleFunctionObjects.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libsimpleSwakFunctionObjects.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libswakTopoSources.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libswakSourceFields.so' is up to date.
'/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/lib/libgroovyStandardBCs.so' is up to date.
SWAK_PYTHON_INCLUDE not defined .... no Python-Integration
make[1]: Entering directory `/opt/openfoam211/src/swak4Foam/Utilities/funkyDoCalc'
make[1]: `/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/bin/funkyDoCalc' is up to date.
make[1]: Leaving directory `/opt/openfoam211/src/swak4Foam/Utilities/funkyDoCalc'
make[1]: Entering directory `/opt/openfoam211/src/swak4Foam/Utilities/funkySetBoundaryField'
make[1]: `/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/bin/funkySetBoundaryField' is up to date.
make[1]: Leaving directory `/opt/openfoam211/src/swak4Foam/Utilities/funkySetBoundaryField'
make[1]: Entering directory `/opt/openfoam211/src/swak4Foam/Utilities/funkySetFields'
make[1]: `/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/bin/funkySetFields' is up to date.
make[1]: Leaving directory `/opt/openfoam211/src/swak4Foam/Utilities/funkySetFields'
make[1]: Entering directory `/opt/openfoam211/src/swak4Foam/Utilities/replayTransientBC'
make[1]: `/home/stripathi/OpenFOAM/root-2.1.1/platforms/linuxGccDPOpt/bin/replayTransientBC' is up to date.
make[1]: Leaving directory `/opt/openfoam211/src/swak4Foam/Utilities/replayTransientBC'

I can see there are some errors but I am unable to understand what they mean. Please help.

Regards,
Sagun
That looks fine (the errors in the beginning will go away in the next release and are not a problem).

Meditated on it for some hours and then it occurred to me: you're compiling swak as root, but using it as stripathi, right? The problem is that swak writes its stuff to $FOAM_USER_APPBIN where only the user who compiled it can "see" it. This is done because "non-official"-stuff does not belong in the global $FOAM_APPBIN (especially on multi-user installeations)

So the recommended way to compile it is as the user who is going to use it (there is a script to afterwards copy it to directories to site-wide access it, but if you've never heard of $FOAM_SITE_APPBIN then I don't recommend using it ... the next upgrade of swak4Foam will have a lot of surprises for you)

Sagun October 8, 2012 07:01
OMG, yes you are right.

And it finally worked!

Thanks a zillion!

Sagun October 23, 2012 10:53
Hello Bernhard,

I hope you have been doing well. I eventually got groovyBC to work and simulated second order Stokes' waves for the first time yesterday. It ran perfectly fine but when I tried to do the same today, oddly enough I get this error:

Courant Number mean: 0 max: 0
Interface Courant Number mean: 0 max: 0
deltaT = 0.011976048
Time = 0.011976048

swak4Foam: Allocating new repository for sampledGlobalVariables
MULES: Solving for alpha1
Phase-1 volume fraction = 0.2 Min(alpha1) = 0 Max(alpha1) = 1
MULES: Solving for alpha1
Phase-1 volume fraction = 0.2 Min(alpha1) = 0 Max(alpha1) = 1
#0 Foam::error::printStack(Foam::Ostream&) in "/opt/openfoam211/platforms/linuxGccDPOpt/lib/libOpenFOAM.so"
#1 Foam::sigFpe::sigHandler(int) in "/opt/openfoam211/platforms/linuxGccDPOpt/lib/libOpenFOAM.so"
#2 Uninterpreted:
#3 Foam::PCG::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const in "/opt/openfoam211/platforms/linuxGccDPOpt/lib/libOpenFOAM.so"
#4 Foam::fvMatrix<double>::solve(Foam::dictionary const&) in "/opt/openfoam211/platforms/linuxGccDPOpt/lib/libfiniteVolume.so"
#5
in "/opt/openfoam211/platforms/linuxGccDPOpt/bin/interFoam"
#6 __libc_start_main in "/lib/i386-linux-gnu/libc.so.6"
#7
in "/opt/openfoam211/platforms/linuxGccDPOpt/bin/interFoam"
Floating point exception


I haven't changed anything in my case files. Hence, I don't understand why I am getting this error today. Please take a look.

Thanks,
Sagun

gschaider October 23, 2012 17:23
Quote:
Originally Posted by Sagun (Post 388132)
Hello Bernhard,

I hope you have been doing well. I eventually got groovyBC to work and simulated second order Stokes' waves for the first time yesterday. It ran perfectly fine but when I tried to do the same today, oddly enough I get this error:

Courant Number mean: 0 max: 0
Interface Courant Number mean: 0 max: 0
deltaT = 0.011976048
Time = 0.011976048

swak4Foam: Allocating new repository for sampledGlobalVariables
MULES: Solving for alpha1
Phase-1 volume fraction = 0.2 Min(alpha1) = 0 Max(alpha1) = 1
MULES: Solving for alpha1
Phase-1 volume fraction = 0.2 Min(alpha1) = 0 Max(alpha1) = 1
#0 Foam::error::printStack(Foam::Ostream&) in "/opt/openfoam211/platforms/linuxGccDPOpt/lib/libOpenFOAM.so"
#1 Foam::sigFpe::sigHandler(int) in "/opt/openfoam211/platforms/linuxGccDPOpt/lib/libOpenFOAM.so"
#2 Uninterpreted:
#3 Foam::PCG::solve(Foam::Field<double>&, Foam::Field<double> const&, unsigned char) const in "/opt/openfoam211/platforms/linuxGccDPOpt/lib/libOpenFOAM.so"
#4 Foam::fvMatrix<double>::solve(Foam::dictionary const&) in "/opt/openfoam211/platforms/linuxGccDPOpt/lib/libfiniteVolume.so"
#5
in "/opt/openfoam211/platforms/linuxGccDPOpt/bin/interFoam"
#6 __libc_start_main in "/lib/i386-linux-gnu/libc.so.6"
#7
in "/opt/openfoam211/platforms/linuxGccDPOpt/bin/interFoam"
Floating point exception


I haven't changed anything in my case files. Hence, I don't understand why I am getting this error today. Please take a look.

Thanks,
Sagun
You're started from t=0 and one time it worked and one time it didn't. Shouldn't happen unless the first start wrote some additional stuff to the case. Did you alter the swak-installation (for instance upgrade) between the tries?

Hold the press .... now it comes back to me .... this looks like a problem that I fixed a couple of weeks ago ... something with uninitialized memory in groovyBC/mixed. Are you working with the release that came out last week? If not then chances are good that this is fixed in this release. Quote from the README
Code:
**** =groovyBC= makes =interFoam=-runs fail unpredictably
    Reason was an uninitialized =valueFraction= which sometimes has
    values that cause a floating point exception. Fixed

Sagun October 24, 2012 06:40
Hello Bernhard,

No I didn't alter the installation in any way. Also, Its been a while since I installed swak4Foam, so I'm pretty sure I'm not using the release that came out last week. The behaviour of groovyBC has been very erratic. Sometimes it works and sometimes it doesn't. What should I do?

Thanks,
Sagun

gschaider October 24, 2012 09:22
Quote:
Originally Posted by Sagun (Post 388265)
Hello Bernhard,

No I didn't alter the installation in any way. Also, Its been a while since I installed swak4Foam, so I'm pretty sure I'm not using the release that came out last week. The behaviour of groovyBC has been very erratic. Sometimes it works and sometimes it doesn't. What should I do?
In that case upgrade. As I said above: The problem looks a lot like one that was fixed in the latest release (0.2.1) of swak4Foam

Sagun December 2, 2012 11:01
Hello Bernhard,

I hope you are doing well. I wanted to ask you that is it possible to generate waves in 3D using groovyBC?

Thanks,
Sagun

gschaider December 2, 2012 16:46
Quote:
Originally Posted by Sagun (Post 395293)
Hello Bernhard,

I hope you are doing well. I wanted to ask you that is it possible to generate waves in 3D using groovyBC?
a) how does that have to do with the title of this thread ("funkySetFields compilation error"). Neither is the question about FSF nor about compilation errors

b) what do you mean with "generate waves in 3D"? groovyBC is "only" a boundary condition: if fed with the right expressions it induce waves (if the solver is right). But if you can call the "generate waves in 3D" is a philosophical question

Sagun December 2, 2012 17:14
Apologies for posting on this thread and for being so vague. I did not think it to be necessary to create a new thread for a question which I thought only had a 'yes/no' answer to it, but now I realize that maybe I should have done otherwise.

By 'generating waves in 3D' I meant that is it possible to generate waves at one end in a 3-dimensional tank. All the simulations that I have done so far have been in a 2-D tank which has constrained the flow only to 'over' an object and not 'around' it.

Thanks,
Sagun

gschaider December 3, 2012 05:18
Quote:
Originally Posted by Sagun (Post 395332)
Apologies for posting on this thread and for being so vague. I did not think it to be necessary to create a new thread for a question which I thought only had a 'yes/no' answer to it, but now I realize that maybe I should have done otherwise.
OK.

Quote:
Originally Posted by Sagun (Post 395332)
By 'generating waves in 3D' I meant that is it possible to generate waves at one end in a 3-dimensional tank. All the simulations that I have done so far have been in a 2-D tank which has constrained the flow only to 'over' an object and not 'around' it.
After all for OpenFOAM 2D is only a special case of 3D so I don't see why it shouldn't generate 3D waves ... as long as the BCs are physically correct ... for which groovyBC can't be held responsible

Ah. And also consider the waves2foam-toolbox (which can be found on this forum and/or the Wiki)


All times are GMT -4. The time now is 03:02.
Page 2 of 2 1 2
Show 40 post(s) from this thread on one page