Closed caseyzak24 closed 1 year ago
Hi @caseyzak24, I'm looking into this now, but suspect that you may need to define all of those subarray2, subarray3, and subarray4 inputs even if those subarrays are not enabled.
@caseyzak24 We added some input checks to pvsamv1 that are supposed to help make sure inputs are correctly assigned. For example, to ensure that subarray2_tilt
is correctly assigned based on the value of subarray2_enable
and subarray2_track_mode
. It looks like some of those checks are incorrect, causing the "check fail" error messages you are seeing.
We will fix this for the next update. For now, the workaround is to set inputs for all of the subarrays even if they are not enabled.
Thanks Paul,
Will you ref this issue when you make that update? I just want to make sure we get on that fixed version ASAP.
This is fixed in #1062.
Note that for scripts based on versions of SSC greater than 274 (newer than SAM 2021.12.02 Revision 2, PySAM 3.0.2), the following new pvsamv1 variables are required for Subarray 1:
subarray1_rear_soiling_loss
(number)subarray1_rack_shading
(number)subarray1_electrical_mismatch
(number)And for SSC > 280 (newer than SAM 2022.11.21 Revision 3, PySAM 4.2.0), the format of the adjust
input has changed:
adjust_constant
, changed from adjust:constant
.dc_adjust_constant
, changed from dc_adjust:constant
.
I recently upgraded from the latest 3.0.2 version to 4.2.0 and attempted to run a pvsamv1 model. Here is the result of
model.export()
prior to calling to callingmodel.execute(0)
:When I call
model.execute(0)
I get the following error:This same model definition ran successfully on pysam 3.0.2 with the only exception being that the new bifacial-related inputs in
model.Losses
were replaced withsubarray1_rear_irradiance_loss
.As you can see in the model definition,
subarray2_enable
is set to zero, so I'm not sure why track_mode and monthly_tilt are being referenced for subarray 2 in the error message. The latest docs say thatsubarray2_enable
depends on a large number of inverter and module inputs, but it doesn't mention how it depends on these factors. If pysam is now forcingsubarray2_enable
to be active under certain conditions (I could see it depending on sizing considerations), then apologies for raising a usage question as an issue; but as far as I can tell this is a bug.