Skip to content

Milestones

List view

  • v1.0 sidequests

    Nice to see fixed, but probably not going to happen

    Due by September 1, 2025
    •0/7 issues closed
    0% complete7 open0 closed

  • Epic: iMOD5 Backwards compatibility

    Things to do to achieve backwards compatibility of the common use-cases of iMOD5's RUNFILE function.

    No due date
    •7/25 issues closed
    28% complete18 open7 closed

  • v1.0 release

    Non-functional issues to resolve for v1.0 release

    Due by September 1, 2025
    •65/68 issues closed
    95% complete3 open65 closed

  • Epic: General maintenance

    Issues which are general maintenance.

    No due date
    •18/27 issues closed
    66% complete9 open18 closed

  • Epic: Multi-model support loose ends

    All left-over loose ends for the multi-model support can be added to this (not timeboxed) epic.

    No due date
    •11/14 issues closed
    78% complete3 open11 closed

  • Epic: General improvements

    No due date
    •29/41 issues closed
    70% complete12 open29 closed

  • Epic: MODFLOW6 Maintenance

    No due date
    •36/40 issues closed
    90% complete4 open36 closed

  • Epic: Regridding support

    No due date
    •15/17 issues closed
    88% complete2 open15 closed

  • Epic: Modflow 6: Differentiate Package objects into low-level and high-level abstraction layers

    It has become somewhat clear through the Lake Package (!166), Well, etc. that we could use both a "high level" package interface next to a "low level" one, which (mostly) matches the mf6 input one-to-one. The high level classes would contain `to_mf6_pkg` method, which takes a model grid, and returns a low-level grid with the data regridded to the model grid. The low level classes would contain `to_grid` to go from low-level to high-level (or more general name, wells would be turned into points or something). [In MR197](https://gitlab.com/deltares/imod/imod-python/-/merge_requests/197), a prototype low-level class was introduced, with a ``ncellid`` dimension, which contain the cellids, and the `nmax_cellid` dimension. The latter can have length 1 (``cell3d`` for DISU), length 2 (``layer, cell2d`` for DISV) or length 3 (``layer, row, column`` for DIS). This would replace the "to_recarr" functions and "to_sparse" method (which is a bit of a misnomer). Benefit is that users can completely inspect the intermediate objects, rather than having to debug the files. A high-level package has the following functionality: - Regrid to any provided grid - Mask cells in inactive model cells - Clip from a provided clipping box (xmin/xmax, ymin/ymax, time_min/time_max, zmin/zmax). - Write to netcdf - Read from netcdf - Connect to GIS world (Inherent from using x,y coordinates) - Convert to low-level The low-level package the following: - Writing Modflow 6 files - Reading Modflow 6 files - Convert to high-level A draft feature branch was created here: https://gitlab.com/deltares/imod/imod-python/-/merge_requests/199 A proposal design in UML: ![image](https://gitlab.com/deltares/imod/imod-python/uploads/60863ba47db5186c7f776375a6101623/image.png)

    No due date
    •5/10 issues closed
    50% complete5 open5 closed