Create a CI that runs every week / month

seareport / seareport_models

0 stars 1 forks source link

Create a CI that runs every week / month #11

Open tomsail opened 3 months ago

tomsail commented 3 months ago

This will test the capacity of the package to produce reproducible models, including the following steps:

meshing
modeling
post-processing

For that a link with the data is necessary:

for the coastlines (I am using the parquet version of GSHHS f resolution by default)
for the bathy (for now I am using ETOPO)
for the wind forcing (ERA5 as we cannot distribute ECMWF operational data)

tomsail commented 1 month ago

FESOM has a very simple (global) mesh - called pi-mesh - mainly intended for technical tests.

I think it'd be interesting to also run models using that grid too.

All meshes details are available here: https://fesom.de/models/meshessetups/ The pi-mesh is available here: https://github.com/FESOM/FESOM-data

However this obviously does not cover the meshing part.

tomsail commented 1 month ago

A few elements to go forward for setting CI/CD for models:

[ ] use the new seareport_data package to get GSHHS coastlines and update all scripts
[ ] find a way to download bathy (ETOPO, GEBCO, RTOPO) to recreate meshes
[ ] find a way to download ERA5 wind forcing

pmav99 commented 1 month ago

pi-mesh looks great. It is actually what I head in mind when I was trying to create a minimal global mesh. But they seem to have taken the correct approach. I.e. ditch all islands and greatly simplify the coastlines. Yeah we can definitely use this for tests on Azure, too.

find a way to download bathy (ETOPO, GEBCO, RTOPO) to recreate meshes I was thinking that we should put them on zenodo/seareport_data, too. We could even put some ERA5 data, too

PS. @brey This was my motivation in looking again into compression of netcdfs. I was wondering whether it is worth it to store the data compressed, what is the overhead when decompressing etc.