TeeTime issueshttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues2018-03-25T13:44:55+02:00https://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/364Add Changelog for 3.0 to Website2018-03-25T13:44:55+02:00Sören HenningAdd Changelog for 3.0 to WebsiteVersion 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/357Add wiki entry for logging2017-12-31T11:36:39+01:00Christian WulfAdd wiki entry for loggingmaven dep + xml config filemaven dep + xml config fileVersion 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/341Finish implementation of DynamicTaskFarmStage2017-10-20T20:14:50+02:00Christian WulfFinish implementation of DynamicTaskFarmStageSo far, ``declareActive()`` at runtime is required, but not yet implemented/mergedSo far, ``declareActive()`` at runtime is required, but not yet implemented/mergedVersion 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/339How to handle time-triggered stages?2017-08-02T14:28:38+02:00Christian WulfHow to handle time-triggered stages?Some time-triggered stages:
* Delay
* ElementDelayMeasuringStage
* ElementThroughputMeasuringStage
The semantics of a time-triggered stage depends on whether it should react on a time trigger
* instantly (out-of-scheduling), or
* on the...Some time-triggered stages:
* Delay
* ElementDelayMeasuringStage
* ElementThroughputMeasuringStage
The semantics of a time-triggered stage depends on whether it should react on a time trigger
* instantly (out-of-scheduling), or
* on the next regular scheduling cycle by enforcing a new cycle, or
* on the next regular scheduling cycle by waiting for the next regular cycle.
Hence, such stages require a particular scheduling approach. This implies that we must provide more than one scheduling. And this implies that there is no single optimal scheduling approach for all cases.Version 3.0https://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/338Add method CompositeStage.declareActive()2017-08-01T21:30:45+02:00Christian WulfAdd method CompositeStage.declareActive()Currently, a composite stage can be set active by setting one or more of its substages active:
```java
wc.getInputPort().getOwningStage().declareActive();
```
We should also add ``declareActive()`` to ``CompositeStage``. The stage devel...Currently, a composite stage can be set active by setting one or more of its substages active:
```java
wc.getInputPort().getOwningStage().declareActive();
```
We should also add ``declareActive()`` to ``CompositeStage``. The stage developer can then decide what ``declareActive()`` should mean for the particular composite stage.Version 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/331Reconsider map with threads and exceptions for other scheduling approaches2017-06-14T12:49:45+02:00Christian WulfReconsider map with threads and exceptions for other scheduling approachesThere is no dedicated thread for a stage when using the global task queue scheduling. The following interface is thus suboptimal:
``teetime.framework.exceptionHandling.AbstractExceptionListenerFactory.createInstance(Thread)``
Same appli...There is no dedicated thread for a stage when using the global task queue scheduling. The following interface is thus suboptimal:
``teetime.framework.exceptionHandling.AbstractExceptionListenerFactory.createInstance(Thread)``
Same applies for ``Stage.setOwningThread``Version 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/321Validate stages created at runtime2017-03-21T10:21:59+01:00Christian WulfValidate stages created at runtimeVersion 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/319Rename AbstractRunnableStage2017-03-21T09:56:31+01:00Christian WulfRename AbstractRunnableStagesuggestions:
- AbstractStageExecutor
- AbstractStageRunnersuggestions:
- AbstractStageExecutor
- AbstractStageRunnerVersion 3.0https://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/312State of producers does not need to be volatile2017-03-24T08:07:41+01:00Christian WulfState of producers does not need to be volatileVersion 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/285Make the signal tests work again2016-09-08T16:41:50+02:00Christian WulfMake the signal tests work againVersion 3.0Christian WulfChristian Wulfhttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/284DivideAndConquerStageTest runs infinitely2017-08-03T12:58:57+02:00Christian WulfDivideAndConquerStageTest runs infinitelyVersion 3.0https://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/272Test Snap CI2016-03-14T16:04:46+01:00Nelson Tavares de SousaTest Snap CIhttps://www.snap-ci.com/https://www.snap-ci.com/Version 3.0Nelson Tavares de SousaNelson Tavares de Sousahttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/271Add documentation for our fancy patterns2016-09-06T14:49:59+02:00Nelson Tavares de SousaAdd documentation for our fancy patternsI already added a 6th point under "Using the Framework".
As for now, neither DC nor TF are promoted or explained anywhere.
This needs to be changed! ;)I already added a 6th point under "Using the Framework".
As for now, neither DC nor TF are promoted or explained anywhere.
This needs to be changed! ;)Version 3.0Nelson Tavares de SousaNelson Tavares de Sousahttps://git.se.informatik.uni-kiel.de/teetime/teetime/-/issues/227Divide teetime in separate sub-projects2016-02-22T13:35:02+01:00Nelson Tavares de SousaDivide teetime in separate sub-projectsMaven supports a project hierarchy... we should use this featureMaven supports a project hierarchy... we should use this featureVersion 3.0Nelson Tavares de SousaNelson Tavares de Sousa