Create a monthly report (web page) with forecasts and validation/stats

[scotthosking]

I would like us to automate the creating of a monthly icenet report (web page), looking forward to the next 3 months and a validation over the previous 3 months.

We can also produce running statistics on how accurate IceNet is, and whether there are any anomalous events coming up

• Produce pipeline action to cover the following steps:
  • Run the existing "production" forecast (this is currently done automatically via run_era5_forecast so don't duplicate if that forecast exists already)
  • Ensure a forecast exists for t - 93 days
  • Download the SEAS data for model comparison
  • Run produce_op_assets for both forecasts if the assets aren't already present. This will plot against SEAS if available, from memory, but needs testing
• Decide whether to either...
  • ...produce a little static HTML report in the pipeline, or...
  • ...integrate the assets with the icenet-application dashboard, which is designed for this purpose...
  • Both of the ideas above require some deliberation, as the latter involves cloud hosting and the plotting can get quite involved - but it's a cleaner extension to the methodology in place. Discuss with @JimCircadian
• @JimCircadian extend / plan incorporation for multi-temporal forecasting

[JimCircadian]

@scotthosking Moving this into icenet-project, as we actually have this infrastructure and it spans multiple repositories. Will be better captured there so that we can produce the required stats / plots under icenet-application and in the icenet-etl repositories as well.

[JimCircadian]

Links to #49 so that we can report on different timescales.

[JimCircadian]

@scotthosking updated the steps to implementation, can you provide a little feedback on whether you have any preferences, or are you happy for us to stitch this together using the numerous assets we have at our disposal for the daily forecasting?

I'll address the monthly / seasonal forecasting incorporation in due course, working on that in parallel

@bnubald once we get an OK from Scott that the above covers his requirements, are you keen to pick up initial implementation via the pipeline?

[bnubald]

@scotthosking updated the steps to implementation, can you provide a little feedback on whether you have any preferences, or are you happy for us to stitch this together using the numerous assets we have at our disposal for the daily forecasting?

I'll address the monthly / seasonal forecasting incorporation in due course, working on that in parallel

@bnubald once we get an OK from Scott that the above covers his requirements, are you keen to pick up initial implementation via the pipeline?

Yes, happy to.

[scotthosking]

Sorry @bnubald - just saw these messages here, they get lost in my inbox so feel free to nudge me on Slack in the future and I can then reply here

[bnubald]

To discuss:

• SEAS access
• Discuss integration into icenet-application +- cloud hosting pros/cons. Ideal preference would be to integrate within icenet-application rather than another implementation.