Skip to content

Conditional battery inputs in UI for BTM, FOM, standalone, PV, Generic configurations #798

@cpaulgilman

Description

@cpaulgilman

1. Battery Voltage UI

Battery voltage model option batt_voltage_choice and voltage table batt_voltage_matrix does not update when battery type changed. For example:

  1. Open default PV Battery / Single Owner case.
  2. Change voltage model from electrochemical model to voltage table.
  3. Change battery type to a vanadium flow battery.

2. Standalone Battery

Disable "Minimum time at charge state" under Charge Limits and Priority?

Are all dispatch options available for standalone battery? If not, for now, use msgbox() in UI when user chooses an invalid option for now.

3. Generic Battery with Custom Weather File

UI callback error for Generic Battery / Single Owner with Automated dispatch and Look ahead to custom weather file. Should 1) display msgbox() with "Look ahead to custom weather file is only available for system systems with a photovoltaic array." 2) Disable batt_select_weather_file_forecast and batt_user_specified_weather_file Browse button and weather file input field.

Could not evaluate callback function:batt_select_weather_file_forecast->on_change
[27]: eval error in statement list
[27]: error inside function call
[30]: eval error in statement list

4. Generic Battery with PV Smoothing

For generic battery, msgbox() when PV smoothing selected, or allow when generation profile option enables with 15-minute or less time step data.

5. FOM Automated Dispatch with Specify IRR

SSC should throw an error for this option. Until we make that change, show message on both Battery Dispatch and Revenue (or Financial Parameters for partnership flip and sale leaseback) when user chooses automated dispatch option while in Specify IRR mode (or chooses Specify IRR while in Automatic dispatch mode). Consider using yesno() instead of msgbox() to prompt user to automatically change mode from Specify IRR to Specify PPA price.

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