[fisch]

Hi,

I try using the toPoints Method for initialising my pointMotionU field because if i don't do it the following error occurs:

--> FOAM FATAL ERROR: 
 inconsistent types: pointMotionU is  pointVectorField while the expression evaluates to a volVectorField

    From function doAnExpression()
    in file funkySetFields.C at line 328.

So i think i should use the toPoints(...) function in my funkySetFieldsDict like

      setPointMotionUstart
    {
        field pointMotionU;
        expression "vector(toPoint(0),toPoint(0.5e-1) * toPoint(pi) * (toPoint(0.1e1) - toPoint(pos().y)),toPoint(0)) ";
        keepPatches true;
    }

But now, the following error occurs:

--> FOAM FATAL ERROR: 
 Parser Error at "1.8-14" :"field toPoint not existing or of wrong type"
"vector(toPoint(0),toPoint(0.5e-1) * toPoint(pi) * (toPoint(0.1e1) - toPoint(pos().y)),toPoint(0)) "
"        ^^^^^^^                                                                                   "

    From function parsingValue
    in file lnInclude/CommonValueExpressionDriverI.H at line 802.

FOAM exiting

Is there some mistake on my side or is it simply not possible to work like this??

Is it maybe something for the mantis bugtracker?

Thanks a lot

[gschaider]

Originally Posted by fisch

Hi,

I try using the toPoints Method for initialising my pointMotionU field because if i don't do it the following error occurs:

--> FOAM FATAL ERROR: 
 inconsistent types: pointMotionU is  pointVectorField while the expression evaluates to a volVectorField

    From function doAnExpression()
    in file funkySetFields.C at line 328.

So i think i should use the toPoints(...) function in my funkySetFieldsDict like

      setPointMotionUstart
    {
        field pointMotionU;
        expression "vector(toPoint(0),toPoint(0.5e-1) * toPoint(pi) * (toPoint(0.1e1) - toPoint(pos().y)),toPoint(0)) ";
        keepPatches true;
    }

But now, the following error occurs:

--> FOAM FATAL ERROR: 
 Parser Error at "1.8-14" :"field toPoint not existing or of wrong type"
"vector(toPoint(0),toPoint(0.5e-1) * toPoint(pi) * (toPoint(0.1e1) - toPoint(pos().y)),toPoint(0)) "
"        ^^^^^^^                                                                                   "

    From function parsingValue
    in file lnInclude/CommonValueExpressionDriverI.H at line 802.

FOAM exiting

Is there some mistake on my side or is it simply not possible to work like this??

Is it maybe something for the mantis bugtracker?

Thanks a lot

Due to historical reason (groovyBC and funkySetFields started out as two different projects) there are inconsistencies between the two grammars. In the field grammar there is

- "point(3.4)" this only works for a scalar (no expressions or anything)
- "interpolateToPoint(0.1e1-pos().y)" this works for any expression

Yes. A Mantis bug "Clean up this unholy mess in the grammars" might speed this up (although your immediate problem should be solved)

[mecman]

Hi all
i want use of FunkySetFields for may case in OpenFoam2.1.1,i instal swak4Foam for this version witout problem,i made FunkySetFieldsDict for my case and after when i run that i see this problem

--> FOAM FATAL ERROR:
funkySetFields: time/latestTime option is required
From function main()
in file funkySetFields.C at line 641.
FOAM exiting
what is my mistake?

[gschaider]

Originally Posted by mecman

Hi all
i want use of FunkySetFields for may case in OpenFoam2.1.1,i instal swak4Foam for this version witout problem,i made FunkySetFieldsDict for my case and after when i run that i see this problem

--> FOAM FATAL ERROR:
funkySetFields: time/latestTime option is required
From function main()
in file funkySetFields.C at line 641.
FOAM exiting
what is my mistake?

Please don't post the same question in multiple threads and don't hijack threads whose topic is not related to your problem (which could have been easily solved by actually READING the error message)

[mecman]

Originally Posted by gschaider

Please don't post the same question in multiple threads and don't hijack threads whose topic is not related to your problem (which could have been easily solved by actually READING the error message)

Sorry man...: