-
Notifications
You must be signed in to change notification settings - Fork 85
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
refactor: Use TensorViewer in SciPy optimizer, instead of explicit constraints #970
Conversation
aaf68a4
to
2885764
Compare
Codecov Report
@@ Coverage Diff @@
## master #970 +/- ##
==========================================
+ Coverage 96.48% 96.50% +0.02%
==========================================
Files 57 57
Lines 3217 3236 +19
Branches 441 442 +1
==========================================
+ Hits 3104 3123 +19
Misses 72 72
Partials 41 41
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looking very nice, and I appreciate the work that factoring this out took. Just have a few questions and then we need @lukasheinrich's review.
Closing in favor of #951 which is preserving all of the functionality instead of removing the option to not-stitch entirely. |
Pull Request Description
Part of pulling out/refactoring #951. We need to split out the portion of rewriting scipy to use TensorViewer first, so we know the changes in the tests, before doing a larger refactor.
Checklist Before Requesting Reviewer
Before Merging
For the PR Assignees: