When a weather file has a column that consists entirely of bad albedo values, should we consider reporting them as one error "Weather file contained X bad albedo values, monthly value was used", sort of like we do for bad values in the snow model? "SRRL weather data with fixed snow and fake POA" in the sam-documentation repo can be used to see the current behavior, which is a separate warning for every single timestep.

Not urgent, and welcome opinions to the contrary.