InterpFromMeshToMesh2d bug

philipp.griewank

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

mathieumorlighem

Hi Philipp,

thanks for reporting the bug and providing the file. This was indeed a bug that we had never noticed because we never do P0 interpolation. Some of the points of bug.x2,bug.y2 lie on the boundary of the mesh, and bamg has to make a decision (whether they are inside the mesh or outside). For one point, bamg decided that it was outside, and there is no possible interpolation for P0 field so it did not know what to do. Now it will return NaN.

Please update the code, you will need to treat the NaN manually after the interpolation I am afraid (using griddata with a nearest neighbor interpolation for example).

I hope all is well in Bergen!

Best

Mathieu

philipp.griewank

Hello Mathieu,

thank you for the quick fix! I updated ISSM and I get a NAN instead just as you predicted. Now that I know where the issue comes from I can easily avoid it.

Things are going well in Bergen. BAMG with ISSM has been functioning so well, that we have plenty of time to focus on all the other bugs and issues we have.

Cheers,

Philipp