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
Setups described by HTD are typically associated to some kind of input data (e.g., generation profiles). However, the HTD provides no means to distribute data in a consistent way. If any data is provided, there is no guarantee that a recipient of an HTD description has the knowledge or the tools to interpret this data.
Hence, I would like to define a format for attaching data to an HTD description. This could for instance be based on the data format used for the PreCISE approach (refer to Deliverable 3.3 from SmILES project for details), which provides a simple and machine-readable approach to share text-based data.
Setups described by HTD are typically associated to some kind of input data (e.g., generation profiles). However, the HTD provides no means to distribute data in a consistent way. If any data is provided, there is no guarantee that a recipient of an HTD description has the knowledge or the tools to interpret this data.
Hence, I would like to define a format for attaching data to an HTD description. This could for instance be based on the data format used for the PreCISE approach (refer to Deliverable 3.3 from SmILES project for details), which provides a simple and machine-readable approach to share text-based data.
An example of how this could look like comes from the JRA1 benchmarks, e.g., the data attached to the multi-energy networks benchmark.
The text was updated successfully, but these errors were encountered: