-
Notifications
You must be signed in to change notification settings - Fork 1.1k
how to organize loss functions #891
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
Comments
Hi Will, I tend to be about looser on definitions about what losses are and am perfectly happy to accept a temperature loss. For example under a given irradiance, ambient and windspeed the temperature could be affected by things that can be changed such as insulating the back of a module, putting fins on or even water cooling. Similarly there are losses due to the series resistance of a module and shunt resistances, neither of which we can do much about but they are losses nevertheless. The Loss Factors model identifies about 12 losses to do with the module IV curve and physical parameters. |
IMO it would be really awesome if we could get the LFM in pvlib. |
I'm working on it at the moment ! I hope to talk about it and demonstrate it in Salt Lake City |
Are we able to decide a way forward on this question, i.e., to keep Deciding is the roadblock to merging #764 |
+1 |
Hearing no votes for retaining |
Originally posted by @cwhanse in #764
Nice metaphor.
Editorial: Let me just state that I think the PVsyst-style "loss diagrams" do somewhat of a disservice, by applying the term "loss" to quantities of energy that couldn't have been generated in the first place. An example that's not a loss (IMO) is "temperature loss"; the physical reality is that cells are less efficient at higher temperature and hot air happens. There's only a "temperature loss" if the PV system could operate at lower temperature but doesn't.
If we follow the modeling process diagram, which is a guide not a rule, a module
dc_losses
could contain functions for wiring and mismatch losses, but not soiling, since soiling applies to irradiance not DC current. Debatable whethersnow_coverage
is an effect on DC current or on irradiance.It seems that pvlib will have multiple modules
soiling.py
,snow.py
,mismatch.py
ordc_losses.py
etc. at some level, and the question is about grouping these modules into alosses
folder, or not. @wholmgren's question suggests we should agree on a list of these modules, and maybe it will become more clear where to place them.Here's an attempt to list categories for functions that could be broadly termed losses using my view of that term:
The text was updated successfully, but these errors were encountered: