-
Notifications
You must be signed in to change notification settings - Fork 5
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
Restructure STEPWAT2 #478
Comments
@dschlaep it would be great to get your thoughts on this. We have three goals here:
perhaps something similiar to be done with SOILWAT2? |
A few quick thoughts:
Maybe a meeting would be easier? |
To sum up the meeting @kpalmqui, @dschlaep and I had, we decided that restructuring both STEPWAT2 and SOILWAT2 would be a good idea. In general the layout I describe above will work for STEPWAT2. However, we decided that before we restructure the files we should decouple the STEPWAT2 makefile from any specific SOILWAT2 structure. This means the STEPWAT2 makefile should call the SOILWAT2 makefile then use the resultant library file to build STEPWAT as opposed to building STEPWAT2 using SOILWAT2 files directly. I will open a separate issue for this and depending on how quickly we can merge in the other development branches I will implement the change. |
Issue #483 summarizes the changes that must occur to decouple the STEPWAT2 makefile. |
The structure of the STEPWAT2 repository could be streamlined very easily to make it easier to understand and use. I spent some time thinking about what the new structure could look like and this is my suggestion:
The main directory:
dev:
Inputs:
Outputs:
There are obviously some small details to still work out, but I think this general structure would be much easier to understand.
The text was updated successfully, but these errors were encountered: