Hyperlinking code formatted text doesn't work great, e.g., pvlib.module.function doesn't look very much like a hyperlink to the user. Instead, I recommend explicitly adding the link: pvlib.module.function (link to documentation).
Several participants asked why the year was 1990. If using TMY data, then there should be at least one slide explaining what a TMY is.
Consider using NASA POWER dataset as this gives near-real time irradiance and has the three components.
The fact that the tracker angles are nan at night, results in the funky feature where the power output is never zero (because it's nan):
Using .head() confused several participants.
We should consider not using pvlib's pvlib.location.Location object as it seems a bit of magic to several users. I think manually passing in latitude/longitude and timestamps to the function pvlib.solarposition.get_solarposition is better educationally.
Hyperlinking code formatted text doesn't work great, e.g.,
pvlib.module.functiondoesn't look very much like a hyperlink to the user. Instead, I recommend explicitly adding the link:pvlib.module.function(link to documentation).Several participants asked why the year was 1990. If using TMY data, then there should be at least one slide explaining what a TMY is.
Consider using NASA POWER dataset as this gives near-real time irradiance and has the three components.
The fact that the tracker angles are nan at night, results in the funky feature where the power output is never zero (because it's nan):
Using
.head()confused several participants.We should consider not using pvlib's
pvlib.location.Locationobject as it seems a bit of magic to several users. I think manually passing in latitude/longitude and timestamps to the functionpvlib.solarposition.get_solarpositionis better educationally.