Open Peter9192 opened 1 year ago
~related: https://github.com/SciTools/iris/issues/3413~
never mind, happens for esmvalcore's own messages as well
On closer inspection, the problem applies to esmvalcore's own messages as well:
from esmvalcore.dataset import Dataset
dataset = Dataset(
short_name='tos',
mip='Omon',
project='CMIP6',
exp= 'historical',
dataset='IPSL-CM6A-LR',
ensemble='r4i1p1f1',
grid='gn',
)
dataset.add_supplementary(short_name='areacello', mip='Ofx', exp='historical')
dataset.augment_facets()
cube = dataset.load()
WARNING:esmvalcore.cmor.check:There were warnings in variable areacello:
Long name for areacello changed from Grid-Cell Area to Grid-Cell Area for Ocean Variables
loaded from file /home/peter/climate_data/CMIP6/CMIP/IPSL/IPSL-CM6A-LR/historical/r4i1p1f1/Ofx/areacello/gn/v20180803/areacello_Ofx_IPSL-CM6A-LR_historical_r4i1p1f1_gn.nc
again, log_level
has been set to error
(not interactively, but already in config-user.yaml`)
When using esmvalcore through the API in a jupyter notebook, iris warnings show up in the output despite setting
log-level
toerror
in config-user. For example:spits
Another one I keep getting is
The amount and non-prosaic nature of these messages very much clutter my notebooks, to the extent that I'd prefer to suppress them. I had expected that the user configuration setting
log_level
would apply to iris' messages as well, but apparently, it does not.