-
Notifications
You must be signed in to change notification settings - Fork 51
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
Improved error reporting for greedy solver #539
Improved error reporting for greedy solver #539
Conversation
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.
A little later I'll very much want to review / revise what we do for log messages in all of these algorithms. But for now I'm happy with printing at least fewer messages.
We should just think of whether "flood" messages, with INFO:
message lines are the things that we want to go for in the meanwhile. 🤔
static std::ostream& flood() { | ||
std::cout << "@greedy_ambiguity_resolution_algorithm: "; | ||
std::cout << "INFO: @greedy_ambiguity_resolution_algorithm: "; | ||
return std::cout; | ||
} |
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.
I'm generally not the biggest fan of all of these output messages. 🤔 But as long as we use them, why not name this as either a DEBUG
or VERBOSE
output level? To be a bit more in line with Athena / Python / etc. message logging conventions.
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.
Thanks for your review :)
I made a mistake, I meant to say FLOOD:
for "flood" messages. I completely agree with you, I think it's much better to have a common vocabulary and not confuse developers with too many different names referring to the same concept. I’ve changed FLOOD
into DEBUG
(since I only used these messages for debugging purposes). They are here to help me in case anything goes wrong and I need to debug the code, but I agree, the fewer messages we print on the terminal, the better, and there is no point in repeatedly saying "I'm doing this and that, everything works fine", better save space for the really important messages.
6a217d3
to
1b7f7c8
Compare
1b7f7c8
to
8ea55b7
Compare
8ea55b7
to
241b9c7
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.
👍
A few tings: