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
Control functions (CF) are an essential part of basically all setups described by HTD. However, even though the original HTD templates provide space for describing CFs, they do not encourage users to make this in a structured way.
Hence, I would like to propose to add to the HTD an optional template for CFs. This could for instance be based on an adapted version of the CF template from the PreCISE approach (refer to Deliverable 3.2 from SmILES project for details), which provides a structured approach for describing CFs. For setups with complex controllers, this could be added as an attachment to an HTD description.
Control functions (CF) are an essential part of basically all setups described by HTD. However, even though the original HTD templates provide space for describing CFs, they do not encourage users to make this in a structured way.
Hence, I would like to propose to add to the HTD an optional template for CFs. This could for instance be based on an adapted version of the CF template from the PreCISE approach (refer to Deliverable 3.2 from SmILES project for details), which provides a structured approach for describing CFs. For setups with complex controllers, this could be added as an attachment to an HTD description.
An example of how this could look like comes from the JRA1 benchmarks, e.g., the CF description of the multi-energy networks benchmark
The text was updated successfully, but these errors were encountered: