We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From @bob-carpenter
Our loggers should just take these, as in: logger.info() << "Gradient evaluation took " << ...; Or we should have a polyadic info function that could look like: logger.info("Gradient evaluation took ", deltaT, " seconds");
Our loggers should just take these, as in:
logger.info() << "Gradient evaluation took " << ...; Or we should have a polyadic info function that could look like:
logger.info("Gradient evaluation took ", deltaT, " seconds");
Our loggers were introduced as a stepping stone to getting us to a better design.
We can use this issue to discuss different designs for the loggers.
cc @sakrejda
Original comment from: #2570 (comment)
v2.17.1
The text was updated successfully, but these errors were encountered:
.str().length()
The current implementations are:
https://github.com/stan-dev/stan/blob/develop/src/stan/callbacks/logger.hpp https://github.com/stan-dev/stan/blob/develop/src/stan/callbacks/stream_logger.hpp
As used in CmdStan, the calling function instantiates a logger where debug and info messages are sent to std::cout and the rest are sent to std::cerr - https://github.com/stan-dev/cmdstan/blob/4a34c4786d30da566ded7c4ad0e16b9ec189571a/src/cmdstan/command.hpp#L289-L290
Sorry, something went wrong.
No branches or pull requests
Summary:
From @bob-carpenter
Description:
Our loggers were introduced as a stepping stone to getting us to a better design.
We can use this issue to discuss different designs for the loggers.
Additional Information:
cc @sakrejda
Original comment from: #2570 (comment)
Current Version:
v2.17.1
The text was updated successfully, but these errors were encountered: