-
Notifications
You must be signed in to change notification settings - Fork 157
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
fix: non finite weight handling in GSF #1591
fix: non finite weight handling in GSF #1591
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1591 +/- ##
==========================================
- Coverage 48.54% 48.54% -0.01%
==========================================
Files 381 381
Lines 20782 20785 +3
Branches 9534 9536 +2
==========================================
+ Hits 10089 10090 +1
Misses 4112 4112
- Partials 6581 6583 +2
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Co-authored-by: Alexander J. Pfleger <70842573+AJPfleger@users.noreply.github.com>
@AJPfleger I found some other issues related to non finite weights, so I thought that could also be included in this PR to limit the number of PRs. Could you have a look again and reapprove is everything is fine? Thanks! |
Co-authored-by: Alexander J. Pfleger <70842573+AJPfleger@users.noreply.github.com>
This fixes an error where a
throw_assert
checking if all components weight sums up to 1 could trigger when all components have statusmissed
w.r.t. the next navigation surface. Requires a bit of rearrangement to check this beforehand.