Gamze Yıldırım
unread,Sep 1, 2026, 1:39:31 PM (6 days ago) Sep 1Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to SWAT+ Toolbox
Hello,
I'm reporting an issue with the gwflow module in SWAT+ Editor v4.0.1 (rev. 62). We've run into several related problems, all pointing to gwflow outputs/interactions not working correctly in this version:
1) Stream-aquifer exchange does not respond to parameter changes. We raised streambed hydraulic conductivity (stream_K) to 0.5 m/day, but observed no measurable change in the stream-aquifer exchange output.
2) We were unable to add observation wells properly - the well entry process in SWAT+ Editor did not work as expected, and the gwflow.input file (where well definitions should be stored) does not exist at all in the TxtInOut folder.
3) As a consequence, gwflow_obs_mon.txt is always empty (1 KB, never updated since project setup) even though other gwflow monthly outputs (e.g. gwflow_basin_wb_mon.txt, gwflow_cell_wb_mon.txt) are correctly generated and updated after each run. As a workaround, we've been manually extracting head values for the relevant cells from gwflow_cell_wb_mon.txt instead.
4) Groundwater abstraction (pumping) produces no output either. We set up water-stress-triggered auto-irrigation from the aquifer on the relevant HRUs (plant water stress <0.99 threshold, 25 mm, up to 20 times/year) and confirmed the aquifer/cell linkage is correct, but gwflow_hru_pump_mon.txt stays at 1 KB and never records any pumping
Has any of this been reported before, in particular the missing gwflow.input file and the well-entry issue? Any guidance on known issues or required settings for gwflow rev. 62 would be appreciated. I've shared a screenshot of the TxtInOut folder showing the file sizes/timestamps if useful.
Thank you.
Best regards