Skip to content

add missing area parameter for eta_m arg #1182

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

Merged
merged 7 commits into from
Mar 5, 2021
Merged

add missing area parameter for eta_m arg #1182

merged 7 commits into from
Mar 5, 2021

Conversation

KushalBeniwal
Copy link
Contributor

@KushalBeniwal KushalBeniwal commented Mar 3, 2021

Before:
Screenshot (1)

After:
Screenshot (2)

@mikofski
Copy link
Member

mikofski commented Mar 3, 2021

Hi @KushalBeniwal, can you check stickler? also what do you think about formatting the math using latex so it looks better? Thx!

@KushalBeniwal
Copy link
Contributor Author

Screenshot (6)
This is what it looks like now.

Copy link
Member

@cwhanse cwhanse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't believe that formula is correct. External module efficiency is based on total module area, including gaps between cells, rather than total cell area.

Co-authored-by: Cliff Hansen <cwhanse@sandia.gov>
@mikofski
Copy link
Member

mikofski commented Mar 4, 2021

@KushalBeniwal Sorry, I think we should remove the underscores. Also what would it look like if we use \frac {} {}? EG: something like this:
external efficiency
or more tersely:
external efficiency tersely
where SUM(P_dc) is the total DC power, POA_global is the global irradiance in the plane of the array, and SUM(A_module) is the total module surface area.

@cwhanse any preference?

@cwhanse
Copy link
Member

cwhanse commented Mar 4, 2021

@cwhanse any preference?

@mikofski you aren't wrong - the DC power and area need to match. But I think it's confusing, and out of synch with the rest of pvlib, to have this function ask for a parameter based on array scale values, rather than single module values. E.g. all the methods in PVSystem and ModelChain calculate DC power for a single module. I think the cell temperature functions should do likewise.

I don't being formal with the equation adds value here. One can't use the output of the DC model as input to this temperature function (it's circular) so I wouldn't use pvlib variable names to avoid suggesting that's what is needed.

I guess I'd prefer the text formula "DC power / (POA irradiance x module area)". OK with me if you'd prefer to render that using LateX, as "P_{DC} / (G_{POA} \times Area}" and then defining each of the three terms.

Sorry @KushalBeniwal that we're having a bit of back and forth on this.

@mikofski
Copy link
Member

mikofski commented Mar 4, 2021

Agreed. Let's drop the word "total" & keep it at the module (as in PV panel, not a Python "module") level

@KushalBeniwal
Copy link
Contributor Author

Sorry @KushalBeniwal that we're having a bit of back and forth on this.

Not an issue.
I should have first asked for your opinion before making any changes.

@KushalBeniwal
Copy link
Contributor Author

I tried both, so, which one looks better or should I try something else?

  1. Screenshot (7)
  2. Screenshot (9)
    Is "Area" fine or should I put {A}_module?

@mikofski
Copy link
Member

mikofski commented Mar 5, 2021

My vote's on 1.

@cwhanse
Copy link
Member

cwhanse commented Mar 5, 2021

My vote's on 1.

Mine also.

@mikofski mikofski merged commit dc617d0 into pvlib:master Mar 5, 2021
@mikofski
Copy link
Member

mikofski commented Mar 5, 2021

Thanks @KushalBeniwal !

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

Successfully merging this pull request may close these issues.

pvsyst cell temp docs for eta_m arg missing "area" from definition
3 participants