Hi Ismael, Sorry that this email seems to have been left unanswered. I am not sure I have a resolution for you on this, asides from noting that I think your approach is certainly valid, but perhaps this can spur someone else into answering your question. It certainly looks like either random or spurious values are being put into the field at the boundary. I suspect mesh2 might not be an exact subset of mesh1 and perhaps this is causing our reverse lookup (i.e. from points (x,y,z) to elements and their local coordinates) to fail/converge incorrectly. How big are the meshes? Can you share them with us? Cheers, Dave
On 28 Jun 2017, at 17:32, Ismael El Houas Ghouddana <ismael.elhouas@gmail.com> wrote:
Dear Nektar development team,
I am writing to you in order to communicate some issues which I have experimented,while performing a mesh interpolation with FieldConvert module.
I am originally working with a specific mesh, Mesh1, with which I have obtained some results, chk1. Now, I want to redefine this mesh and make it more detailed,
so I generated a new mesh, Mesh2, which has the same dimensions and geometry as mesh1, but it is better meshed (more elements).
Then, the problem appears when I want to interpolate the solution chk1 to the new mesh, Mesh2. In order to perform this interpolation, I have used the "interpfield" module from FieldConvert. The output file from this operation, file2.fld, is not correct at all, as some incoherent velocities have appeared. Specifically, it appeared extremely high velocities which have no reason to be. In more detail, those velocities are located at some nodes along the boundary of the domain of the solution file2.fld. These high speeds have propagated and blurred a few elements into the domain. The geometry of this boundary is a circumference arc, and its boundary conditions are HOutflow.
I also have tried to smooth the file2.fld by using the C0Projection module, file2_C0.fld, but has blurred the velocities only a few.
I have attatched some photos from file2_C0.fld showing some of those high velocities on the boundary. Must be noted that file2.fld is quite similar to file2_C0.fld,
but less blurred.
I remain at your disposal for any doubt or clarification,
Ismael El Houas
<Boundary.png><Boundary-Mesh.png>_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users