[ ] compute_expected_counts has an edgecase for months/years with only a value on the first and last timestep, derived frequency will be 15/183 days days and this will result in 2 expected counts. This causes the mean to be seen as valid, while it is not.
[ ] release
[ ] derive (now official) results for all stations and for 2011/2021
Todo not related to methods:
[ ] check warnings in pytest workflow
[ ] move to Deltares Github organization?
Reporting:
[ ] rapportage evt met Quarto: iets online via bookdown R of opvolger, een webpage of pdf. Mooie methode voor technische rapporten, kan ook met Deltares LaTeX template: https://www.testsysteemrapportage.nl/wadden/_main.pdf Of gewoon sphinx docs op github?
[ ] docstrings do/will contain the technical user information about input/output of functions and what they do
[ ] the description of the kenmerkende waarden can be in sphinx documentation (what does it represent, why this method, interaction)
[ ] additionally a pdf report with description of historic methods and motivation of improvements/simplification? Maybe including comparison of methods if still reproducible This information is not all relevant for the online documentation, since not all users will be interested in this. But it is good to document motivation for changes somewhere.
[ ] which language where?
[ ] the RWS dashboard will show the results for all stations, so here we can focus on one example station (or some)
[ ] also document which output (csv files, figures, boi timeseries) is relevant for which process (including contact person)
Todo:
compute_expected_countshas an edgecase for months/years with only a value on the first and last timestep, derived frequency will be 15/183 days days and this will result in 2 expected counts. This causes the mean to be seen as valid, while it is not.Todo not related to methods:
Reporting: