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 diurnal cycle analysis has just been accidentially removed from main-dev during a bigger than ususal PR. This slipped throuigh testing because there is no test for it.
Because it's a rarely used feature but also a feature that is important when it's needed, we should have a test if it's still working in CI.
Needs hourly model and obs data (example vmrno2 from EBAS and EMEP data from here: /lustre/storeB/project/fou/kl/CAMS2_40/task4041/EMEP.cams2.40.p2/
The model data needs to be much coarser to be small enough for CI
aeroval option to set: use_diurnal=True
The text was updated successfully, but these errors were encountered:
One idea is that if it is too big in memory due to hourly data would be to test that this code exists. We could ping it, and mark the test as expecting to fail for no data (or something else)
General comment: It could be worth thinking about having (at least) two types of tests: unit tests, and and tests which take more time and should be run locally (not on CI) at the frequency closer to the release schedule, not necessarily during PRs. Would be useful for this at PM ratio tests.
the diurnal cycle analysis has just been accidentially removed from main-dev during a bigger than ususal PR. This slipped throuigh testing because there is no test for it.
Because it's a rarely used feature but also a feature that is important when it's needed, we should have a test if it's still working in CI.
Needs hourly model and obs data (example
vmrno2
fromEBAS
and EMEP data from here:/lustre/storeB/project/fou/kl/CAMS2_40/task4041/EMEP.cams2.40.p2/
The model data needs to be much coarser to be small enough for CI
aeroval option to set:
use_diurnal=True
The text was updated successfully, but these errors were encountered: