| Leibniz Institute for Baltic Sea
Research Warnemünde Physical Oceanography and Instrumentation Seestrasse 15 18119 Rostock Germany |
Hi Ulf,
Yes that’s one topic where we should add a wiki page about (models built into FABM for common functionality). Anyway, the idea is to add a “surface flux” model like so (under instances):
tracer_flux:
model: external_surface_flux
coupling :
target : tracer/c
That will leave you with a dependency for the surface flux (in tracer/m2/s), named tracer_flux/flux (or tracer_flux/flux). Typically you would then provide that 2D field through the host, i.e., GETM.
Scanning the GETM code, it looks like you should then provide a NetCDF file with that variable. The path to the file is configured through fabm_surface_flux_file in getm_fabm_nml. The variable must be named “tracer_flux” in your case. But as far as I can tell, the current GETM code only allows that field to be a monthly climatology…
Cheers,
Jorn
--
You received this message because you are subscribed to the Google Groups "FABM-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabm-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fabm-users/d94e3f18-7706-e712-f997-13dfcb6c7444%40io-warnemuende.de.
Addendum: that dependency for the surface flux would be named tracer_flux/flux or tracer_flux_flux. It is accessible by the host under both names. GETM uses the latter.
J
To view this discussion on the web visit https://groups.google.com/d/msgid/fabm-users/010201d63ff1%243939dd10%24abad9730%24%40bolding-bruggeman.com.