i have problems running the Habitat risk assessment model, the logfile says The maximum pairwise risk score for multiplicative risk is 9.0
or The maximum pairwise risk score for euclidean risk is 2.8…
What do you expect to happen?
i don’t understand what is the issue here, i would expect it to run without problems
What have you tried so far?
i’ve tried using invest 3.13
i’ve tried using only 9 stressors
i’ve tried changing the parameters from decay and equation and number of overlapping stressors
i’ve tried using only a couple of habitat and stressors
i’ve checked if all my stressors .tiff are int (instead of float) ex_criteria_mon.csv (21.4 KB)
i’ve erased all field in my habitat .shp that are float
i’ve checked both the stressors table and the criteria table
File "natcap\invest\utils.py", line 164, in prepare_workspace
File "invest\cli.py", line 469, in main
File "natcap\invest\hra.py", line 537, in execute
File "natcap\invest\hra.py", line 2047, in _parse_criteria_table
AttributeError: 'float' object has no attribute 'lower'
I found a small formatting error in your criteria table. Each stressor row is expected to repeat the column headers, “RATING, DQ, WEIGHT, …”
thanks @dave, it solves the initial issue, but now im facing this new Error ‘NoneType’ object is not subscriptable,
i think it has something to do with some rasters sizes, however, the model was able to create the aligned tiffs and reprojected shapes
these are the first stressor and the first habitat aligned_aeropuerto_mon.tif (57.0 KB) reprojected_sierra chiquita_mon.zip (10.2 KB)
This new error is a tough one. It seems the aligned habitat and the aligned stressor that the model is creating are not actually aligned with one another. There is one extra column of pixels in the habitat raster.
thank you @dave, i dont know why or how this error is happening, but i was able to work around it by poligonizing all my stressors, the model seems to work fine when using only poligons,
it worked when i didnt have any rasters (.tif) as habitat or stressors
Okay, thanks @Gperilla, good to know. Yes, I expect it would work fine with all polygons or all rasters. I have your data to reproduce the error, and it is likely a bug in the model, so we’ll try to get to the bottom of it anyway.