Texture Vertex.num_verts_per_mesh deep copy when num_verts_per_mesh is a list #623
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
Nice work! Thank you for this pytorch3d repo which boosted my research efficiency. However, I found a potential unexpected behavior regarding
TextureVertex
. Here is my guess, proposed fixed, and a toy example.The
TexturesVertex._num_verts_per_mesh
is not correctly copied inclone()
,detach()
,join_batch()
when this property is a list. In fact, it is created as a list as in__init__
here or hereAs a result, when a list of Mehses is join_batched(), the num_verts_per_mesh in the list will be unexpectedly modified although the merged meshes is in correct shape. A toyish self-contained test is as followed:
Note the output becomes [8, 8] from [8] after join_batch(). After the fixed, the last output is [8] as expected.
create_cube
is: