You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks @SorooshMani-NOAA for pointing this out. Although there is an overlap with #3 , I would suggest to use this one to link the workflow components with corresponding developmental packages.
Thus, my take:
Forcing components
Meteorological
- Use any of the packages listed https://github.com/orgs/oceanmodeling/projects/4 or others that we don't know of.
- Do we have a need for a wrapper (similar to the meteo module of pyposeidon? Seaforce maybe?
Tidal
- Support FES, TPX, others? They are distributed as files. No API. How to deal with this?
Bathymetry information
- Merging of DEMs. I suggest a new package to deal with that. Could be wrapper around existing ones if available.
Meshing
- Seamesh will handle that.
Coupling
- This one deserves more consideration. Could be part of the manager but use cases are needed to have a better idea.
Manager
- Seamulate is envisioned to handle that. We have to define the scope of it.
Let's discuss components required for modeling, including but not limited to:
The text was updated successfully, but these errors were encountered: