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
Refer to the log output in this issue: #228 (comment)
No response
Latest e3sm_to_cmip
The text was updated successfully, but these errors were encountered:
Regarding duplicate messages, this web-post may address the issue:
https://stackoverflow.com/questions/67269916/how-to-avoid-root-handler-being-called-from-the-custom-logger-in-python
Sorry, something went wrong.
@TonyB9000 Thanks Tony! I would like to address this soon in e3sm_to_cmip and e3sm_diags, as I'm sure it annoys everyone including me.
e3sm_to_cmip
e3sm_diags
@tomvothecoder A minor, related annoyance: Even just issuing e3sm_to_cmip --help results in a "logs" directory created.
e3sm_to_cmip --help
Also, with info-mode, the stderr logging says "output will be written to (numeric-filename).log", but never is such a log created.
(Separate issues, I know...)
No branches or pull requests
What happened?
Refer to the log output in this issue: #228 (comment)
What did you expect to happen? Are there are possible answers you came across?
No response
Minimal Complete Verifiable Example (MVCE)
No response
Relevant log output
No response
Anything else we need to know?
No response
Environment
Latest e3sm_to_cmip
The text was updated successfully, but these errors were encountered: