diff --git a/docs/_quarto.yml b/docs/_quarto.yml index d9c23e8..ac88fe7 100644 --- a/docs/_quarto.yml +++ b/docs/_quarto.yml @@ -9,11 +9,19 @@ website: left: - reference/index.qmd - cloudstorage.qmd + - text: "Workflows" + file: workflow/main-watersystem.qmd right: - icon: github href: https://github.com/Deltares/Ribasim-NL aria-label: GitHub + sidebar: + - title: "Workflows" + contents: + - workflow/main-watersystem.qmd + - workflow/level-controlled.qmd + format: html: theme: cosmo diff --git a/docs/workflow/level-controlled.qmd b/docs/workflow/level-controlled.qmd new file mode 100644 index 0000000..e27870c --- /dev/null +++ b/docs/workflow/level-controlled.qmd @@ -0,0 +1,22 @@ +--- +title: "Level controlled" +--- + +Workflow for deriving level controlled (peilbeheerst) regional models. +All code can be found under [`src/peilbeheerst_model`](https://github.com/Deltares/Ribasim-NL/tree/main/src/peilbeheerst_model). +The paths below are relative to this path. + +1. Run the preprocessing notebooks. One notebook per water board, path: `peilbeheerst_model/preprocess_data/` +2. Run the postprocessing notebook. One notebook per water board, path: `peilbeheerst_model/postprocess_data/` +3. Run the crossings notebook. One notebook, path: `01_test_parse_crossings.ipynb` +4. Run shortest paths notebooks. One notebook per water board, path: `Shortest_path/` +5. Run crossings to Ribasim notebook. One notebook, all water boards are below each other, path: `02_crossings_to_ribasim_notebook.ipynb` +6. Run parametrize notebooks. One notebook per water board, for now only Amstel, Gooi en Vecht (AGV), path: `Parametrize/AmstelGooienVecht_parametrize.ipynb` + +We originally had more parametrize notebooks, but because so much has changed I have now saved these in our backup. +We will only use these to see if there were any additional manual adjustments. +For the rest, it follows the same workflow as `AmstelGooienVecht_parametrize.ipynb`. + +Finally: step 1 started with a clear notebook per water board. +During the process of 1.5 years, these notebooks have become increasingly larger and more confusing, whereby not every line is needed anymore. +For now, there is no priority to clean this up, partly because this is a major risk that the data will (unintentionally) change, which will change the networks and the feedback forms can no longer be used. diff --git a/docs/workflow/main-watersystem.qmd b/docs/workflow/main-watersystem.qmd new file mode 100644 index 0000000..6a87751 --- /dev/null +++ b/docs/workflow/main-watersystem.qmd @@ -0,0 +1,17 @@ +--- +title: "Main watersystem" +--- + +All files are in [`notebooks/rijkswaterstaat`](https://github.com/Deltares/Ribasim-NL/tree/main/notebooks/rijkswaterstaat) are numbered in order of execution. + +# 1_bathymetrie.py +In this script we merge data from Baseline (version j23_6-v1, non-public) with grids from [bathymetrie-Nederland](https://maps.rijkswaterstaat.nl/geoweb55/index.html?viewer=Bathymetrie_Nederland) to one 5x5m GeoTiff. + +We combine both sources as the Midden Limburgse en Noord Brabantse (MLNB) kanalen are not in Baseline and the IJsselmeer is not completely covered in bathymetrie-Nederland. +For the mask we use Top10NL waterdelen and manually filled a boolean column `baseline`. + +::: {layout-ncol=2} +![Bathymetry mask](https://s3.deltares.nl/ribasim/doc-image/ribasim-nl/bathymetrie_mask.png) + +![Bathymetry](https://s3.deltares.nl/ribasim/doc-image/ribasim-nl/bathymetrie_result.png) +::: diff --git a/src/peilbeheerst_model/Workflow_peilbeheerst_NL_LHM.txt b/src/peilbeheerst_model/Workflow_peilbeheerst_NL_LHM.txt deleted file mode 100644 index 3557561..0000000 --- a/src/peilbeheerst_model/Workflow_peilbeheerst_NL_LHM.txt +++ /dev/null @@ -1,15 +0,0 @@ -Stappenplan ontwikkelen code peilbeheerst NL: -1) Doorloop de preprocessing notebooks. Notebook per waterschap, locatie: peilbeheerst_model/peilbeheerst_model/preprocess_data -2) Doorloop de post processing notebook. Notebook per waterschap, locatie: peilbeheerst_model/peilbeheerst_model/postprocess_data -3) Doorloop de crossings notebook. Eén notebook, locatie: peilbeheerst_model/01_test_parse_crossings.ipynb -4) Doorloop shortest paths notebookS. Notebook per waterschap, locatie: peilbeheerst_model/Shortest_path -5) Doorloop crossings to Ribasim notebook. Eén notebook, alle waterschappen staan onder elkaar, locatie: peilbeheerst_model/02_crossings_to_ribasim_notebook.ipynb -6) Doorloop parametrize notebookS. Notebook per waterschap, voor nu alleen nog AGV. Locatie: peilbeheerst_model/Parametrize/AmstelGooienVecht_parametrize.ipynb - -We hadden oorspronkelijk meer parametrize notebooks, maar omdat zo veel is veranderd heb ik deze nu opgeslagen in onze back up. -Deze gaan we alleen gebruiken om te kijken of er nog extra handmatige aanpassingen waren. -Voor de rest gaat het dezelfde workflow volgens als AGV_parametrize. - -Tot slot: stap 1 begon met een overzichtelijk notebook per waterschap. Gedurende het proces van 1.5 jaar zijn deze notebooks steeds groter en onoverzichtelijker geworden, -waarbij niet elke regel meer nodig is. Voor nu ligt er geen prioriteit om dit op te schonen, mede omdat dit een groot risico dat de data (onbedoeld) wijzigt, -waardoor de netwerken zullen veranderen en de feedback formulieren niet meer gebruikt kunnen worden.