Menu

#221 groovyBC: toPoint(cellMotionU) not working well in the first time step

None
acknowledged
None
normal
minor
always
none
Library
2.0
other
2014-06-19
2012-07-09
Anonymous
No

Originally created by: rupert.fisch

Hi (me again),

i try to calculate meshMotion problems (currently using velocityLaplacian) and i get problems using the toPoint(cellMotionU) command for defining the value of the BC.
It seems that in the first time step only the inner mesh (cf. groovyToPoint1.png) is moving and not the points of the BC.
whereas if i define the same field as in pointMotionU with all single toPoint(pi) etc... it works well.

Is this a bug or a misuse?
---- additional_information ----
thanks for an answer

Discussion

  • Bernhard Gschaider

    Definitely a bug I'd say. The question is just: in swak (my problem) or in the underlying motion-solver.

    Just some questions:
    - in subsequent timesteps everything is alright? And is it your impression that the actual point motion was OK and just the points were not correctly drawn? (or updated internally)?
    - could you provide me with a simple testcase?

     
  • Anonymous

    Anonymous - 2012-07-12

    Originally by: rupert.fisch

    I uploaded a file containing a test case (i start the row of tests with ./doAllscript_both) and a solver scalarTransportDyMFoam (with some extensions for source terms). In the test case the bottom patch goes up with a sin(pi*time()) function.

    This strange motion is only occuring in the first time step. afterwards the points and the cells are moving the same time. As already said, this is only occuring if i use the toPoint(cellMotionU) using the velocityLaplacian meshMotion solver.

    Do you need something more?
    Thanks

     
  • Bernhard Gschaider

    Sorry. The response time is a new record I'm afraid.

    Tried your case. Not with your solver but with moveDynamicMesh and this addition in controlDict

    libs (
    ŒŒŒ "libsimpleSwakFunctionObjects.so"
    ŒŒŒ "libgroovyBC.so"
    );

    functions {
    ŒŒŒ pos {
    ŒŒŒŒŒŒŒ type swakExpression;
    ŒŒŒŒŒŒŒ valueType internalField;
    ŒŒŒŒŒŒŒ accumulations (
    ŒŒŒŒŒŒŒŒŒŒŒ min max
    ŒŒŒŒŒŒŒ );
    ŒŒŒŒŒŒŒ verbose true;
    ŒŒŒŒŒŒŒ expression "pts()";
    ŒŒŒ }
    };

    The numbers seem OK and when I write out all timesteps then the grid is correctly compressed (same with your solver). Version I tried was OF 2.1.x. Which versions did you try

     
  • Bernhard Gschaider

    Ticket moved from /p/openfoam-extend/ticketsbreeder/142/

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.