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

Create long-standing development "GW" branch for GroundWater component development #77

Open
ekluzek opened this issue Jan 7, 2024 · 2 comments
Assignees
Labels

Comments

@ekluzek
Copy link
Contributor

ekluzek commented Jan 7, 2024

We will create a long-standing branch for development of a GroundWater component that will be beneath MOSART but as a separated component.

I propose we name the branch "gw" and use the CTSM branch naming convention of:

branch_tags/NAME.nXX_BASELINETAG

So for example, you'll have (expanding the branch versions to 3-digits)

branch_tags/gw.n001_mosart1_0_50

@swensosc @slevis-lmwg

@ekluzek ekluzek self-assigned this Jan 7, 2024
@ekluzek
Copy link
Contributor Author

ekluzek commented Jan 7, 2024

This work will start as an evaluation of it's usefulness. Long term we wouldn't want it to be locked into being a part of MOSART. A potential option is to add it as a component of CMEPS. Another option would be for it treated as a subcomponent of any river-model, in such a way that it could be coupled into another river model (i.e mizuRoute). In either of these cases the GW component would be spun off into it's own model and added as an external to river models that can utilize it.

As such as the top level infrastructure is developed for the GW component we should work on designing it in a way that it can be spunoff into it's own component.

@ekluzek
Copy link
Contributor Author

ekluzek commented Jan 10, 2024

This will be done after #76 comes in, and that tag will be the starting basis for this branch work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant