Replies: 2 comments
|
Hi @nanophyto, That all sounds like a good plan. For the light I think we could straightforwardly make a function like We could definitely do with documentation of the new structure. For the ratios you can import the carbon_ratio etc functions and add methods for other planktons. I'm going to be working on MARBL and want to keep everything as generic as possible and keeping everything interoperable, and this will definitely be helpful there too. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
This is related to @BWBlack's 'FrankenLOBSTER' model, which I am hoping to turn into something more generic on the Agate.jl side:
Thus more broadly, this would be about extending LOBSTER/NutrientsPlanktonDetritus to accept arbitrary externally-owned plankton tracers without OceanBioME needing to know the structure of the external community.
It would require two PRs (currently in prep):
a more generic 2-band light function that does not assume a single phytoplankton tracer named P
a LOBSTER/NutrientsPlanktonDetritus refactor which includes:
Maybe this will make sense once the PRs are ready, but I figured this could be a good starting point and perhaps @BWBlack can also weight in.
Hopefully this is also useful for OceanBioME beyond the Agate use case, since it would remove a few assumptions about plankton structure/naming and make the LOBSTER/NutrientsPlanktonDetritus interfaces a bit more generic.
More broadly, I see this as a targeted way to improve Agate x OceanBioME compat which we can hopefully extend to PISCES in the future.
All reactions