You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The LHM apparently has > 1000 cells where IDOMAIN == 2. I noticed that wells located in these cells get masked away. For both iMOD5 as well as MODFLOW 6, IDOMAIN > 0 means active cell. iMOD Python, however, enforces/assumes IDOMAIN == 1, but we don't actually validate this.
I think it is more user friendly to support IDOMAIN > 0. A quick search showed that we only have a few files where active is computed as idomain == 1, so it appears to be low hanging fruit.
The text was updated successfully, but these errors were encountered:
JoerivanEngelen
changed the title
[Bug] - Find active cells with idomain > 0 instead of idomain == 1
Find active cells with idomain > 0 instead of idomain == 1
Jan 10, 2025
Fixes#1376
# Description
This aligns the way we find active cells, consistently with MODFLOW6:
idomain > 0 is now the active domain, instead of idomain == 1. I updated
some model fixtures to have idomain = 2 to see if stuff like masking
works now for idomain == 2. Furthermore, I tried my best to update all
docstrings.
# Checklist
- [x] Links to correct issue
- [x] Update changelog, if changes affect users
- [x] PR title starts with ``Issue #nr``, e.g. ``Issue #737``
- [x] Unit tests were added
- [ ] **If feature added**: Added/extended example
The LHM apparently has > 1000 cells where IDOMAIN == 2. I noticed that wells located in these cells get masked away. For both iMOD5 as well as MODFLOW 6, IDOMAIN > 0 means active cell. iMOD Python, however, enforces/assumes IDOMAIN == 1, but we don't actually validate this.
I think it is more user friendly to support IDOMAIN > 0. A quick search showed that we only have a few files where active is computed as idomain == 1, so it appears to be low hanging fruit.
The text was updated successfully, but these errors were encountered: