When using ssc_auto_exec to call a cmod, we use ‘SIMULATION_PARAMETER’ to designate variables that the UI doesn’t provide to the cmod. It appears that all the variables that don’t have SIMULATION_PARAMETER are required to be in the UI, even if “required_if” is false.
For example, the following SSC branch currently contains exactly one new line of code in the mspt cmod that adds a new input var, “is_dispatch123”, that i) is not required, ii) does not have ‘SIMULATION_PARAMETER’ in UI Hints, iii) is not defined in the UI, iv) is not used anywhere in the cmod. The MSPT model will fail on open because it uses ssc_auto_exec on MSPT System Design. https://github.com/NREL/ssc/tree/add-temp-mspt_cmod_var
When using ssc_auto_exec to call a cmod, we use ‘SIMULATION_PARAMETER’ to designate variables that the UI doesn’t provide to the cmod. It appears that all the variables that don’t have SIMULATION_PARAMETER are required to be in the UI, even if “required_if” is false.
For example, the following SSC branch currently contains exactly one new line of code in the mspt cmod that adds a new input var, “is_dispatch123”, that i) is not required, ii) does not have ‘SIMULATION_PARAMETER’ in UI Hints, iii) is not defined in the UI, iv) is not used anywhere in the cmod. The MSPT model will fail on open because it uses ssc_auto_exec on MSPT System Design. https://github.com/NREL/ssc/tree/add-temp-mspt_cmod_var