A Problem
Dear foamers!
I have a problem when I using Funky to set a complicated fields .my profile is as below: funkySetFields -time 0 -field alpha1 -expression 1 -condition "pos().y-1e-9-7.5e-9*exp((pow(pos().x-15e-9,10)+1)*log(1-pow((pos().x-15e-9)/7.5e-9,2)))<=0" but I think that this module have some problem with power function. I have this error: Putting "1" into field alpha1 at t = "0" if condition "pos().y-1e-9-7.5e-9*exp((pow(pos().x-15e-9,10)+1)*log(1-pow((pos().x-15e-9)/7.5e-9,2)))<=0" is true #0 Foam::error::printStack(Foam::Ostream&) in "/home/Zakerzadeh/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so" #1 Foam::sigFpe::sigFpeHandler(int) in "/home/Zakerzadeh/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so" #2 Uninterpreted: #3 log in "/lib/libm.so.6" #4 Foam::log(Foam::Field<double>&, Foam::UList<double> const&) in "/home/Zakerzadeh/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so" #5 Foam::tmp<Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> > Foam::log<Foam::fvPatchField, Foam::volMesh>(Foam::GeometricField<double, Foam::fvPatchField, Foam::volMesh> const&) in "/home/Zakerzadeh/OpenFOAM/Zakerzadeh-1.6/applications/bin/linuxGccDPOpt/funkySetFields" #6 .L21360 at ValueExpressionParser.C:0 #7 ValueExpressionDriver::parse(std::string const&) in "/home/Zakerzadeh/OpenFOAM/Zakerzadeh-1.6/applications/bin/linuxGccDPOpt/funkySetFields" #8 doAnExpression(Foam::fvMesh const&, Foam::word const&, Foam::string const&, Foam::string const&, Foam::Time const&, bool, bool, bool, Foam::dimensionSet const&, bool, Foam::List<Foam::word> const&) in "/home/Zakerzadeh/OpenFOAM/Zakerzadeh-1.6/applications/bin/linuxGccDPOpt/funkySetFields" #9 main in "/home/Zakerzadeh/OpenFOAM/Zakerzadeh-1.6/applications/bin/linuxGccDPOpt/funkySetFields" #10 __libc_start_main in "/lib/libc.so.6" #11 Foam::regIOobject::writeObject(Foam::IOstream::str eamFormat, Foam::IOstream::versionNumber, Foam::IOstream::compressionType) const in "/home/Zakerzadeh/OpenFOAM/Zakerzadeh-1.6/applications/bin/linuxGccDPOpt/funkySetFields" Floating point exception Is there anyone have any idea about it. Sincerely |
According to error #3 it is due to the log-function. So make sure that you are not evaluating log(r), with r<=0.
Best regards, Niels |
Yes,you are right!
But when I have this problem unless I decrease the power to 2 or 1. I test an easier case with just power term . Its better to test this case . I believe that this program have some problems with power.I appreciate if you have any suggestion about it? Sincerely |
This is very embarassing! What had worked previously with OF-1.6, now is not working with OF-1.6.x. I followed my steps but now im getting this error:
Code:
position.hh: In function ‘bool ve::operator==(const ve::position&, const ve::position&)’: |
I do not know what i did, but it is working now. Thanks all.
|
Quote:
If you really feel that there is a bug in FSF report it at https://sourceforge.net/apps/mantisb...e_status_id=-2 Bernhard |
I'm trying to install funkySetFields (v1.6) on OF-1.6, but i get this error in "Allwmake" :
Quote:
Thanks in advance! |
Quote:
|
Tx man. this message is very useful for such beginner like me
Quote:
|
Quote:
No, i did not even try to compile any OF-utility before. But i realised, that i was trying to install the funkySetFields-Tool from the POSTprocressing-directory. I don't know if that made any difference. Anyway, now i tried to install it from the PREprocessing directory and got these lines : Code:
hiwi@wmpc05:~/OpenFOAM/OpenFOAM-1.6/applications/utilities/preProcessing/FunkySetFields> ./Allwmake Thanks. |
Quote:
Quote:
Bernhard |
Quote:
Now it compiled without errors. Thank you very much, again ! :) |
funkySetFields and OpenFOAM 1.7.0
Hi all,
Tried to compile the FSF library and encountered the same error as the post previously about it being calling overloaded function. I can't figure out what's wrong... Anyone here willing to help? Thanks. Regards, Kelvin Code:
SOURCE=ValueExpressionDriver.C ; g++ -m64 -Dlinux64 -DWM_DP -Wall -Wno-strict-aliasing -Wextra -Wno-unused-parameter -Wold-style-cast -Wnon-virtual-dtor -O3 -DNoRepository -ftemplate-depth-40 -IMake/linux64GccDPOpt -I/home/kklloh/OpenFOAM/OpenFOAM-1.7.0/src/finiteVolume/lnInclude -I/home/kklloh/OpenFOAM/OpenFOAM-1.7.0/src/meshTools/lnInclude -IlnInclude -I. -I/home/kklloh/OpenFOAM/OpenFOAM-1.7.0/src/OpenFOAM/lnInclude -I/home/kklloh/OpenFOAM/OpenFOAM-1.7.0/src/OSspecific/POSIX/lnInclude -fPIC -c $SOURCE -o Make/linux64GccDPOpt/ValueExpressionDriver.o |
Quote:
|
Quote:
As added information, the bison version I have is 2.4.1, flex 2.5.35, and FSF from the OpenFOAM extend project, which I got from the source file "ICE Revision: $Id: funkySetFields.C 7567 2007-06-20 12:38:50Z bgschaid $" Am compiling FSF in OF 1.7.0 with 64-bit Fedora Core 13 OS. Thanks. Regards, Kelvin |
Quote:
Quote:
Quote:
|
yes, i'm back with more funky set fields trouble. This time im actually getting the same error as the original poster, i.e, floating point exception. And i know what is causing it exactly, i just can't fathom why.
ill write my funkysetfields dict here, the abbreviate version: Code:
temperature1 This is the error message Code:
#0 Foam::error::printStack(Foam::Ostream&) in "/home/gustavo/OpenFOAM/OpenFOAM-1.6.x/lib/linux64GccDPOpt/libOpenFOAM.so" Thanks for your time GB |
Quote:
pos().z and check whether the result is definitely bigger than 0 for your mesh Bernhard |
Hello Bernhard, thanks for your reply (and sorry for taking so much time). It indeed is positive as expected. Ill try other values of z to see how the problem develops. I still find it peculiar that it woudl work with 25 and not 15.
Thanks again UPDATE: i discovered it works on funky set fields from 18 onwards. 17 already gives floating point exception. But ill post this here for everyone to see: http://www.wolframalpha.com/input/?i=plot+52.96281*%28z^0.262054%29+from+0+to+0.15 Why is it giving floating point exception? This must have such a simple reason. |
Quote:
- modify OF-sources to print out intermediate results - use a Debug-version of OF, a core-dump and gdb to have a look at the backtrace - by trial and error try expressions of the form "pow(0.0345,0.262054)" to find a value that fails (start with the largest and smallest values from the previous experiment) OK. That's three possibilities, but who's counting. Anyway. As far as I can tell it is either a problem with pow or a problem with the expression (but you ruled that out) but not a problem of FSF per see BTW: have you tried it with different powers? ( 0.1, 0, 1, 2 ...) |
All times are GMT -4. The time now is 13:58. |