potet coefficients were being set each time step instead of only when new values were read, so values set to super small values.
Similar issue if dynamic soil_moist_max or soil_rechr_max, but, it was just checking values each time step instead of updating to bad values, so just extra CPU burning.
potet coefficients were being set each time step instead of only when new values were read, so values set to super small values.
Similar issue if dynamic soil_moist_max or soil_rechr_max, but, it was just checking values each time step instead of updating to bad values, so just extra CPU burning.
Fixes made in dynamic_param_read.f90