You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using BCVTB the ExternalInterface:Actuator can be left with empty initial value, meaning we don't want to overwrite the simulation default values. However, when using energyplus as a FMU it will complain that the initial value is a required field.
This forces the user to define some constant value during the warmup, which might not be ideal in cases where the actuator is controlling highly dynamic properties like ventilation.
Is this on purpose? Or is it a constraint from the setup as FMU?
Thank you beforehand!
The text was updated successfully, but these errors were encountered:
Hi!
When using BCVTB the ExternalInterface:Actuator can be left with empty initial value, meaning we don't want to overwrite the simulation default values. However, when using energyplus as a FMU it will complain that the initial value is a required field.
This forces the user to define some constant value during the warmup, which might not be ideal in cases where the actuator is controlling highly dynamic properties like ventilation.
Is this on purpose? Or is it a constraint from the setup as FMU?
Thank you beforehand!
The text was updated successfully, but these errors were encountered: