Fix start_edge and end_edge node extraction across multiple edge groups#131
Open
ManavSharma23 wants to merge 1 commit intoMonashSmartStructures:mainfrom
Open
Fix start_edge and end_edge node extraction across multiple edge groups#131ManavSharma23 wants to merge 1 commit intoMonashSmartStructures:mainfrom
ManavSharma23 wants to merge 1 commit intoMonashSmartStructures:mainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Fixes incorrect node extraction for
start_edgeandend_edgewhen multiple edge groups exist.Problem
Previously, only a single edge group was considered, which caused missing start/end nodes in models with multiple edge groups.
Solution
This change aggregates elements from all valid edge groups and extracts unique boundary nodes, ensuring correct girder identification downstream.