Kevin Anderson

Append `v5` to the function names? So `ModelChain.with_pvwattsv5`, etc, and deprecate the originals

I think there are two independent goals here. For one, to resolve the ambiguity of what models our current "pvwatts_dc" et al. functions implement. For two, to make space for...

> Would the version suffix refer to the version where the function was introduced? That makes sense to me. The docstring could list any newer versions that also use it....

Diffuse and horizon shading are good steps forward but I think adding a model for row-to-row direct shading as well would make it easier to say "yes, pvlib-python models shading"....

+1 from me for having multiple shading models available in pvlib. I'd be happy to help with a python version of the SAM model or any other model of interest.

> library updates don't require a pvlib re-release if the two are decoupled > +1. But that feels like a breaking change Perhaps that concern could be addressed by pvfree...

Looks like the NDFD section has some broken code too. > the "View on Github" link is broken In fact most of the top-level pages in `stable` have broken "view...

In https://github.com/pvlib/pvlib-python/issues/1199#issuecomment-801431990 @cwhanse said: > That would be a nice addition to pvlib. But, to my knowledge the inverter model in Pvsyst is not fully documented. The Pvsyst license prohibits...

> The outputs are ridiculous. The temperatures increase exponentially and basically hit a singularity. There seems to be a feedback loop where t_mod_delta calculated for each step is too large....

@stephenjkaplan For the `module_area*poa_effective` question, could it be it a matter of different module sizes for Series 4 (or 3) vs Series 6 (0.72 vs 2.47 m^2)? From Table 1...