Bug with concave meshes

[cedricjeanty]

I was building out a unit test for some code using trimesh, when I encountered some strange behavior. I am loading a unit cube with a notch taken out of the origin corner like so:

The file is:
Unit Cube w Notch.STL.zip

The origin is the bottom left "corner" which is missing. When I do mesh.contains([[0.1,0.1,0.1]]) I get True, which is not expected, as this point is in the "notched" part of the cube. I get similarly incorrect results for signed_distance.

Am I misunderstanding something, or is this a bug with concave meshes?
Thanks!

[cedricjeanty]

My mistake, the coordinate system of the STL got changed during the save. This is not a bug.

[mikedh]

No worries, glad you figured it out! There is a rather unfortunate bug with contains tests and pyembree, but if you have well constructed meshes it shouldn't be a problem.