Cliff Hansen

My vote is for option 3, which I think is what will happen (eventually) if we choose 2 or 1.

Concur with no deprecation and v0.11.0

@pvlib/pvlib-maintainer whatsnew used to have "API changes". We dropped that when we switched to "Breaking changes" and "Deprecations" and now I'm not sure where we list a function that's been...

Thanks @mdeceglie. I've had on my list for a while to implement [this extension](https://research-hub.nrel.gov/en/publications/clear-sky-detection-for-pv-degradation-analysis-using-multiple-re-2) of the detect clearsky algorithm. In the meantime, PRs welcome to improve the error detection/docstrings.

In the second case: the window contains 2 data values. Buried in the detect_clearsky algorithm is the calculation of a _sample_ standard deviation of slopes between points in an interval....

To be clear, MIDC no longer offers data from those old instruments through their API? Or, are the old data still available somehow, and there are also data from new...

If someone requests old data (prior to these MIDC changes), they will get old data. If they also ask for variable mapping, pvlib will rename any of the current fields,...

> merging this PR is the current best option I agree

I don’t see why not. Anyone have a readable .PAN file I could work from? From: DanRiley [mailto:[email protected]] Sent: Tuesday, June 28, 2016 8:20 AM To: sandialabs/MATLAB_PV_LIB [email protected] Subject: [EXTERNAL]...

I think we also need code tests to verify installation or code changes. From: DanRiley [mailto:[email protected]] Sent: Tuesday, June 28, 2016 10:35 AM To: sandialabs/MATLAB_PV_LIB [email protected] Subject: [EXTERNAL] [sandialabs/MATLAB_PV_LIB] Include...