-
Notifications
You must be signed in to change notification settings - Fork 151
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
Add PV option to specify tilt angle as time series data #850
Comments
I'll add some additional thoughts on this. I've come across three specific cases related to misaligned trackers:
I think all of these could be covered pretty easily through a time series surface angle input, for example, by running SAM once, exporting modeled or ideal surface tilt ( |
Adding pvlib perspective on tracking capabilities from @kanderso-nrel: |
@janinefreeman I think minimum viable product here is to use functionality for seasonal tilt (monthly inputs) applied to nrecords per year array of user-specified tilt angles. This treats user-specified tilt angles as fixed tilt category for shading and other downstream calculations. This would essentially extend track_mode options by 1, or allow for flexibility in array size for seasonal tilt input. |
Closing per NREL/ssc#1071, outstanding work moved to #1543 |
SAM's PV models currently model fixed arrays with a constant tilt angle, and tracking arrays with surface angles calculated by the model in each time step based on the tilt and azimuth inputs and sun position.
For some modeling applications, it would be useful to be able to provide time series surface angles as input, for example to model advanced "smart" trackers, or misaligned trackers. The latter would make it possible to compare a system with misaligned trackers to one with "ideal" trackers, which would be useful for PV O&M teams to evaluate the impact of tracker problems on project economics.
Another approach would be to make the angle of incidence an input as suggested here: https://sam.nrel.gov/forum/forum-general/3702
See this feature request from June 2022: https://sam.nrel.gov/forum/forum-general/3914
The text was updated successfully, but these errors were encountered: