Currently the report has rule-based validations that run on all the data and forecast-based validations that run on a single day. One remedy for this would be to store the forecasts as a data set (e.g. with arrow and parquet files) each day. Then, build the report once a week with a week's worth of data in the validations (both rule and forecast based). These reports could be saved as separate quarto documents and could be accessible through a simple quarto website with links to previous reports.
Currently the report has rule-based validations that run on all the data and forecast-based validations that run on a single day. One remedy for this would be to store the forecasts as a data set (e.g. with arrow and parquet files) each day. Then, build the report once a week with a week's worth of data in the validations (both rule and forecast based). These reports could be saved as separate quarto documents and could be accessible through a simple quarto website with links to previous reports.
An alternative to #23.