Hey Luke -
Oh dear. The first thing I’m seeing is that you’re getting LZW errors before the ufunc error. This is a bigger software problem that is still being worked on by the software team. It seems to happen with particularly large datasets, and so far there’s no workaround that I’m aware of, is that correct @jdouglass?
Another thing could be the naming of your precip rasters. The requirement is this (from the User Guide):
"Folder containing 12 rasters of monthly precipitation for each pixel. Raster file names must end with the month number (e.g. Precip_1.tif for January.) "
It looks like your precip rasters are not named this way, they are more like “prcp_a3_EA_01.tif” and “prcp_a4_EA_01.tif”. Try correcting these file names (your ET0 rasters might need the same adjustment) and see if that changes anything. You might still get the LZW error though.
If that doesn’t help, and I’m going to try to run the model and replicate the problem, I’d need all of your inputs. It is giving the error with the quickflow calculation, so theoretically I could look at the inputs that go into that without needing everything, but that’s still a majority of the data (precip, rainy days, land cover, biophysical table…) and it wouldn’t allow me to actually try running the model.
If you do end up sending the whole data bundle, the easy way to do it is to use the model interface, which will let me just drag and drop it into my SWY window and get all of the parameters exactly like you’re using:
- File > Save as
- Datastack type: Data archive
- Check the box next to “Use relative paths”
- Post the result to Google Drive or wherever
If you want to do some sleuthing before sending the data… The first thing I’d probably look at are the rainy day and biophysical tables, make sure they are actually comma-separated, don’t have any blank lines at the end, or have any other oddness that can throw off processing CSVs (much of that is only visible when you look at the file in a text editor like Notepad, not Excel.)
Then I’d double-check the precipitation and soil group rasters, do they have valid values (for example, the soil group can only have values 1-4), do they have No Data values set (I think you may have already checked for that?) etc.
Aside from the LZW error, the models can usually handle pretty large datasets, but there’s always a computational limit. What is the resolution of your DEM? That will be the processing resolution of the model.