Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Project: MARBL Configuration - Plankton Time!

This project is about setting up a MARBL configuration and any nuances we might want to consider.

Download this project by either:

  1. Running the CrocoDash CLI command: crocodash template --output marbl_case.ipynb --machine glade --notebook crocodash.projects.marbl, then filling in the paths it leaves as placeholders

  2. Copying the file from your CrocoDash checkout: gallery/crocodash/projects/marbl.ipynb

Grid Generation

MARBL is integrated into MOM6, so it’s pretty straightforward to set up. Since there are so many tracers, MARBL’s initial and boundary conditions come from a previous CESM run, which carries all of them.

Since MARBL adds cost, we will pick a small domain. Let’s rip through the first steps!

MARBL Forcing

We use a global MARBL file to set up the initial condition (It is regridded as part of the model run). We generate MARBL OBCs in the same exact way as the MOM6 OBC (we’re just adding >40 more tracers).

We need to provide the path to a MARBL run or have it default to a run to generate MARBL OBCs. What we’re going to use below defaults to a FIESTY run (https://www.sciencedirect.com/science/article/abs/pii/S0079661124001204). We do not support having separate physical vs MARBL forcings. All the forcings come from one product, which in this case is CESM POP Output, the old CESM ocean model.

I’d mess with the NTASKS/ROOTPEs (give more ocean PEs) and build & submit!

Feel free to iterate with process forcings! You can run it on the command line with crocodash process --caseroot YOURCASEROOT --all (or name just the pieces you changed, e.g. --bc, --cice; see crocodash process -h)!