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.

Sign up for GitHub

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

Jump to bottom

Separate upland and fluvial components #11

Open
franz825 opened this issue Oct 7, 2020 · 0 comments · May be fixed by #30
Open

Separate upland and fluvial components #11

franz825 opened this issue Oct 7, 2020 · 0 comments · May be fixed by #30

Comments

@franz825
Copy link

franz825 commented Oct 7, 2020

For didactic purposes, I suggest that we keep upland and fluvial components as separated notebooks. Notebooks are run in a sequence, which is explained in the main readme file. Outputs of upland component are used as inputs (generic naming convention) by the fluvial component.
@josiearcuri josiearcuri linked a pull request Jan 9, 2021 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

jarcuri/reorganize espin-2020/fluvial
1 participant
@franz825