Mfem: FindPointsGSLIB does not return right element indices for tets

Created on 26 May 2020  路  3Comments  路  Source: mfem/mfem

I was recently working on a side project that makes use of linear tets where I needed to find what elements a set of points belonged within. I first made use of FindPointsGSLIB and found that a few of the elements were outside of the range for how many the mesh contained. I have a feeling this might be due to the fact that the tet mesh is converted over to a hex mesh, and then later on the element numbers aren't mapped back to the original elements.

I found that Mesh::FindPoints does work for my needs but is significantly slower.

I've included what should be a minimal working example that should reproduce the problem.

min_ex.zip

bug mesh

All 3 comments

Yes, the current version of the master does not return the right element number for simplices because of conversion to a quad/hex mesh. I am working on an update to FindPointsGSLIB where I have added this functionality of mapping the element number for simplices (here). Note that this function also maps the reference space coordinates from [-1, 1] (output by GSLIB) to [0, 1] (for MFEM).

@kmittal2 thanks for the quick feedback. I look forward to seeing this update brought into master :)

@rcarson3 I am closing this issue for now but feel free to reopen it if you have any further questions.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

termi-official picture termi-official  路  4Comments

anjirom picture anjirom  路  3Comments

sshiraiwa picture sshiraiwa  路  4Comments

latug0 picture latug0  路  4Comments

tuckerbabcock picture tuckerbabcock  路  4Comments