@ClaraBuettner and I have recently reviewed quite a few PRs and run a number of local test calculations. It has become clear that we are not yet confident about the validity of the results.
To improve this, we would like to implement a set of automated checks. However, we currently do not have a sufficiently clear understanding of the eDisGo side of the data flow.
Therefore, we would like to ask you (@MoritzSchloesser and @joda9) to provide a more detailed overview of how the data from the overlying grid data is expected to appear in eDisGo.
In particular, it would be helpful to specify:
- which data from the overlying grid data is used in the optimisation,
- in which variables / columns / time series the respective data should appear in the eDisGo results,
- and, if relevant, any expected constraints between the values.
With this information, we could use the expected behavior as a basis for implementing automated validation tests and would therefore be able to identify incorrect results much more reliably.
Thanks a lot!
@ClaraBuettner and I have recently reviewed quite a few PRs and run a number of local test calculations. It has become clear that we are not yet confident about the validity of the results.
To improve this, we would like to implement a set of automated checks. However, we currently do not have a sufficiently clear understanding of the eDisGo side of the data flow.
Therefore, we would like to ask you (@MoritzSchloesser and @joda9) to provide a more detailed overview of how the data from the overlying grid data is expected to appear in eDisGo.
In particular, it would be helpful to specify:
With this information, we could use the expected behavior as a basis for implementing automated validation tests and would therefore be able to identify incorrect results much more reliably.
Thanks a lot!