change precision EPSILON in C code#217
Merged
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #217 +/- ##
==========================================
+ Coverage 88.48% 92.40% +3.92%
==========================================
Files 20 16 -4
Lines 3196 3056 -140
==========================================
- Hits 2828 2824 -4
+ Misses 368 232 -136 |
agramfort
reviewed
Nov 12, 2020
rflamary
reviewed
Nov 12, 2020
Collaborator
Author
|
Finally I only changed the final test value against EPSILON to test wether the problem is infeasible or not. It drastically limitates the side effects in the resolution of the problem. |
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.
Types of changes
Motivation and context / Related issue
Problem INFEASIBLE cast where it should not happen.
Fixes #126
Fixes #93
How has this been tested (if it applies)
The minimal code to repdroduce the bug is now working.
A user tested on its own data and now the problem is also working
Checklist