TEC issueshttps://gitlab.ethz.ch/groups/tec/-/issues2020-04-14T09:58:23Zhttps://gitlab.ethz.ch/tec/public/exot/eengine/-/issues/1Issue with capacity bound calculations2020-04-14T09:58:23ZGhost UserIssue with capacity bound calculationshttps://gitlab.ethz.ch/tec/public/flocklab/flocklab-tools/-/issues/2Getting test running time in createTest()2020-04-28T14:07:32ZjacobrGetting test running time in createTest()The CLI used to return the scheduled start time of the test; in practice, I found this useful. Could something similar be added to the new `createTest()` method?The CLI used to return the scheduled start time of the test; in practice, I found this useful. Could something similar be added to the new `createTest()` method?https://gitlab.ethz.ch/tec/public/employees/matthias-meyer/stuett/-/issues/3uninitialized variable2019-11-27T13:37:08ZGhost Useruninitialized variableIn the beginning of the function configuration in graph.py, the variable collections is not initialized, if delayed is a list.
Link: https://gitlab.ethz.ch/tec/research/stuett/software/framework/stuett/blob/master/stuett/core/graph.py#L126In the beginning of the function configuration in graph.py, the variable collections is not initialized, if delayed is a list.
Link: https://gitlab.ethz.ch/tec/research/stuett/software/framework/stuett/blob/master/stuett/core/graph.py#L126https://gitlab.ethz.ch/tec/public/employees/matthias-meyer/stuett/-/issues/2Default __call__ of Nodes2019-11-15T15:36:08ZmatthmeyDefault __call__ of NodesA new change I will introduce is that the Nodes __call__ function is not a dask.delayed function by default.
This has already been partially implemented in the develop branch, but still needs to be finished.
The intuition is that the ...A new change I will introduce is that the Nodes __call__ function is not a dask.delayed function by default.
This has already been partially implemented in the develop branch, but still needs to be finished.
The intuition is that the nodes should be usable without having to work with a dask graph.
There will be an option (global and per node) which enables dask.delayed wrapping of the __call__ function.
@tkuonen will need to consider this when implementing the visualization.https://gitlab.ethz.ch/tec/public/employees/matthias-meyer/stuett/-/issues/1Timezone issues with xarray dataarray2019-11-14T19:08:50ZmatthmeyTimezone issues with xarray dataarrayLike described in this issues [1](https://github.com/pydata/xarray/issues/3291) [2](https://github.com/pydata/xarray/issues/3320), if we use timezone aware inputs as datetime coordinates in xarray it will be converted to an object instea...Like described in this issues [1](https://github.com/pydata/xarray/issues/3291) [2](https://github.com/pydata/xarray/issues/3320), if we use timezone aware inputs as datetime coordinates in xarray it will be converted to an object instead of datetime.
If we convert it with pd.to_datetime() when we want to use it is not an issue but if we want to use slicing this is an issue.