pvlib-python bring pvlib-python up to date with PVLIB-MATLAB 1.2 and 1.3

Add additional functions introduces in PVLIB-matlab 1.2

Feb 17 '15 01:02 robwandrews

Where can we find PVLIB-matlab 1.2? Is it this one? https://github.com/Sandia-Labs/PVLIB_Matlab/commits/master

Is the documentation of functions online? It looks that one needs to be logged in: https://pvpmc.sandia.gov/resources-for-members/pv_lib-toolbox/matlab/functions-by-catagory/

And is it planned to develop matlab & python libs always in parallel?

anyway, I would like to see in future Shading and Soiling (Item 3) as well as AC Losses (Item 9) of https://pvpmc.sandia.gov/wp-content/uploads/2014/08/1199X499_slide2.png But maybe these deserve a separate page/issue.

Feb 17 '15 10:02 dacoex

PVLIB-Matlab 1.2 is only available at the PVPMC website. The github PVLIB_Matlab repository is an older version and may be removed. @Calama-Consulting you might want to ask Josh if he wants the matlab project available on github since it may hurt their official download statistics.

The readme has a link to the documentation.

We want to keep the core functionality and algorithms of the python and matlab projects roughly in parallel, but we're not making any promises at this point.

Yes, please do make separate issues for any feature requests.

Feb 17 '15 17:02 wholmgren

PVLIB-Matlab 1.2 is only available at the PVPMC website. The github PVLIB_Matlab repository is an older version and may be removed.

OK, so login and find out...

The readme has a link to the documentation.

Which is behind a login gate.

We want to keep the core functionality and algorithms of the python and matlab projects roughly in >parallel, but we're not making any promises at this point.

So this means: PVPMC adds a functionality and then issues a release, then the pvlib-python would be updated? A rather parallel process? In consequence, one would have to know Mtalab, as well?

Yes, please do make separate issues for any feature requests.

OK, one the development strategy discussed here is clear.

Feb 17 '15 21:02 dacoex

The read me for this github repo has a line

"Full documentation can be found at readthedocs"

Which links to

http://pvlib-python.readthedocs.org/en/latest/

This is the Pvlib Python documentation only.

The Matlab and Python projects are developed by different teams that do not regularly work together. There will not be feature parity, only similarity. On Tue, Feb 17, 2015 at 2:00 PM Data & Code Expert Experimenting with Code on Data [email protected] wrote:

PVLIB-Matlab 1.2 is only available at the PVPMC website. The github PVLIB_Matlab repository is an older version and may be removed.

OK, so login and find out...

The readme has a link to the documentation.

Which is behind a login gate.

We want to keep the core functionality and algorithms of the python and matlab projects roughly in >parallel, but we're not making any promises at this point.

So this means: PVPMC adds a functionality and then issues a release, then the pvlib-python would be updated? A rather parallel process? In consequence, one would have to know Mtalab, as well?

Yes, please do make separate issues for any feature requests.

OK, one the development strategy discussed here is clear.

— Reply to this email directly or view it on GitHub https://github.com/pvlib/pvlib-python/issues/2#issuecomment-74752219.

Feb 17 '15 21:02 wholmgren

The Matlab and Python projects are developed by different teams that do not regularly work together. There will not be feature parity, only similarity.

OK, this is more clear. Consequently, you may decide to spearhead with new features and then the Matlab will follow?

Or is pvlib after a similar feature set but more driven by its developers/users?

Maybe good also to limit the scope and compare it to other packages such as https://github.com/pingswept/pysolar. Then teh docs cloud show where pvlib by its intention will be different apart from the more sphisticated tied-in to the scipy stack with the reliance on pandas (very positive).

I am thinking of something like: Related Packages http://statsmodels.sourceforge.net/devel/related.html

Looking forward to your feedback on this and the above questions.

Feb 17 '15 22:02 dacoex

Pvlib Python already has a few features that the Matlab version doesn't have. It's up to the Matlab developers to update their code where possible. I can only say that the Python project will try to stay current with most things that the Matlab project adds.

The Python project will be mostly community supported, whereas the Matlab project is mostly supported by u.s. department of energy grants.

The Python project is very much tied to the scientific Python stack. This would not be feasible without those libraries.

Our pvsc 2015 abstract and rob's 2014 PVSC paper outline the scope of this project.

Pysolar is much more limited in scope and is gpl licensed. Nothing against Pysolar, it's just different.

I will put some of this in the docs/readme. On Tue, Feb 17, 2015 at 3:45 PM Data & Code Expert Experimenting with Code on Data [email protected] wrote:

The Matlab and Python projects are developed by different teams that do not regularly work together. There will not be feature parity, only similarity.

OK, this is more clear. Consequently, you may decide to spearhead with new features and then the Matlab will follow?

Or is pvlib after a similar feature set but more driven by its developers/users?

Maybe good also to limit the scope and compare it to other packages such as https://github.com/pingswept/pysolar. Then teh docs cloud show where pvlib by its intention will be different apart from the more sphisticated tied-in to the scipy stack with the reliance on pandas (very positive).

I am thinking of something like: Related Packages http://statsmodels.sourceforge.net/devel/related.html

Looking forward to your feedback on this and the above questions.

— Reply to this email directly or view it on GitHub https://github.com/pvlib/pvlib-python/issues/2#issuecomment-74771603.

Feb 17 '15 23:02 wholmgren

Thanks a lot.

So next could be a series of feature plans that can be added to the roadmap.

Feb 18 '15 07:02 dacoex

Here's a list of the v1.2 Matlab project's functions that we're missing (from the 1.2 help page):

[ ] pvl_louche - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the LOUCHE model
[ ] pvl_orgill_hollands - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Orgill and Hollands model
[ ] pvl_erbs - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Erbs model
[ ] pvl_reindl_1 - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Reindl 1 model
[ ] pvl_reindl_2 - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Reindl 2 model
[ ] pvl_martinruiziam - Determine the incidence angle modifier using the Martin and Ruiz incident angle model
[ ] pvl_adrinverter - Anton Driesse's Grid-Connected PV Inverter

I also looked at the changelog but most of it has either already been incorporated or is Matlab specific.

Many of these would be good first PRs.

Apr 09 '15 22:04 wholmgren

Maybe Anton could implement "his Inverter" ;-) @adriesse?

Apr 10 '15 06:04 bmu

Sure.  What's the best way to publish a
  collection of model parameters?

  Anton

Apr 10 '15 08:04 adriesse

Thanks. I suggest a csv file in pvlib/data since this can be easily imported by pandas.

Apr 10 '15 16:04 wholmgren

Copy/paste from PVPMC's recent PVLIB Matlab 1.3 announcement...

[ ] pvl_FSspeccorr: Spectral mismatch modifier function contributed by First Solar based on precipitable water.
[ ] pvl_calcPwat: function to estimate precipitable water content
[ ] pvl_huld: PV performance model of Huld et al., 2011
[x] pvl_PVsyst_parameter_estimation: function to estimate PVsyst module parameters from IV curves.
[x] pvl_calcparams_PVsyst: Calculates the five parameters for an IV curve using the PVsyst model.
[x] pvl_desoto_parameter_estimation: function to estimate Desoto module parameters from IV curves.
[ ] pvl_getISDdata: Functions to access ground measured weather data from NOAA's Integrated Surface Data network

Jan 12 '16 18:01 wholmgren

Will,

I put version 1.3 together. The PVPMC notice is only highlights, here’s the full list of new functions and changes copied from the Matlab toolbox release notes.

Cliff

Jan 12 '16 18:01 cwhanse

Thanks Cliff!

Jan 12 '16 18:01 wholmgren

In anticipation of the upcoming Santa Clara workshop, I'm consolidating the lists in the comments above into a new list. I also removed some of the items that don't apply to python. It's probably best to start making new issues for specific features.

[x] pvl_louche - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the LOUCHE model
[ ] pvl_orgill_hollands - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Orgill and Hollands model
[x] pvl_erbs - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Erbs model. And from v1.3: Corrected pvl_erbs; the coefficient of K_t^2 changed from 4.3888 to 4.388
[ ] pvl_reindl_1 - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Reindl 1 model
[ ] pvl_reindl_2 - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Reindl 2 model
[x] pvl_martinruiziam - Determine the incidence angle modifier using the Martin and Ruiz incident angle model
[x] pvl_adrinverter - Anton Driesse's Grid-Connected PV Inverter
[x] pvl_PVsyst_parameter_estimation - Estimates parameters for the PVsyst version 6 module performance model.
[x] pvl_desoto_parameter_estimation - Estimates parameters for the De Soto single diode module performance model.
[x] pvl_rectify_IV_curve - Ensures that Isc and Voc are included in a IV curve and removes duplicate voltage and current points.
[x] pvl_calcparams_CEC - Create module performance model coefficients for the single diode model used by the CEC.
[x] pvl_calcparams_PVsyst - Create module performance model coefficient for the single diode model in PVsyst version 6.
[ ] pvl_huld - Calculates DC power using the Huld PV module model.
[x] pvl_calcPwat - Calculate precipitable water (cm) from ambient air temperature (C) and relatively humidity (%). see #115.
[x] pvl_FSspeccorr - Calculate spectral mismatch modifier based on precipitable water and absolute airmass. see #115.
[ ] pvl_getISDdata - Fetch data from NOAA ISD at ftp.ncdc.noaa.gov.
[ ] pvl_readISH - Read data fetched from ftp.ncdc.noaa.gov into a table.
[x] Changed pvl_calcparams_desoto to require effective irradiance as its input, rather than absorbed irradiance (i.e., broadband irradiance reaching a module's cells). pvl_calcparams_desoto no longer computes and applies a spectral mismatch modifier.
[x] Changed pvl_calcparams_desoto to remove the requirement that all inputs be vectors of the same length. Inputs S and Tcell can be vectors of the same length; all other inputs should be scalars.
[x] Changed pvl_erbs, pvl_louche, pvl_orgill_hollands, pvl_reindl_1, and pvl_reindl_2 to output DNI, DHI and Kt, and to clarify each model’s description.
[ ] Corrected description of pvl_kingdiffuse to clarify that the King diffuse model estimates total plane-of-array diffuse (sky diffuse and ground reflected irradiance).
[x] Added CEC module library and inverter library from SAM2015.6.30 in .csv format and in .mat format, along with scripts to read the .csv files and write the .mat files.

Mar 18 '16 22:03 wholmgren

I intend to create a function to calculate the sandia inverter coefficients from datasheet and CEC efficiency information. I was planning to use Santa Clara as my motivation to get it done, either before or during.

I think it would be considered another in the parameter_estimation set of functions?

On Fri, Mar 18, 2016 at 3:39 PM, Will Holmgren [email protected] wrote:

In anticipation of the upcoming Santa Clara workshop, I'm consolidating the lists in the comments above into a new list. I also removed some of the items that don't apply to python. It's probably best to start making new issues for specific features.

pvl_louche - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the LOUCHE model

pvl_orgill_hollands - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Orgill and Hollands model

pvl_erbs - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Erbs model. And from v1.3: Corrected pvl_erbs; the coefficient of K_t^2 changed from 4.3888 to 4.388

pvl_reindl_1 - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Reindl 1 model

pvl_reindl_2 - Estimate Direct Normal Irradiance from Global Horizontal Irradiance using the Reindl 2 model

pvl_martinruiziam - Determine the incidence angle modifier using the Martin and Ruiz incident angle model

pvl_adrinverter - Anton Driesse's Grid-Connected PV Inverter

pvl_PVsyst_parameter_estimation - Estimates parameters for the PVsyst version 6 module performance model.

pvl_desoto_parameter_estimation - Estimates parameters for the De Soto single diode module performance model.

pvl_rectify_IV_curve - Ensures that Isc and Voc are included in a IV curve and removes duplicate voltage and current points.

pvl_calcparams_CEC - Create module performance model coefficients for the single diode model used by the CEC.

pvl_calcparams_PVsyst - Create module performance model coefficient for the single diode model in PVsyst version 6.

pvl_huld - Calculates DC power using the Huld PV module model.

pvl_calcPwat - Calculate precipitable water (cm) from ambient air temperature (C) and relatively humidity (%). see #115 https://github.com/pvlib/pvlib-python/pull/115.

pvl_FSspeccorr - Calculate spectral mismatch modifier based on precipitable water and absolute airmass. see #115 https://github.com/pvlib/pvlib-python/pull/115.

pvl_getISDdata - Fetch data from NOAA ISD at ftp.ncdc.noaa.gov.

pvl_readISH - Read data fetched from ftp.ncdc.noaa.gov into a table.

Changed pvl_calcparams_desoto to require effective irradiance as its input, rather than absorbed irradiance (i.e., broadband irradiance reaching a module's cells). pvl_calcparams_desoto no longer computes and applies a spectral mismatch modifier.

Changed pvl_calcparams_desoto to remove the requirement that all inputs be vectors of the same length. Inputs S and Tcell can be vectors of the same length; all other inputs should be scalars.

Changed pvl_erbs, pvl_louche, pvl_orgill_hollands, pvl_reindl_1, and pvl_reindl_2 to output DNI, DHI and Kt, and to clarify each model’s description.

Corrected description of pvl_kingdiffuse to clarify that the King diffuse model estimates total plane-of-array diffuse (sky diffuse and ground reflected irradiance).

Added CEC module library and inverter library from SAM2015.6.30 in .csv format and in .mat format, along with scripts to read the .csv files and write the .mat files.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/pvlib/pvlib-python/issues/2#issuecomment-198569169

Mar 18 '16 23:03 jforbess

Absolutely. In fact I have some matlab code already but it's not in pvlib format yet.

Mar 19 '16 00:03 cwhanse

@jforbess that sounds great. I suggest creating a new issue if you'd like to discuss it further.

Mar 19 '16 02:03 wholmgren

Just wanted to let folks know that the Matlab help files are available at a new location on the PVPMC website: https://pvpmc.sandia.gov/PVLIB_Matlab_Help/

I have been updating and cleaning up the website and several old links no longer work. Please let me know if you find any problems.

Mar 21 '16 14:03 jsstein

Thanks @jsstein, I'll add a link to this page from our documentation.

Mar 21 '16 15:03 wholmgren

I suggest we close this issue and open more specific ones when needed.

Apr 03 '23 15:04 adriesse

Of the remaining items, Huld's DC model and perhaps the read ISD/ISH functions are worth considering. I wouldn't object to adding the Orgill and Hollands model. I would consider removing pvlib.irradiance.king since there will never be an archival publication to reference.

Apr 03 '23 15:04 cwhanse

PVGIS is using Huld model. What data are in ISD/ISH? Is it just rain & snow data? How are these data archived? API, FTP, or HTTP? Maybe this could be part of iotools? What about GSOD data?

Apr 03 '23 18:04 mikofski

ISD is global data primarily for aviation. Sometimes (not common) there is an irradiance sensor, but mostly I've used it for air temperature and wind. https://www.ncei.noaa.gov/products/land-based-station/integrated-surface-database

Apr 03 '23 18:04 cwhanse

Issues for ISD and GSOD: #759 #668

I'm going to close this but other maintainers can reopen it if they feel it still has value.

Apr 03 '23 19:04 wholmgren

I feel that we should have some kind of distributed celebration for closing the oldest issue.

Apr 03 '23 21:04 cwhanse