-
Notifications
You must be signed in to change notification settings - Fork 46
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
Added cost details to sol #440
Conversation
Codecov Report
@@ Coverage Diff @@
## master #440 +/- ##
=======================================
Coverage 80.47% 80.48%
=======================================
Files 85 85
Lines 8985 8996 +11
=======================================
+ Hits 7231 7240 +9
- Misses 1754 1756 +2
Continue to review full report at Codecov.
|
I don't understand the purpose of "to_console"? What happens if you put False, doesn't it just print nothing (which kind of doesn't make sense)? |
Yes, if to_console=False, nothing is print to the console but the values are added to sol. This might be great if you are multi-starting and want to log the console or if you want to be able to follow what is happening in the console with a print_level very low. However, I would understand if you prefer to remove this option. |
As verbally discussed: |
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.
See previous comment
as requested
I'm on black version : |
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.
Reviewed 3 of 3 files at r2, 5 of 5 files at r3, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @EveCharbie)
README.md, line 356 at r3 (raw file):
```python sol.print_cost() # For printing their values in the console sol.detailed_cost_values_to_sol() # For adding the objectives details to sol for later manipulations
sol.compute_detailed_cost_values() (to sol is redundant)
tests/test_global_getting_started.py, line 74 at r3 (raw file):
# detailed cost values sol.detailed_cost_values_to_sol() np.testing.assert_almost_equal(sol.detailed_cost[0]['cost_value_weighted'], 41.57063948309302)
Maybe to help for future, instead of hard coding the value, you can compare it to f[0, 0] that is already valided? Like that if it ever change, we won't have to update the 2 lines for each test that changed?
I like what you have done so far, I think it is a great addition :) |
@pariterre are we good with this? |
This commit 27eeac3 |
I'm so sorry it happened again! |
@EveCharbie |
8475ca8
to
f9bbad4
Compare
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.
Reviewed 3 of 7 files at r4, 3 of 7 files at r6, 4 of 4 files at r7, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @EveCharbie)
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.
Reviewed 1 of 1 files at r8, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @EveCharbie)
This change is