Skip to content
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

Restore correct strong branching output #1123

Merged
merged 1 commit into from
Jan 19, 2024
Merged

Conversation

rrsadykov
Copy link
Collaborator

• Restored strong branching output
• Correction for global bounds output when strong branching is used
• Output information every time an improving primal solution is found
Closes #1119

• Correction for global bounds output when strong branching is used
• Output information every time an improving primal solution is found
Copy link

codecov bot commented Jan 19, 2024

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (3db73e6) 86.32% compared to head (4630c0e) 86.51%.

Files Patch % Lines
src/ColGen/ColGen.jl 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1123      +/-   ##
==========================================
+ Coverage   86.32%   86.51%   +0.19%     
==========================================
  Files          85       85              
  Lines        7544     7556      +12     
==========================================
+ Hits         6512     6537      +25     
+ Misses       1032     1019      -13     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@rrsadykov rrsadykov merged commit d1064d8 into master Jan 19, 2024
6 checks passed
@rrsadykov rrsadykov deleted the strong_branching_print branch January 19, 2024 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Strong branching output is corrupted
1 participant