Add advanced bifacial PV and ground irradiance modeling#1152
Conversation
mjprilliman
left a comment
There was a problem hiding this comment.
-
UI is a bit confusing because when weather file albedo checkbox is checked, spatial albedo uses weather file albedo and UI inputs in matrix do not apply. Is this intended behavior?
-
Both spatial and single-value rear POA reported in outputs when spatial data is used. Single-value appears to be average of the spatial data. Will users get confused on this?

-
Can these variable names indicate that they apply to the rear surface?

-I guess it makes sense to average bifacial electrical mismatch over all subarrays (all in one output)?
This is what I found so far in SAM, still working through ssc.
It is the intended behavior. If "Use albedo from weather file if available" is checked, then the (single) albedo from the weather file is used if present, on a timestep-by-timestep basis. If an albedo value is missing in the weather file for a given timestep, then the spatial albedo is used (if "Use spatial monthly albedo values" is selected). I could see this functionality being useful for parametric studies of different years or locations that include differences in snow cover or crop harvesting (which can also occur at a sub-monthly fidelity). This will be explained in the help, but if this feature is too confusing, it can just be removed. @janinefreeman ? @cpaulgilman ? |
|
Yes, done. |
Thank you @mjprilliman ! |
I'm fine with leaving the variables as they are just wanted to talk it through. |
Let's keep this as is for now, and I will address this and some other albedo confusion in https://github.com/NREL/SAM/tree/pv-albedo-fix. |
Those "POA irradiance after..." outputs are confusing -- I think that should be addressed separately. (I think it might be clearer to show a single POA irradiance value and show the losses instead of a series of reduced POA values.) |
Dependencies
/Matthew-Boyd/wex:bifacial
/Matthew-Boyd/ssc:bifacial
Description
Adds:
Type of change
Please delete options that are not relevant.
Checklist:
If you have added a new compute module in a SSC pull request related to this one, be sure to check the Process Requirements.