Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M MEDUSA_4.2.x
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • acc
  • MEDUSA_4.2.x
  • Wiki
  • MEDUSA DOCU : Rivers

MEDUSA DOCU : Rivers · Changes

Page history
Update MEDUSA DOCU : Rivers authored Nov 22, 2024 by julpal's avatar julpal
Hide whitespace changes
Inline Side-by-side
Showing with 23 additions and 3 deletions
+23 -3
  • MEDUSA-DOCU-:-Rivers.md MEDUSA-DOCU-:-Rivers.md +23 -3
  • No files found.
MEDUSA-DOCU-:-Rivers.md
View page @ 1bd64453
...@@ -103,6 +103,26 @@ first runs did not work because of something in the newly made river input files ...@@ -103,6 +103,26 @@ first runs did not work because of something in the newly made river input files
With river, the total production in 1986 is of 31 Pg-C per y still too low for our liking. this will need some tweaking. With river, the total production in 1986 is of 31 Pg-C per y still too low for our liking. this will need some tweaking.
* Trying to Understand why it is failing there, in the Chinese sea... * Trying to Understand why it is failing there, in the Chinese sea...
* I've tried 1 run with all Andrew's new LS200 files (let's call it `LS200`) * I've tried 1 run with all Andrew's new LS200 files (let's call it `LS200`)
* and also 1run where i've switched `DIC` and `ALK` to the widerly spreaded LS400 (so let's call it `LS400`). * and also 1run where i've switched `DIC` and `ALK` to the widerly spreaded LS400 (so let's call it `LS400`).
Both failed. `LS400` few days later though. Both failed. `LS400` few days later though.
An interesting point is that the model ran with no river nutrients, in both advection scheme. What means that something in the river induces the crash.
\ No newline at end of file The DIC field in the `no_river` run (fct advection) looks like this :
<img src="uploads/681ad9fee40424c0bf4401cb1a9d81e4/image.png" width=49%>
The difference with here is the diff with respectively `LS200` and `LS400` bellow.
<img src="uploads/5a6d4c51dd7da71bf1d6e443cfac97de/image.png" width=49%>
<img src="uploads/5ffeab748e149f99aeb8942cf20a7dbd/image.png" width=49%>
<img src="uploads/0583ccd90f5e2fb294626a0adc958ddc/image.png" width=49%>
<img src="uploads/b4ace1fc3265be5248ea5b1050d2aec2/image.png" width=49%>
The difference decrease in `LS400`, but the interesting bit here, is that we loose DIC compare to the `no-river` run, although we add the river nutrients...
Looking at the river, we might understand what's going on :
Here `LS200`:
<img src="uploads/21b7054deefbdae89b3eaf6395662829/image.png" width=49%>
<img src="uploads/d627423cc33edc7804850527fdaa68de/image.png" width=49%>
The problem seems to come from the mismatch between DIN and DIC riverine inputs. PP is boosted by the N supply, where no DIC is added and where fresh water arrives. DIC is driven down by the PP, and probably bellow 0.0 because of the fresh water and advection.
I am doing another test with add mixing at river mouth down to 20m instead of 10, but best might be to make sure both DIN and DIC river input match.
\ No newline at end of file
Clone repository
  • Compile MEDUSA from scratch
  • Developing on MEDUSA git Best practice
  • How to SETTE test MEDUSA.
  • How to run MEDUSA 1D on ARCHER2 and ANEMONE
  • How to run on ANEMONE
  • How to run on ARCHER2
  • MEDUSA DOCU : Chl light
  • MEDUSA DOCU : Rivers
  • MEDUSA Guide some useful explanations
  • MEDUSA NEMO4.2
  • MEDUSA Training How to run MEDUSA 1D ( on NOC linux system)
  • Home
  • todo_list