Hi @sfix -
Thanks for posting your log file. It must be a big watershed, to take almost 6 hours, and I’m surprised that it took so long to give this error. It seems to be happening when the model is summing the raster results by your watershed shapefile. Given the error message, my first guess is that bigSioux.shp has a different coordinate system than the other inputs, so check to make sure that it has exactly the same projected coordinate system as your raster inputs.
Another possibility is that some of the watershed polygon (or some of the sub-watersheds, if you’re using those) lies outside of the raster coverage, so the resulting rasters do not cover the whole watershed. In this case, you’ll need to either extend the input rasters to cover the whole watershed, or choose a sub-watershed that lies within the raster coverage.
It does appear that the model actually produced all of the raster results. So if you’re only interested in those, you might not need to worry about the aggregation error. Another nice thing is that the new feature Taskgraph might make re-running the model go much faster, since it won’t re-run any of the calculations that haven’t changed since the previous run.
By “SDR value” do you mean the “Max SDR Value” model input? The User Guide says this:
SDRmax (required): The maximum SDR that a pixel can reach, which is a function of the soil texture. More specifically, it is defined as the fraction of topsoil particles finer than coarse sand (1000 μm; Vigiak et al. 2012). This parameter can be used for calibration in advanced studies. Its default value is 0.8.
Does that help? I’ll say that I’ve run this model a lot, and have always used the default value of 0.8.