iMOD Python tries to be as backwards compatible with iMOD5 as our resources allow. Below you can find some known issues, notes, and more detailed tables with the status of support for important iMOD5 features. If you miss an important feature or run into any issues, feel free to open an issue on our issueboard.
Known issues#ISG files cannot be read directly. The workaround is to rasterize the ISG files to IDF files using the iMOD5 BATCH function ISGGRID.
MetaSWAP sprinkling wells defined as IPF files are not supported.
MetaSWAP’s “flexible drainage” (“Peilgestuurde drainage” in Dutch) is not supported.
IPEST is not supported.
Edge case: When a well is located on the x-boundary of a cell in the model grid, the well is placed by iMOD5 in the western cell, whereas iMOD Python places the well in the eastern cell. This is because iMOD Python conforms to GDAL in how it looks up points in a grid. The workaround is to move the well slightly away from the boundary, by subtracting a small value from the x-coordinate of the well (e.g. 0.1 mm).
There is a bug in iMOD5 in how the HFB’s hydraulic characteristic is computed. iMDO5 adds the background resistance of the aquifer to the HFB resistance when writing the MODFLOW 6 input files. The background resistance is already accounted for by MODFLOW 6 internally, so in practice this means the background resistance is added twice. This is especially noticeable when a HFB intersects a low permeable layer. The workaround in iMOD5 is to specify a negative HFB factor in the projectfile, which makes iMOD5 to skip adding the background resistance.
By specifying a negative HFB factor in the projectfile, the iMOD5 documentation mentions this will turn on the option to override a resistance in between cells with the HFB resistance. This is NOT supported by MODFLOW 6, as MODFLOW 6 always adds the background resistance to the HFB resistance to compute the resistance inbetween cells.
if STO package in projectfile is absent, an error is thrown when trying to write the imod.mf6.Modflow6Simulation object to disk. This is due to the fact that the STO package is mandatory in iMOD Python. A workaround is to add a imod.mf6.StorageCoefficient package to the projectfile before calling imod.mf6.Modflow6Simulation.write().
When importing models with the ANI package, make sure to activate the “XT3D” in the NodePropertyFlow package of the model.
Solver settings (PCG) are NOT imported from iMOD5, instead a solver settings preset from MODFLOW 6 (“Moderate”) is set. This is because the solvers between iMODLFOW and MODFLOW 6 are different. You are advised to test settings yourself.
The imported iMOD5 discretization for the model is created by taking the smallest grid and finest resolution amongst the TOP, BOT, and BND grids. This differs from iMOD5, where the first BND grid is used as target grid. All input grids are regridded towards this target grid. Therefore, be careful when you have a very fine resolution in one of these packages.
Here an overview of iMOD5 files supported:
MODFLOW 6#Here an overview of iMOD5 MODFLOW 6 features:
MetaSWAP#An overview of the support for iMOD5’s MetaSWAP features:
Postprocessing#The following post-processing features are supported:
Visualization#The following visualization features are supported. For interactively viewing your data, see our iMOD Viewer.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4