Lewis Blake

Pushing back at least a month until we determined desired functionality for trends.

From pyaerocom meeting: This is related to the caching. We should talk about this tomorrow at the Design Retreat. Previously we had explicitly not had caching in pyaro.

Notes from pyaerocom 28.10.24: Two requests from pyaro: 1) We want a cheap way to access the `data_revision` without reading the data. 2) We want a way to read temporal...

@magnusuMET fixed this in #1401 eliminating the use of loops and thereby speeding up the code. Close until becomes relevant again.

Pyaerocom 18.11.24: Once solution could be to make a network specific variables.ini file in `MyPyaerocom` which contains the supported variables. Then a bool could be passed saying whether to use...

This seems like a bug in GitHub's automation, not something we can control. 

Results from profiling one instance of the test:  `calc_statistics` takes only about 11% of the time whereas `load_region_mask_xr` takes about 60% of the time. A lot of this in...

> Has this test been run with a long time-series with more than one year of hourly data (8760 timesteps at least)? We don't see a bottleneck for short timeseries....

Part of the reason we compute the statistics on the flattened arrays is (used to be) because the filtering is applied at the station time series level. So we would...

Idea: pytest has a plugin called [timeout](https://pypi.org/project/pytest-timeout/). Once optimized, we can write a test to check that the code does not take more than a certain amount of time. If...