-
Notifications
You must be signed in to change notification settings - Fork 0
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
add some basic logging #70
Comments
FYI... there is this https://github.com/RMI-PACTA/pacta.portfolio.analysis/blob/main/R/write_log.R which we have used in the past to not flood stdout with messages making it difficult to parse, but still get important messages in the error log. It's not widely used though, tbh. |
Hmmm. We should maybe consider how we treat logging. But yes, that is useful. I agree with not flooding STDOut, although I think some basic indication of what is going on could be helpful |
We also have a few
but I'm not sure either will really help with what you're talking about, because they only work when there is not a problem. Errors do get sent to stdout though. |
relevant discussion here https://github.com/RMI-PACTA/pacta.portfolio.analysis/issues/235 |
used a wrong variable name, and got an error that variable did not exist
similar to
pacta.data.preparation
, so that we know what is going on, and where things are failing etc.The text was updated successfully, but these errors were encountered: