Open hildefagerli opened 1 year ago
This issue is stale because it has been open for 365 days with no activity. This issue will be closed in 14 days if no action is taken.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Why close issues that are not solved? This is still a problem, and somewhere the problems should be documentary and solved one by one. Hilde
On Thu, Feb 1, 2024 at 2:45 AM github-actions[bot] @.***> wrote:
Closed #812 https://github.com/metno/pyaerocom/issues/812 as completed.
— Reply to this email directly, view it on GitHub https://github.com/metno/pyaerocom/issues/812#event-11663395917, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFNP6OKZHQF5HU7WUNSJ4T3YRLXR7AVCNFSM6AAAAAAT2MV2HKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGY3DGMZZGU4TCNY . You are receiving this because you authored the thread.Message ID: @.***>
--
Hilde Fagerli Tel: +47 92 02 65 97
The issue was closed after 14 days of inactivity after being marked as stale. If it is still a problem, then coming to the issue, making a comment and removing the stale tag prevents it from being closed automatically. Since nothing was done in this case, the issue was closed by GitHub Actions. I will reopen it but please keep this in mind for future issues.
E.g. for Birkenes 2021 there are 3 sets of precipitation (daily, weekly). Some set belongs to HM/POP sampling and shouldnt be used (can see that on the instrument type I think). I think we only sort on component (precipitation_amount) and take the most recent data set, but we should think about including other options.