2024-05-13 Pyaerocom Meeting

[jgriesfeller]

Last meeting

• 2024-05-06 Pyaerocom Meeting #1155

Next milestone: m2024-06

EMEP workshop

• EMEP configs prepared
• tutorials all updated and clear
• what to do with EBAS this summer (Can we get preliminary dataset for 2022)?
• Has somebody ordered snacks/fruit as we had for the NORESM workshop?

current status is unknown since @dulte is not around. Should be solved tomorrow.

PRs

• code to make the cams2_83 mos evaluation work #1166
• O3 mda8 #1165
• Add test with oldest dependencies to CI #1154
• Custom variables when running aeroval #1147
• Custom statistics #1138
• Fix obs climatology #1135
• pyaro-readers: PR 31: Nilupmf

Other issues

• pyaro-readers: issue 39: all readers should provide a revision string

AOB

• How to implement the glue between pyaerocom variables and pyaro variables?
  The existing glue between pyaerocom and pyaro works if there's a 1:1 relationship between the pyaerocom and pyaro variable. But for EBAS that's rather a 1:n relationship meaning that at pyaerocom wants to try several variables and wants to choose the right one depending on what's available or some additional meta data.
  The question is how to implement that? Possibilities are
  • like the existing readers in pyaerocom,
  • additional pyaro based layer in pyaro-readers or e.g seperate project (pyaro-interface). In this case the input and the output is pyaro but as pyaerocom variable
  • in the existing reader in pyro-readers

conclusion: do in pyaro