Hi Hanbo, You are getting this error in parallel because this test case is using the option <I PROPERTY="GlobalSysSoln" VALUE="DirectMultiLevelStaticCond"/> and the direct solver only works in serial. You can run it in parallel by changing this option to IterativeStaticCond or XxtMultiLevelStaticCond. To visualize the movement, you have to use the mapping module during postprocessing, i.e. FieldConvert -m mapping CylFlow_Mov_mapping.xml CylFlow_Mov_mapping.fld cyl.vtu This way the vtu file will have additional fields xCoord and yCoord containing the x and y deformed coordinates. If you are using paraview, you can then create a Calculator with the expression "xCoord*iHat + yCoord*jHat + coordsZ*kHat" and activate the "Coordinate results" option to visualize the deformed geometry. Cheers, Douglas 2018-01-31 8:37 GMT-02:00 Hanbo JIANG <hjiangan@connect.ust.hk>:
Dear all,
I am a new user. When I tried the VCSMapping with test case (nektar/solvers/ IncNavierStokesSolver/Tests/CylFlow_Mov_mapping.xml) it failed to run in parallel with errors: " mpirun -np 8 IncNavierStokesSolver CylFlow_Mov_mapping.xml
Fatal : Level 0 assertion violation A parallel solver must be used when run in parallel. "
I had to run it in serial to get the final result. However the mesh grid and the position of cylinder remain the same as initial field, even if I have tried different "NumSteps".
I just followed the user guide and used
"FieldConvert CylFlow_Mov_mapping.xml CylFlow_Mov_mapping.fld cyl.vtu"
to get the converted result.
I guess maybe because 'CylFlow_Mov_mapping.xml' only contains initial mesh data and CylFlow_Mov_mapping.fld only contains field data, i.e., deformed mesh information is missed by this command. so I think this problem is about post-processing.
Could you please help to find out what I've missed and fix this problem? I would appreciate your Help.
Kind regards, Hanbo
_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users