FieldConvert interpfield odd behaviour
Hello everyone, I'm using the FieldConvert interpfield function to interpolate a simple inviscid flow around a Joukowski airfoil onto a new mesh. While for the most part the result seems to be smooth and correct when visualizing the field in paraview, there are a few odd isolated cells wherein the interpolated values in the new mesh are completely off. The files to reproduce this behaviour are too big to share here, but I'm sending a screenshot to illustrate this. I'm using Nektar++ 4.4.1 and performing the computation in parallel. Any help understanding this would be much appreciated. Cheers, Henrique
Dear all, When starting IncNavierStokesSolver with version 4.4.1 I got the message: Fatal : Level 0 assertion violation Unable to find composite 3 in order map. Composite 3 is defined in geometry domain and appears under BOUNDARYREGIONS <C ID="3"> E[1269,1272,1274,1276,1278,....,7011] </C> <BOUNDARYREGIONS> <B ID="0"> C[1] </B> //inflow <B ID="1"> C[2] </B> //outflow <B ID="2"> C[3] </B> //walls </BOUNDARYREGIONS> The mesh looks fine at the mentioned boundary. Any help would be much appreciated! Kind regards, Albert Baars
Hi Henrique, If you put the mesh on are these points at the vertices of the cells? It is not easy to see from this image. Have you also tried 4.5.0? Cheers, Spencer. On 13 Mar 2019, at 19:03, Raposo, Henrique T <h.raposo17@imperial.ac.uk<mailto:h.raposo17@imperial.ac.uk>> wrote: Hello everyone, I'm using the FieldConvert interpfield function to interpolate a simple inviscid flow around a Joukowski airfoil onto a new mesh. While for the most part the result seems to be smooth and correct when visualizing the field in paraview, there are a few odd isolated cells wherein the interpolated values in the new mesh are completely off. The files to reproduce this behaviour are too big to share here, but I'm sending a screenshot to illustrate this. I'm using Nektar++ 4.4.1 and performing the computation in parallel. Any help understanding this would be much appreciated. Cheers, Henrique <Screenshot from 2019-03-13 13-20-52.png>_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk<mailto:Nektar-users@imperial.ac.uk> https://mailman.ic.ac.uk/mailman/listinfo/nektar-users Spencer Sherwin FREng, FRAeS Head, Aerodynamics, Director of Research Computing Service, Professor of Computational Fluid Mechanics, Department of Aeronautics, s.sherwin@imperial.ac.uk<mailto:s.sherwin@imperial.ac.uk> South Kensington Campus, Phone: +44 (0)20 7594 5052 Imperial College London, Fax: +44 (0)20 7594 1974 London, SW7 2AZ, UK http://www.imperial.ac.uk/people/s.sherwin/
Hi Spencer and Henrique, We have used "FieldConvert -m interpfield" module to interpolate a field to another mesh by using Nektar++4.4.1, and seems have the similar problem. We found that this problem wouldn't happen in the previous module "fieldtofield". The problem was solved after we deleted <CURVED> .... </CURVED> section in those two *.xml files. Probably because of the high-order mesh we used so that the interpfield module cannot find the proper vertices from one mesh to the another? The interpolate results look good but I'm not really sure if this step OK for further simulation. The screenshots are attached for your reference. Kind regards, Chengjiao ===================================== 任珵娇；Cheng-Jiao Ren， 博士研究生；Ph.D Candidate， 建设工程学部；Faculty of Infrastructure Engineering， 大连理工大学； Dalian University of Technology， 大连，中国 116024；Dalian，CHINA 116024. 电话，Phone：86-18504285808， 电子邮箱，Email：dlut_renchengjiao@163.com . ===================================== On 3/18/2019 02:58，Sherwin, Spencer J<s.sherwin@imperial.ac.uk> wrote： Hi Henrique, If you put the mesh on are these points at the vertices of the cells? It is not easy to see from this image. Have you also tried 4.5.0? Cheers, Spencer. On 13 Mar 2019, at 19:03, Raposo, Henrique T <h.raposo17@imperial.ac.uk> wrote: Hello everyone, I'm using the FieldConvert interpfield function to interpolate a simple inviscid flow around a Joukowski airfoil onto a new mesh. While for the most part the result seems to be smooth and correct when visualizing the field in paraview, there are a few odd isolated cells wherein the interpolated values in the new mesh are completely off. The files to reproduce this behaviour are too big to share here, but I'm sending a screenshot to illustrate this. I'm using Nektar++ 4.4.1 and performing the computation in parallel. Any help understanding this would be much appreciated. Cheers, Henrique <Screenshot from 2019-03-13 13-20-52.png>_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users Spencer Sherwin FREng, FRAeS Head, Aerodynamics, Director of Research Computing Service, Professor of Computational Fluid Mechanics, Department of Aeronautics, s.sherwin@imperial.ac.uk South Kensington Campus, Phone: +44 (0)20 7594 5052 Imperial College London, Fax: +44 (0)20 7594 1974 London, SW7 2AZ, UK http://www.imperial.ac.uk/people/s.sherwin/
participants (4)
-
Albert Baars
-
chengjiaoren
-
Raposo, Henrique T
-
Sherwin, Spencer J