Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Velocity Projected Timestep Calculation Modification #120

Open
srwopschall opened this issue Jan 9, 2025 · 0 comments
Open

Velocity Projected Timestep Calculation Modification #120

srwopschall opened this issue Jan 9, 2025 · 0 comments
Assignees

Comments

@srwopschall
Copy link
Collaborator

The velocity projection considers one face fixed in space (i.e. current unprojected configuration), while doing a linear velocity based projection of the other face (e.g. into it's opposing contact face friend) and then checks to see if the interpen exceeds the max allowable. This was tested on problems where one object is stationary and the other is an incoming impactor.

The issue is that when both objects are coming toward each other, the current approach may not actually trigger a tribol dt vote, but excessive interpenetration may exist.

Solution:
Consider comparing one face's projected configuration against the other faces PROJECTED configuration. This will catch the case where the next cycle's current configuration is an interpenetrated configuration that has resulted from BOTH objects opposing velocities.

@srwopschall srwopschall self-assigned this Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant