Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tutorial: system modeling #84

Closed
dacoex opened this issue Aug 20, 2015 · 13 comments
Closed

Tutorial: system modeling #84

dacoex opened this issue Aug 20, 2015 · 13 comments
Milestone

Comments

@dacoex
Copy link
Contributor

dacoex commented Aug 20, 2015

NOTE: no bug but clarification question.

Reading the tutorials is is unclear how inverter connections are defined and the power of a whole PV system of more than 1 string is calculated.

The notebook shows that 1 module is picked and then DC power calculated.
http://nbviewer.ipython.org/github/pvlib/pvlib-python/blob/master/docs/tutorials/tmy_to_power.ipynb#DC-power-using-SAPM

But the next step
http://nbviewer.ipython.org/github/pvlib/pvlib-python/blob/master/docs/tutorials/tmy_to_power.ipynb#AC-power-using-SAPM

uses a micro-inverter on module level.

How would the whole process be done with a different inverter, say a 30kW multi-string inverter?

And how would these then be added into a system of 500kW?

If it's roof-top, then multiplying by number of inverters would be possible but on a flat roof or ground mounted case, row-to-row spacing would need to be accounted for.

@dacoex dacoex changed the title Tutorilal: system modeling Tutorial: system modeling Aug 20, 2015
@wholmgren
Copy link
Member

Feel free to make PRs with improved tutorials.

@wholmgren wholmgren added this to the Someday milestone Aug 21, 2015
@dacoex
Copy link
Contributor Author

dacoex commented Aug 21, 2015

Well, that was the purpose of my comment: I am not really sure how it is done with pvlib.

Although I could see the potential applications already.

@wholmgren
Copy link
Member

There is currently no standardized way to do something like that in pvlib. Would be nice to see development in that direction.

@dacoex
Copy link
Contributor Author

dacoex commented Aug 25, 2015

Ok, so it means that your application of pvlib is rather for forecasting. There, single system is not that important but rather an upscale get of the typical behaviour, right?

My focus would be more system analysis.

Back to the topic: so the 30kW inverter would be simulated with a, say a number of 138 modules of 260Wp totalling to about 36kW.

So in section
http://nbviewer.ipython.org/github/pvlib/pvlib-python/blob/master/docs/tutorials/tmy_to_power.ipynb#AC-power-using-SAPM
One would have to manually add the strings to series and parallels, correct?

@jforbess
Copy link
Contributor

Yes, I have put together a dict that I use that expands the systemdef, and
perhaps it is time to wrap it into the systemdef dict, because it is pretty
unhelpful to define how many modules you have if you don't define which
kind of modules they are, or what kind of inverter you are using.

One more item on the todo list.

On Tue, Aug 25, 2015 at 2:32 PM, Data & Code Expert Experimenting with Code
on Data notifications@github.com wrote:

Ok, so it means that your application of pvlib is rather for forecasting.
There, single system is not that important but rather an upscale get of the
typical behaviour, right?

My focus would be more system analysis.

Back to the topic: so the 30kW inverter would be simulated with a, say a
number of 138 modules of 260Wp totalling to about 36kW.

So in section

http://nbviewer.ipython.org/github/pvlib/pvlib-python/blob/master/docs/tutorials/tmy_to_power.ipynb#AC-power-using-SAPM
One would have to manually add the strings to series and parallels,
correct?


Reply to this email directly or view it on GitHub
#84 (comment).

@jforbess
Copy link
Contributor

My dict isn't anywhere to be found in the pvlib code, in case it wasn't
clear.

On Tue, Aug 25, 2015 at 2:52 PM, Jessica Forbess jforbess@gmail.com wrote:

Yes, I have put together a dict that I use that expands the systemdef, and
perhaps it is time to wrap it into the systemdef dict, because it is pretty
unhelpful to define how many modules you have if you don't define which
kind of modules they are, or what kind of inverter you are using.

One more item on the todo list.

On Tue, Aug 25, 2015 at 2:32 PM, Data & Code Expert Experimenting with
Code on Data notifications@github.com wrote:

Ok, so it means that your application of pvlib is rather for forecasting.
There, single system is not that important but rather an upscale get of the
typical behaviour, right?

My focus would be more system analysis.

Back to the topic: so the 30kW inverter would be simulated with a, say a
number of 138 modules of 260Wp totalling to about 36kW.

So in section

http://nbviewer.ipython.org/github/pvlib/pvlib-python/blob/master/docs/tutorials/tmy_to_power.ipynb#AC-power-using-SAPM
One would have to manually add the strings to series and parallels,
correct?


Reply to this email directly or view it on GitHub
#84 (comment).

@wholmgren
Copy link
Member

Realistic system level modeling in pvlib needs expert help. I don't have the time or the expertise to do it right. There is discussion in #17 and #39 that is relevant.

And yes, upscaling small, idealized systems is fine for forecasting applications.

@dacoex
Copy link
Contributor Author

dacoex commented Aug 26, 2015

@jforbess
Would it be possible to see a demo of your dict in a notebook?

Realistic system level modeling in pvlib needs expert help. I don't have the time or the expertise to do it right.
Sure. But what I like about the lib is that it can help to understand inner workings of the system well.
So we could add a joint notebook of all interested in that part.

An example might be what statsmodels team did (https://github.com/statsmodels/statsmodels/). They'd compared their models & results with existing and established solutions:
https://groups.google.com/forum/#!searchin/pystatsmodels/stata

This can be done for pvlib with SAM:
https://sam.nrel.gov/sites/sam.nrel.gov/files/sam-webinars-2013-sdk.pdf
https://sam.nrel.gov/content/lk-vs-python

And yes, upscaling small, idealized systems is fine for forecasting applications.
Thanks for this confirmation. This helps to understand the motivation for the development focus.

@jforbess
Copy link
Contributor

I would be happy to share, once I clean it up from work I have done for a
client. Next week might be a good time for me to do that. Please feel free
to ping me again if it hasn't happened by Sept 8.

On Wed, Aug 26, 2015 at 4:40 AM, Data & Code Expert Experimenting with Code
on Data notifications@github.com wrote:

@jforbess https://github.com/jforbess
Would it be possible to see a demo of your dict in a notebook?

Realistic system level modeling in pvlib needs expert help. I don't have
the time or the expertise to do it right.
Sure. But what I like about the lib is that it can help to understand
inner workings of the system well.
So we could add a joint notebook of all interested in that part.

An example might be what statsmodels team did (
https://github.com/statsmodels/statsmodels/). They'd compared their
models & results with existing and established solutions:
https://groups.google.com/forum/#!searchin/pystatsmodels/stata

This can be done for pvlib with SAM:
https://sam.nrel.gov/sites/sam.nrel.gov/files/sam-webinars-2013-sdk.pdf
https://sam.nrel.gov/content/lk-vs-python

And yes, upscaling small, idealized systems is fine for forecasting
applications.
Thanks for this confirmation. This helps to understand the motivation for
the development focus.


Reply to this email directly or view it on GitHub
#84 (comment).

@wholmgren
Copy link
Member

@jforbess looking forward to seeing your ideas

@dacoex
Copy link
Contributor Author

dacoex commented Sep 22, 2015

see also:
https://github.com/oemof/feedinlib

@wholmgren
Copy link
Member

We've made a large number of documentation improvements since this issue was first created. There's no one thing I can point to that resolves this issue, but I think its sufficiently addressed by the combination of improvements. Still, we can always do better and I would welcome more specific issues and especially documentation pull requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants