Closed cpaulgilman closed 1 year ago
@cpaulgilman I created an SSC branch that should fix this (ssc_1015_errors_for_load_mismatch), however when using the test file above the errors are not triggered. The issue seems to be that while load_user_data
has 15 minute data, load
is still being passed to SSC as an 8760:
Do you have time to debug the callbacks and equations to see why that might be happening? I'll create a pull request once we get the expected behavior with the test file.
Yes, I'll look into the SAM UI side of things.
Callbacks should be fixed in https://github.com/NREL/SAM/tree/load_ui_checks.
Describe the bug
SAM UI checks added in https://github.com/NREL/SAM/pull/1390 display UI error messages when critical load and load data have different time steps, but SSC does not prevent simulation from running under this condition.
To Reproduce
On Data Tables tab of Results page, note that "Critical load in this timestep" and "Lifetime electricity load" are of correct length: Hourly critical load data is converted to 15-minute data.
Critical load data 60-minute input:
Resulting output, with 60-minute critical load data converted to 15-minute time steps:
Expected behavior I would expect a simulation message if time steps do not match, but perhaps the automatic conversion is the behavior we intended?