-
Notifications
You must be signed in to change notification settings - Fork 1k
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
ENH: infinite sheds #717
ENH: infinite sheds #717
Conversation
* add _to_radians and is_rad to convert only if necessary * prefix all functions with get_ * add get_f_sky_pv, get_poa_sky_pv, get_ground_angle_tangent, get_f_gnd_pv, get_f_gnd_pv, get_poa_gnd_pv, etc. * update API ui Signed-off-by: Mark Mikofski <[email protected]>
* get_irradiance, output ordered dict or dataframe * finish updating get_poa_global_bifacial to transpose beam and diffuse for each side separately
…ion" - use tan(zenith) in solar projection math latex - implement gcr_prime and ground-sky-angles calculations - add stub for ground-diffuse view factor Signed-off-by: Mark Mikofski <[email protected]>
- calculate ground-sky angles to previous and next rows, assuming height is nonzero - calculate limits on ground where it can see the sky - calculate the view factor as a function of z on the ground to the sky - fix places where it still says degrees, bad, no! - add fixme for pv-sky view factor, still has wrong formula - add tests for angles from point z on the ground to tops of current row, and limits of previous and next rows - add a script to make the plot of ground-sky view factor versus z
@wholmgren FYI: looks like pandas and other versions not supported by python-3.5, not sure? |
- add comments, change names x->z - add TODO's to limit number of rows, and set row-type: 'first', 'last', or 'middle'
- was difference of angles, should be difference of cosines - also add TODO's to return VF versus point x on panel, and don't use averages
Cliff mentioned that in the ivtools pr (I think). I haven’t had a chance to
look into it. Probably should be addressed in a separate pr.
…On Wed, Jul 3, 2019 at 5:38 PM Mark Mikofski ***@***.***> wrote:
@wholmgren <https://github.com/wholmgren> FYI: looks like pandas and
other versions not supported by python-3.5
<https://travis-ci.org/pvlib/pvlib-python/jobs/554012857#L379>, not sure?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#717?email_source=notifications&email_token=ABBOER75RFF75U7MYDRY3DLP5VBAFA5CNFSM4HMBP67KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZGAEYQ#issuecomment-508297826>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABBOER4OIOK4O57A5QKOCZLP5VBAFANCNFSM4HMBP67A>
.
|
- change calc_fx_sky to calc_fz_sky since z is for ground and x is for pv surface - add docstring to calc_fz_sky and for ground_sky_diffuse_view_factor
Co-authored-by: Mark Mikofski <[email protected]>
Co-authored-by: Mark Mikofski <[email protected]>
Terminology issue: pvlib isn't consistent in terms referring to solar zenith and solar azimuth. The last set of changes here renamed two parameters: So pvlib isn't consistent in these terms, and in places is not specific. With that in mind I'm going to open a discussion about the |
In my own code have standardized on |
I think this is ready to merge. @wholmgren wanna do the honors? |
If no one has any objections I'll merge this today, COB, okay? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mikofski thanks, I forgot about this, but I'll let you do the honors when ready. My comments are not blockers.
@@ -0,0 +1,831 @@ | |||
r""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a nice module docstring, but I don't think it's rendered anywhere. Did I miss it? I don't recall rendering any module docstrings (for better or worse). I do recall that it might not be super simple for our current documentation strategy. If so, perhaps the doc string could be copied into another place, like a new bifacial.rst or an example gallery py file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cwhanse any comment on this? Seems like a good idea to me. I happy to move it if you agree. thx.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to bifacial.rst
pvlib/bifacial/infinite_sheds.py
Outdated
def get_irradiance_poa(surface_tilt, surface_azimuth, apparent_zenith, | ||
azimuth, gcr, height, pitch, ghi, dhi, dni, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given where #1403 is going, I suggest we go with solar_zenith
and solar_azimuth
like we do here
pvlib-python/pvlib/irradiance.py
Lines 304 to 305 in c0c46b4
def get_total_irradiance(surface_tilt, surface_azimuth, | |
solar_zenith, solar_azimuth, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we wait until after #1403 is closed to merge this PR?
pvlib/bifacial/infinite_sheds.py
Outdated
|
||
Returns | ||
------- | ||
output : OrderedDict or DataFrame |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few years later, perhaps we just go with dict
instead of OrderedDict
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wholmgren do you mean change only the docstring, or replace the use of OrderedDict
with {}
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace the use
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few sphinx rendering issues
Co-authored-by: Kevin Anderson <[email protected]>
Co-authored-by: Kevin Anderson <[email protected]>
@wholmgren @kanderso-nrel I think I have addressed all comments. I'm satisfied that this PR is ready to merge. @mikofski want the honor of pushing the big green button? |
surface_azimuth) | ||
f_gnd_beam = 1.0 - np.minimum( | ||
1.0, gcr * np.abs(cosd(surface_tilt) + sind(surface_tilt) * tan_phi)) | ||
np.where(solar_zenith > max_zenith, 0., f_gnd_beam) # [1], Eq. 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mikofski I think this line has no effect as there is no return value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a point, well spotted @kdebrab ! Would you like to open a PR fixing it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line is probably supposed to start with f_gnd_beam =
and clip it at max zenith so values don’t blow up.
ICYMI @cwhanse @kandersolar
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @mikofski, that was the intent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these lines are still unchanged in main:
f_gnd_beam = 1.0 - np.minimum(
1.0, gcr * np.abs(cosd(surface_tilt) + sind(surface_tilt) * tan_phi))
np.where(solar_zenith > max_zenith, 0., f_gnd_beam) # [1], Eq. 4
return f_gnd_beam # 1 - min(1, abs()) < 1 always
was a PR forthcoming?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mikofski has not been fixed, should have its own issue.
[ ] Closes issue #xxxxdocs/sphinx/source/api.rst
for API changes.docs/sphinx/source/whatsnew
file for all changes.Implements "infinite sheds" model for irradiance on long, regular bifacial array (fixed or single-axis tracked) on horizontal ground.