-
Notifications
You must be signed in to change notification settings - Fork 0
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
XBeach Rompy #5
Comments
To clarify forcing options apart from Bulk Simon indicates "Accepts user specified “bulk” forcing or select forcing datasets |
a. Accept forcing data inputs (bathy, waves, wind) as files as well as the ability to extract these data from xarray based sources as required |
Adapt rompy to implement XBeach, with functions that can be called to create “ready-to-run" workspaces for XBeach model runs (based on a Python notebook to be provided by CSIRO), and including at least:
a. Accept forcing data inputs (bathy, waves, wind) as files as well as the ability to extract these data from xarray based sources as required
b. Defining a spatial domain initially as a structured grid (also see ramping requirement at Ramping the xbeach grid #4)
c. Produce the XBeach model control file using a template (Jinja2/Cookiecutter) that exposes the required configuration options to replicate the provided notebook
d. Write into output data appropriate geospatial metadata for orienting the data geographically
e. Implement the capability to use simple forcing data in rompy xbeach. Allow hand built forcing files, optionally lacking any geospatial reference, to be provided as manual forcing ensuring that basic validation is in place to check that the data is compatible with model configuration. This implementation should, if practical, consider future implementation of this functionality in other rompy models detail in Bulk forcing options - XBeach #3
The text was updated successfully, but these errors were encountered: