Dear Farhan,
First, please make sure that you are using the same version of SSC in your API calls that SAM is using. To see the SSC version number for SAM, open the Help browser and click
About.
It is possible that the inputs in SAM are not identical to the inputs in your code. You can press the Shift-F5 key in SAM to generate an LK script that lists all of the SSC input variables and their values.
You can use the
variable to read your own shading data. For example, if you have an 8760 column of beam shading losses stored in a variable called
for Subarray 2, you would assign it as follows (in LK script):
var( 'subarray2_shading:hourly' , shading_losses )
Similarly, you can assign month-by-hour shading factors to
, and azimuth-by-altitude losses to
. Note that the number suffix to
determines which subarray the shading losses apply to.
Best regards,
Paul.