You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cf.regrid_logging flag can turn the logging from ESMF regridding on and off as required under cf, but I think it would be cleaner and more natural to the user if it such logging was controlled under the cf logging system.
More specifically I propose that ESMF logging is switched on when the cf.log_level is set to 'INFO' (2) or higher, otherwise off, and perhaps we can, consistently with other functions, provide a verbose keyword argument to the two regridding methods which can override the global log level if a user does want to force the ESMF logging to be enabled. Then we can remove this flag.
Happy to consider other thoughts on this, though, if anyone thinks the current set-up is preferable or there is a better alternative way to manage the configuration of the ESMF logging.
The text was updated successfully, but these errors were encountered:
sadielbartholomew
changed the title
Integrate logging systems
Subsume ESMF regrid logging config. under log level
Dec 14, 2021
sadielbartholomew
changed the title
Subsume ESMF regrid logging config. under log level
Subsume ESMF regrid logging configuration under log level
Dec 14, 2021
The
cf.regrid_logging
flag can turn the logging from ESMF regridding on and off as required undercf
, but I think it would be cleaner and more natural to the user if it such logging was controlled under thecf
logging system.More specifically I propose that ESMF logging is switched on when the
cf.log_level
is set to 'INFO' (2
) or higher, otherwise off, and perhaps we can, consistently with other functions, provide averbose
keyword argument to the two regridding methods which can override the global log level if a user does want to force the ESMF logging to be enabled. Then we can remove this flag.Happy to consider other thoughts on this, though, if anyone thinks the current set-up is preferable or there is a better alternative way to manage the configuration of the ESMF logging.
The text was updated successfully, but these errors were encountered: