You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix buildPatchContactMapping to compare normalized (min,max) pairs
The function now compares (min(A,B), max(A,B)) instead of (A,B) directly
to correctly match the same physical contact across timesteps regardless
of ID ordering. This fixes the issue where contacts were incorrectly
mapped to the first patch contact when IDs were in different order.
Co-authored-by: Ruochun <24469442+Ruochun@users.noreply.github.com>
0 commit comments