-
Notifications
You must be signed in to change notification settings - Fork 3
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
Github Actions; Preliminary Documentation #6
Conversation
we don't have to do it in this PR but we should consider also having a single netcdf with hourly data for a few days and test reading inflows and aggregating up to daily or some other time step. |
fixes #4 -> this is my implementation of inputing multiple weight tables. Added tests to verify these results as well |
.github/workflows/test.yml
Outdated
workflow_dispatch: | ||
branches: | ||
- rapid-inflows | ||
[push, pull_request, workflow_dispatch] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i would be ok with on pull request or workflow_dispatch. Do you think we need to do it on every push?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it is neccesary. It's nice since it automatically tests every push, but workflow_dispatch could make it obsolete since we can run the test whenever we want. If you want me to remove it I can
fixes #5 -> function now checks if weight table dims match the dataset dims. Info provided in readme about naming conventions |
fixes #2 -> test data added and github actions set up
Refs #3 -> some documentation done, readme added