I/O

The PowerSystemDataModel library additionally offers I/O-capabilities. In the long run, it is our aim to provide many different source and sink technologies. Therefore, the I/O-package is structured as highly modular.

• CSV files
  • Naming of files
  • Default naming strategy
  • Default directory hierarchy
  • De-serialization (loading models)
  • Serialization (writing models)
  • Compression and extraction of files
• SQL
  • Id Coordinate Source
• InfluxDB
  • Introduction to InfluxDB
  • Instantiating an InfluxDB DataConnector
• Validation Utils
  • What are the ValidationUtils?
  • What is checked?
  • How to use?
  • How does the general validation work?
  • Which objects are checked?
  • What should be considered?

Data sink structure

Data source structure

The sources are divided in three blocks:

1. InputEntities and ResultEntities

2. TimeSeries related sources

3. Weather and Coordinate sources

The function to read the sources are implemented in the DataSource classes.

Data deployment