List view
Non-functional issues to resolve for v1.0 release
Due by September 1, 2025•77/77 issues closedRefactor datatransformations operating on Modflow 6 objects
Due by March 31, 2024•4/4 issues closedThe nightly builds of iMOD Python support parallel solute transport. This is the last feature required from iMOD Python to help iMOD-WQ users (other features they might require have to be implemented in Modflow 6). General approach: - Starting point: One GWF, one GWT model with GWF - GWT exchange - Create labeled array containing partitions - Split GWF models with GWF-GWF exchanges - NEW: Check if aux vars containing concentrations preserved in GWF packages - NEW: Split GWT models with GWT-GWT exchanges - NEW: Create new GWF-GWT exchanges, delete original GWF-GWT exchange - NEW: Merge concentration output and transport budgets
Due by March 31, 2024•26/26 issues closed- No due date•3/3 issues closed
End goal is being able to read and convert iMOD5 models to Modflow 6 models, from projectfiles, like iMOD Batch's RUNFILE function. This milestone features all functionality to achieve conversion of the LHM model
Due by December 31, 2024•95/95 issues closed- No due date•1/1 issues closed
- No due date•19/19 issues closed
Sprint 7
Due by August 10, 2023•6/6 issues closed- Due by July 30, 2023•5/5 issues closed
- Due by July 9, 2023•2/2 issues closed
- Due by June 25, 2023
improve imod5 compatibility of a mf6 groundwater flow model
Due by June 8, 2023Features developed in this sprint will be merged with feature branch ``imod5_compatibility_featurebranch``, except the ValidationError issue.
Due by May 25, 2023•3/3 issues closedUser stories for sprint belong here
Due by May 30, 2023•1/1 issues closedPut all roadmap developments here
No due date•1/1 issues closedIssues to solve non-functional requirements to reach the v1.0 beta release. Functional requirements are listed here: https://github.com/Deltares/imod-python/milestone/21
Due by December 31, 2024•23/23 issues closedThe architecture for model input validation has been added with the validation for Modflow 6, in the form of the ``schemata`` module. It is good to add that validation for iMOD-WQ and iMODFLOW models as well. Furthemore there are some additional issues we can fix to improve user friendliness for generating these models.
No due date•16/16 issues closedSupport MF6 multi-models, this is needed to support parallel MF6. A function need to be created that splits a simulation into submodels. pseudo code: `new_simlation = simulation.split( splitting_array)` splitting_array is an integer array with the submodel index per cell Focus on unstructured grids. Make sure high-level packages like Well are included in all submodels, and make sure the total number of wells after splitting is the same as before splitting. Make sure the wells end up in the right locations. Splitting simulations containing multiple models (multiple flow models, or flow and transport) is not supported for now. Make sure rivers and lakes end up in the right location after splitting. To be decided: \-should the split function be a part of the simulation class (as in the code snippet above) , or should we create a separate splitter-object like flopy does? Feature branch: - feature/multi_model_support
Due by November 30, 2023•22/22 issues closedSupport reading of native MODFLOW models and converting them to the iMOD-python structure. Also revered to as the "from flopy" functionality
No due date•2/2 issues closediMOD Python currently does not have a model definition file, which points to all package data. iMOD 5 had such a thing, namely a projectfile. It also had functionality to clip and regrid a submodel from an existing model. This functionality is required to support existing iMOD 5 models. We also need to be able to read existing project files and converting them to the new configuration. The model definition, can then be used for example in the iMOD QGIS plugin to load a model. **Scope** We focus on providing functionality required for existing regional models, these contain: * No lake package * No solute transport * Do contain: RIV, DRN, WEL, HFB, NPF, DIS(V), STO, GHB, CHD * A coupled MetaSWAP model
Due by August 31, 2023- Due by July 25, 2019•5/5 issues closed
This is to ensure that milestone numbers in GitLab and GitHub are the same
No due date