Diffuse Shade Loss Parameter for SDK

Hi,

I can see that a new diffuse shade loss factor has been added to the SDK. This number just seems to be a percentage input. How can this actually be calculated in the SDK based on the project and selecting subarray1_shade_mode=0 or is this not possible? Do we need to have a 3D shade model to be able to calculate this, or the hourly shading losses from the actual SAM program? If that is the case, it seems like the diffuse shade loss in the SDK will not be very useful, since we cannot generate hourly shading losses on the fly.

Another question, will the SDK automatically calculate and take off the subarray1_ss_derate and subarray1_ss_diffuse_derate? If the SAM SDK can automatically calculate diffuse shade loss (like in PVsyst), it would be most helpful for accurate automated modeling.

Any help or clarification regarding the diffuse shade loss in the pvsamv1 SDK would be much appreciated.

Thanks,
James

Thanks for the response.

I guess this confirms what I was thinking. Are there any plans to include a diffuse shade loss calculation inside of the pvsamv1 module? It would be most helpful, and allow the results from the SDK to be just as accurate (if not more) as the SAM program and other software (PVsyst).

I suppose the main goal is to just have diffuse shading, and self shadings (external shade structures are not a real concern) both accounted for in the model whether it is based on a 2D or 3D model for both fixed tilt and HSAT. I am not sure how the 3D shade model is performing the calculations (e.g. ray tracing?), so I don't know if the approach outlined below would work.

In the SDK, depending on the shading model chosen, we are already choosing the racking configuration for self shading, and the module dimensions are already included as variables. The only additional variables that I could see being required are the number of racks in x-direction, and number of rows.

From there, a shading scene could simply be constructed and/or calculated based on the module dimensions, rack configuration, # of racks, tilt, azimuth, number of rows, and GCR.

Hi Paul,

Any update on exposing an easier way to incorporate array self shading loss in the SDK?

I too am using the SDK as a automated tool and the largest discrepancy between SDK and other software (PVsyst) is that I can not easily represent self-shading losses. Like James says, external shading is not to much of a concern and most of the information for this to be calculated is already supplied to the SDK.

Best regards,
Stephen