-
Notifications
You must be signed in to change notification settings - Fork 17
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
Contact 2 of 3 #198
Open
gabemorris12
wants to merge
27
commits into
lanl:main
Choose a base branch
from
gabemorris12:contact2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Contact 2 of 3 #198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Yaml input now accepts 'global' as a geometry option for the boundary conditions. This is for contact only and means that contact will be checked on all boundary patches. Additionally, there is some cleanup here as contact features will begin to be added.
Setting things up with a function pointer for the case where there is no contact, an empty function will be getting executed instead of hitting an if statement.
Additionally, the contact_test.geo was changed so that the patch ordered in outward normal. Added additional members to contact_patch_t and contact_patches_t. Getting everything set up for the bucket sorting.
All the previous sorting methods lead up to the ability to find nodes that could potentially penetrate a patch. This ability is now implemented with the contact_patches_t::find_nodes function.
Added the get_contact_point method which determines the reference coordinates of the intersection point.
…t_nodes; added unit test for get_contact_point
… del_tc instead to prevent matar array allocation
… added the corresponding unit test
Additionally, I've done a restructure of the unit test so that it can be based on the file name.
Refer to edge_cases.py
All tests are working and results are identical to the python implementation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This is the second stage PR for contact in single-node-refactor. Since the first stage PR has not been approved yet, only accept this one and delete the first PR. But it is still good for the reviewer to read that one before continuing with this one.
The first stage focused on initializing the data structure and finding the nodes in proximity to the patch. This second stage pull request focuses on the detailed contact check and constructing the contact pairs, which will then lead to the third and final stage of determining the contact force. With these added changes in the second stage, the method resolution order for the contact algorithm is this (for each time step)
As this code sits, there will need to be some modifications to optimize performance (like getting rid of the FOR_ALL_CLASS) and to ensure it runs on the GPU. There are several
// todo
statements that address these issues.If not already aware, there is a python version of the entire algorithm with a plethora of examples here. Before reviewing, take the time to watch this video:
PR.2.Recap.mp4
Type of change
Please select all relevant options
How Has This Been Tested?
For the following tests, uncomment the run_contact_tests() function in SGH::setup(). If you haven't already see the attached video above this.
Make sure that you are in the debug mode so that the assertions will register.
Test Configuration:
Checklist: