Refactor JointRule process to accomodate PlateJoint - #479
Merged
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #479 +/- ##
==========================================
+ Coverage 65.46% 65.97% +0.51%
==========================================
Files 76 76
Lines 11027 11064 +37
==========================================
+ Hits 7219 7300 +81
+ Misses 3808 3764 -44 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This was
linked to
issues
Jul 11, 2025
Closed
This was
unlinked from
issues
Jul 11, 2025
Closed
Contributor
Author
|
@papachap @chenkasirer @Stryzhevska Howdy! I do believe this is ready for a lookyloo! thanks!! |
papachap
reviewed
Aug 19, 2025
chenkasirer
reviewed
Aug 19, 2025
obucklin
commented
Aug 25, 2025
Contributor
|
@obucklin could you please sort out the merge conflicts so that we see the build runs? |
Contributor
Author
|
hey @chenkasirer this is getting an error regarding the ipy checks that doesn't make any sense to me. Otherwise it's ready for another look. |
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
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.
So I wanted to make GH components for the new PlateJoints. This required a rework of the JointRules themselves.
Changes to JointRule application:
I reworked the
comply()methods, and realized we had a lot of redundant checks in the process. I tried to rationalize the rule parsing and joint creation a bit.new workflow:
JointRulecreation. No distance, topology, or other compliance checks are done here.Jointcreation viaJointRule.try_create_joint. This is where all checks are done.DirectRule.try_create_jointraises aBeamJoiningErrorif it fails, but the others take a pair of elements and return a Joint if possible, otherwiseNone.I removed
JointDefinitionandFeatureDefinition.There are 2 other PRs now upon which this depends: #500 and #501. once they are merged we can look at this.
What type of change is this?
Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.CHANGELOG.mdfile in theUnreleasedsection under the most fitting heading (e.g.Added,Changed,Removed).invoke test).invoke lint).compas_timber.datastructures.Beam.