Closed seanbergin closed 5 years ago
The dropping to zero in the second year is because the water_scarcity_index is initialized to zero in the first year. I'll change that to actually compute the water scarcity index of the initial year.
This is also happening with the non_potable_water_vulnerability_index. Thanks
Should be fixed now. Days with flooding and ponding values are off but I'll put that in a new issue. (and those values are impacting non_potable_water_vulnerability_index
in year 2 much larger than the remaining years)
Vulnerability (for potable and non-potable) starts out high for 2018, drops to 0 for 2019 and then stays at normal levels. Is this an artifact of the model initialization or a larger issue?