Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output FEISTY forcing directly #400

Closed
mnlevy1981 opened this issue Apr 11, 2022 · 1 comment
Closed

Output FEISTY forcing directly #400

mnlevy1981 opened this issue Apr 11, 2022 · 1 comment

Comments

@mnlevy1981
Copy link
Collaborator

Summary of issue

It would be great if POP and MARBL could combine to generate FEISTY forcing directly, rather than FEISTY users post-processing existing diagnostics to generate forcing file.


Details

To run FEISTY, we use the following forcing fields:

  1. Average temperature over top 150m of column
  2. Temperature at bottom of column
  3. POC flux to seafloor
  4. Total mesozooplankton biomass over top 150m of column
  5. Total mortality loss of mesozooplankton over top 150m of column

We need to add these to POP:

  1. Average temp over top 150m
  2. Temperature at bottom of column
  3. Integral of ((zoo))C over 150 m for all ((zoo)) tracers (we just want this for mesozoo)

We need to add these to MARBL:

  1. POC flux at KMT
  2. Integral of zoo_loss over top 150 m

Notes

  1. POP can already output tracer integrals over 100m (e.g. zooC_zint_100m), and MARBL can compute zoo_loss_zint_100m so for first test we can use these built-in variables (and compute average temperature over top 100m). This would still require two new POP diagnostics: TEMP_mean_100m and TEMP_bottom. We also need POC_flux_bottom in MARBL.
  2. At the end of Section 2.1 in her paper, Colleen actually uses 100m means / integrals. Do we really want 150m, or is 100m sufficient?
@mnlevy1981 mnlevy1981 linked a pull request May 10, 2022 that will close this issue
@mnlevy1981
Copy link
Collaborator Author

This was addressed in #423 but never closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant