The recent irrigation module proof of concept (#3148) and renewed discussion around online Wflow-Ribasim coupling (issue #16 comment) suggest that it may be a good time to revisit the current module implementation plan (issue #3159).
The current irrigation PoC and implementation plan focus on module-specific functionality and do not explicitly consider a wider online coupling. A more generic online coupling framework could potentially support irrigation use cases as well as a wider range of future applications. Before proceeding further with implementation, it would therefore be valuable to review the current direction and align on the intended scope.
Topics to discuss include:
- How the irrigation module relates to a broader online Wflow-Ribasim coupling approach.
- Whether irrigation-specific functionality should be implemented as a dedicated module, through a generic coupling framework, or through a combination of both.
- The advantages, disadvantages, and long-term implications of the different options.
The goal is not necessarily to change course, but to ensure that architectural and implementation decisions are made with a clear understanding of both short-term needs and long-term ambitions. The outcome should be a well-defined scope and an updated implementation plan that provides a clear path forward.
The recent irrigation module proof of concept (#3148) and renewed discussion around online Wflow-Ribasim coupling (issue #16 comment) suggest that it may be a good time to revisit the current module implementation plan (issue #3159).
The current irrigation PoC and implementation plan focus on module-specific functionality and do not explicitly consider a wider online coupling. A more generic online coupling framework could potentially support irrigation use cases as well as a wider range of future applications. Before proceeding further with implementation, it would therefore be valuable to review the current direction and align on the intended scope.
Topics to discuss include:
The goal is not necessarily to change course, but to ensure that architectural and implementation decisions are made with a clear understanding of both short-term needs and long-term ambitions. The outcome should be a well-defined scope and an updated implementation plan that provides a clear path forward.