Bug fix #128
Merged
Bug fix #128
Conversation
This file contains 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
New Feature: Updated degradation estimation (with uncertainty) plus full loss factor analysis
Minor user experience improvements
Update conda version and spcqe install
…g CLARABEL (2) option to round the time shift deltas to full hours, now defaulted to True (3) record the correction implemented in hours
… the SD formulation
… solver to use CLARABEL with the iteratively reweighted problem otherwise stick with MOSEK and (2) default behavior is now to round the estimated corrections to the nearest hour
|
finally! 🎉 |
pluflou
approved these changes
Mar 21, 2024
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.
Time shift detection algorithm was not working correctly on some fairly simple examples. This bug has been fixed. Also, the default behavior has been changed to round the implemented corrections to the nearest hour.