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

General modeling workflow components #7

Open
SorooshMani-NOAA opened this issue May 6, 2022 · 1 comment
Open

General modeling workflow components #7

SorooshMani-NOAA opened this issue May 6, 2022 · 1 comment

Comments

@SorooshMani-NOAA
Copy link

Let's discuss components required for modeling, including but not limited to:

  • Forcing components
    • Meteorological
    • Tidal
    • etc.
  • Bathymetry information
  • Meshing
  • Coupling
  • Manager
@brey
Copy link
Contributor

brey commented Jun 2, 2022

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.

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

No branches or pull requests

2 participants