Skip to content

Invalid energy charge table with different numbers of tiers causes exec fail #875

@cpaulgilman

Description

@cpaulgilman

See email conversation below for description.

Example file:
billing-demand-no-demand-charges.zip

Notes:

Paul,

The issue there is exclusively confined to the energy charge table, if I uncheck the billing demand options I still get the error. With the way SAM handles TOU rates and tiers (and likely the way that these are handled generally) the rate you’ve sent is invalid due to periods 1 and 2 having different numbers of tiers. I reformatted the rate to trigger the error I think you’re thinking about, below:

exec fail(utilityrate5): The ur_dc_billing_demand_periods matrix should have 0 rows, to match the number of TOU periods. Instead it has 2 rows.
Simulation utilityrate5 failed :exec fail(utilityrate5): The ur_dc_billing_demand_periods matrix should have 0 rows, to match the number of TOU periods. Instead it has 2 rows.
SSC requires input 'year1_hourly_ec_with_system', but was not found in the SAM UI or from previous simulations
Simulation cashloan failed :precheck input: variable 'year1_hourly_ec_with_system' (Energy charge with system (year 1 hourly)) required but not assigned

I took a look at the code, and unfortunately the ur_dc_billing_demand_periods matrix is tied up in the billing demand calculations (which is a bug), so simply not throwing the error is not an option. Please file an issue, and I’ll add this to my list for patch 1 to fix.

Brian

Hi Brian,

The attached file uses kWh/kW units for a tiered energy rate. It causes an SSC error because the billing demand by TOU period table has a different number of periods than the TOU demand rate table for demand charges. However, demand charges are disabled.

Should this error be disabled when demand charges are disabled? If so, I can create an issue.

I could also make the UI text dynamic to suggest the correct number of rows and period numbers based on the demand charge table

Thanks,
Paul.

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions