Dear Eibhlín Vaughan,

To further diagnose if the issue is with SWAT+ or TauDEM, try running the TauDEM pitremove operation independently outside of SWAT+ using the same input DEM file. This can determine if the issue arises from interaction with SWAT+ or is inherent to TauDEM. Also verify the input DEM raster format is supported by TauDEM, as some formats like GeoTIFF typically work better than others. Start with a very small 10m x 10m subset of the DEM to see if pitremove succeeds on that, then progressively increase the area size to isolate any problems related to data complexity or resource demands. If memory or performance seem insufficient, try decreasing the resolution or computational resources allocated to pitremove. Taking these steps to narrow down the root of the problem can clarify whether the pitremove failure stems from SWAT+ linkage or limitations within TauDEM itself.

Humble Regards,