xmipy extension for the MODFLOW API
active 2025-03-09 → 2026-08-08 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 518 days from 2025-03-09 to 2026-08-08. Pushes: 8 total, peak 2 in a day. Pull requests: 10 total, peak 2 in a day. Issues: 7 total, peak 2 in a day. Comments: 20 total, peak 2 in a day. Stars: 2 total, peak 1 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| wpbonelli | 15 | 7 | 5 | 3 |
| jlarsen-usgs | 7 | 0 | 2 | 3 |
| pya | 4 | 0 | 0 | 4 |
| ifariasg | 3 | 0 | 0 | 1 |
| zongxunchai | 3 | 0 | 0 | 2 |
| dbrakenhoff | 2 | 0 | 0 | 1 |
| manupy-hub | 2 | 0 | 0 | 0 |
| emorway-usgs | 2 | 0 | 0 | 2 |
| mwtoews | 1 | 0 | 1 | 0 |
| jesshe | 1 | 0 | 0 | 1 |
| mjr-deltares | 1 | 0 | 0 | 1 |
| aufdenkampe | 1 | 0 | 0 | 1 |
| christianlangevin | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Pull request#106mwtoews2026-08-08 02:47
- Pull request#96wpbonelli2026-06-18 14:27
- Issue#93ifariasg2026-04-08 17:29Support / roadmap for parallel MODFLOW 6 via MODFLOW API (initialize_mpi)?
- Issue comment#72pya2026-02-21 04:43Wrong results with models that use time series
- Issue#85jlarsen-usgs2026-02-20 22:33Running model with recharge time series only uses first value when running with API
- Issue#72jlarsen-usgs2026-02-20 22:33Wrong results with models that use time series
- Issue comment#88ifariasg2026-02-17 17:40Callback function when there is more than one model in a simulation (eg. GWF+GWT)
- Issue comment#85dbrakenhoff2026-02-13 09:43Running model with recharge time series only uses first value when running with API
- Issue comment#88jlarsen-usgs2026-02-12 23:32Callback function when there is more than one model in a simulation (eg. GWF+GWT)
- Issue#88ifariasg2026-02-12 23:19Callback function when there is more than one model in a simulation (eg. GWF+GWT)
- Pull request#87wpbonelli2026-01-16 16:19
- Issue comment#72jlarsen-usgs2025-12-12 19:15Wrong results with models that use time series
- Issue comment#86zongxunchai2025-11-20 05:39Dynamic Update of Hydraulic Conductivity During Simulation Has No Effect (MODFLOW API)
- Issue comment#86emorway-usgs2025-11-17 01:32Dynamic Update of Hydraulic Conductivity During Simulation Has No Effect (MODFLOW API)
- Issue comment#86christianlangevin2025-11-16 13:10Dynamic Update of Hydraulic Conductivity During Simulation Has No Effect (MODFLOW API)
- Issue comment#86zongxunchai2025-11-16 08:20Dynamic Update of Hydraulic Conductivity During Simulation Has No Effect (MODFLOW API)
- Issue comment#86emorway-usgs2025-11-14 18:13Dynamic Update of Hydraulic Conductivity During Simulation Has No Effect (MODFLOW API)
- Issue#86zongxunchai2025-11-08 14:21Dynamic Update of Hydraulic Conductivity During Simulation Has No Effect (MODFLOW API)
- Issue#85dbrakenhoff2025-11-04 10:02Running model with recharge time series only uses first value when running with API
- Issue comment#72jlarsen-usgs2025-07-30 22:13Wrong results with models that use time series
- Issue comment#84mjr-deltares2025-07-29 08:52Inconsistent river flow values from SIMVALS("RIV") vs .lst/.cbc outputs
- Issue#84manupy-hub2025-07-28 06:06not getting the same values from gwf.get_value(gwf.get_var_address("SIMVALS", gwf_name, "RIV") than CBC
- Pull request#83jdhughes-dev2025-07-24 14:47
- Pull request#83jdhughes-dev2025-07-23 22:01
- Issue comment#72jesshe2025-07-03 20:53Wrong results with models that use time series
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 2 stars here means stars gained during the window, not the repo's star count.