-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add gallery example for cross-axis slope backtracking #1077
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
Changes from 1 commit
f673ac5
64785ad
f84fb40
0da0d0f
6662505
9d24f61
3b75bb3
fe20f01
e1b4650
186232c
3320e19
cbb8fd1
5dd6d46
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||
---|---|---|---|---|---|---|---|---|
@@ -0,0 +1,122 @@ | ||||||||
""" | ||||||||
Backtracking on sloped terrain | ||||||||
============================== | ||||||||
|
||||||||
Modeling backtracking for single-axis tracker arrays built on sloped terrain. | ||||||||
""" | ||||||||
|
||||||||
# %% | ||||||||
# Tracker systems avoid row-to-row shading when the sun is low in the sky | ||||||||
# by backtracking. The backtracking strategy orients the modules exactly | ||||||||
# on the boundary between shaded and unshaded so that the modules are oriented | ||||||||
# as much towards the sun as possible while still remaining unshaded. | ||||||||
# Unlike the truetracking calculation (which only depends on solar position), | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is "truetracking" (one word) widely accepted? I'd probably write true-tracking even at the cost of inconsistency with backtracking. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The existing single-axis tracker example uses the hyphenated version. |
||||||||
# calculating the backtracking angle requires knowledge of the relative spacing | ||||||||
# of adjacent tracker rows. This example shows how the backtracking angle | ||||||||
# changes based on a vertical offset between rows caused by sloped terrain. | ||||||||
# It uses :py:func:`pvlib.tracking.calc_axis_tilt` and | ||||||||
# :py:func:`pvlib.tracking.calc_cross_axis_tilt` to calculate the necessary | ||||||||
# array geometry parameters and :py:func:`pvlib.tracking.singleaxis` to | ||||||||
# calculate the backtracking angles. | ||||||||
# | ||||||||
# First, let's plot the simple case where the tracker axes are at right angles | ||||||||
# to the direction of the slope. In this case, the cross-axis tilt angle | ||||||||
# is the same as the slope of the terrain and the tracker axis itself is | ||||||||
# horizontal. | ||||||||
|
||||||||
from pvlib import solarposition, tracking | ||||||||
import pandas as pd | ||||||||
import matplotlib.pyplot as plt | ||||||||
|
||||||||
# PV system parameters | ||||||||
tz = 'US/Eastern' | ||||||||
lat, lon = 40, -80 | ||||||||
gcr = 0.4 | ||||||||
|
||||||||
# calculate the solar position | ||||||||
times = pd.date_range('2019-01-01 06:00', '2019-01-01 18:00', closed='left', | ||||||||
freq='1min', tz=tz) | ||||||||
solpos = solarposition.get_solarposition(times, lat, lon) | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The rendered version has some weird syntax highlighting inconsistencies. I don't see anything wrong so probably safe to ignore. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If you're talking about things being rendered blue-ish with clickable links, I think that's the intersphinx linking: https://sphinx-gallery.github.io/stable/configuration.html#add-intersphinx-links-to-your-examples Future improvement: configure pvlib functions to link as well, or disable it for everything, for consistency. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||||||||
|
||||||||
# compare the backtracking angle at various terrain slopes | ||||||||
fig, ax = plt.subplots() | ||||||||
for cross_axis_tilt in [0, 5, 10]: | ||||||||
tracker_data = tracking.singleaxis( | ||||||||
apparent_zenith=solpos['apparent_zenith'], | ||||||||
apparent_azimuth=solpos['azimuth'], | ||||||||
axis_tilt=0, # flat because the axis is perpendicular to the slope | ||||||||
axis_azimuth=180, # N-S axis, azimuth facing south | ||||||||
max_angle=90, | ||||||||
backtrack=True, | ||||||||
gcr=gcr, | ||||||||
cross_axis_tilt=cross_axis_tilt) | ||||||||
|
||||||||
backtracking_position = tracker_data['tracker_theta'].fillna(0) | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||
label = r'$\beta_c$: {}°'.format(cross_axis_tilt) | ||||||||
backtracking_position.plot(label=label, ax=ax) | ||||||||
|
||||||||
plt.legend() | ||||||||
plt.title('Backtracking Curves') | ||||||||
plt.show() | ||||||||
|
||||||||
# %% | ||||||||
# This plot shows how backtracking changes based on the slope between rows. | ||||||||
# For example, unlike the flat-terrain backtracking curve, the sloped-terrain | ||||||||
# curves do not approach zero at the end of the day. Because of the vertical | ||||||||
# offset between rows introduced by the sloped terrain, the trackers can be | ||||||||
# slightly tilted without shading each other: | ||||||||
# | ||||||||
# TODO: RHR image | ||||||||
# | ||||||||
# TODO: talk about RHR | ||||||||
# | ||||||||
# Now let's examine the general case where the terrain slope makes an | ||||||||
# inconvenient angle to the tracker axes. For example, consider an array | ||||||||
# with north-south axes on terrain that slopes down to the south-south-east. | ||||||||
# Assuming the axes are installed parallel to the ground, the northern ends | ||||||||
# of the axes will be higher than the southern ends. But because the slope | ||||||||
# isn't purely parallel or perpendicular to the axes, the axis tilt and | ||||||||
# cross-axis tilt angles are not immediately obvious. We can use pvlib | ||||||||
# to calculate them for us: | ||||||||
|
||||||||
slope_azimuth = 155 # terrain slopes down to the south-south-east | ||||||||
slope_tilt = 10 # terrain is sloped at 10 degrees from horizontal | ||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm confused at this point. The slope direction is 155 azimuth, but, the tilt is 10 degrees relative to what? Is it 10 degrees rotation relative to the tracker azimuth of 180? That seems an odd choice, since it is difficult to measure the slope tilt except relative to the slope azimuth. If slope_tilt is 10 degrees relative to horizontal along slope_azimuth, then I'd suggest
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Correct, but I think your suggested comment has the wrong sign. It's either upwards 10 degrees away from slope_azimuth, or downward 10 degrees towards it. Are you okay with this revision?
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. slope_azimuth is chosen in the downslope direction? I may have missed that if it's earlier in the text. If not, would be good to add. If slope_azimuth is always downslope, then I think it may be more clear to describe slope_tilt in the direction of slope_azimuth, i.e., always negative. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for your patience with this reviewer There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Changes made. As always, I am grateful for the review :) |
||||||||
axis_azimuth = 180 # tracker axis is still N-S | ||||||||
|
||||||||
# calculate the tracker axis tilt, assuming that the axis follows the terrain: | ||||||||
axis_tilt = tracking.calc_axis_tilt(slope_azimuth, slope_tilt, axis_azimuth) | ||||||||
|
||||||||
# calculate the cross-axis tilt: | ||||||||
cross_axis_tilt = tracking.calc_cross_axis_tilt(slope_azimuth, | ||||||||
slope_tilt, | ||||||||
axis_azimuth, | ||||||||
axis_tilt) | ||||||||
|
||||||||
print('Axis tilt:', '{:0.01f}°'.format(axis_tilt)) | ||||||||
print('Cross-axis tilt:', '{:0.01f}°'.format(cross_axis_tilt)) | ||||||||
|
||||||||
# %% | ||||||||
# And now we can pass use these values to generate the tracker curve as | ||||||||
# before: | ||||||||
|
||||||||
tracker_data = tracking.singleaxis( | ||||||||
apparent_zenith=solpos['apparent_zenith'], | ||||||||
apparent_azimuth=solpos['azimuth'], | ||||||||
axis_tilt=axis_tilt, # no longer flat because the terrain imparts a tilt | ||||||||
axis_azimuth=axis_azimuth, | ||||||||
max_angle=90, | ||||||||
backtrack=True, | ||||||||
gcr=gcr, | ||||||||
cross_axis_tilt=cross_axis_tilt) | ||||||||
|
||||||||
backtracking_position = tracker_data['tracker_theta'].fillna(0) | ||||||||
backtracking_position.plot() | ||||||||
|
||||||||
title_template = 'Axis tilt: {:0.01f}° Cross-axis tilt: {:0.01f}°' | ||||||||
plt.title(title_template.format(axis_tilt, cross_axis_tilt)) | ||||||||
plt.show() | ||||||||
|
||||||||
# %% | ||||||||
# Note that the backtracking curve is roughly mirrored compared with the | ||||||||
# earlier example -- it is because the terrain is now sloped somewhat to the | ||||||||
# east instead of west. |
Uh oh!
There was an error while loading. Please reload this page.