cca0.5

Compliant Control Architecture 0.5

44%

36 issues   (15 closed — 21 open)

Time tracking
Estimated time 7.00 hours
Issues by
Bug

3/9
Feature

3/11
Tasks

9/15
Enhancement

0/1
Related issues
Bug #973: Type filter for input ports
Bug #1317: Ambiguous converter sets in cca Basecomponent with ports of type rst.generic.Value (conflicting with ComponentStateConverter)
Bug #1397: Handle buffer access for unconfigured (optional) ports
Bug #1638: cca.component logger[INFO] reports wrong state transition
Bug #1639: Exception when configuring non-available transport
Bug #1647: Weird component-crashes when wrong converter plugins are loaded
Bug #1835: Error when printing properties without default
Bug #2078: Component start state not handled correctly
Bug #2204: suffix argument in cca-statechanger not working properly
Feature #879: RTBeat
Feature #969: ModerateProcessing for set of ports
Feature #970: PortTriggered processing for set of ports
Feature #1436: Enhance CCA component state 'PERSISTED' with storage path information
Feature #1508: Support tracing of events
Feature #1717: Synchronization mechanism / barrier
Feature #1729: Allow remote configuration of components
Feature #1813: Add cca context around user code exceptions
Feature #1814: More detailed printing of the cca input port handler
Feature #2046: Allow to expose virtual / simulation time via external beat
Tasks #290: Timing for Control
Tasks #912: Default configuration for components
Tasks #1635: Detect and warn about too slow processing
Tasks #1772: Create unambigious converter map for cca state ports
Tasks #1773: Fix component state converter to convert to rst.cbse.componentstate
Tasks #1784: Delete component monitor from cca main project
Tasks #1786: Deploy cca-tools trunk package to testing repository
Tasks #2049: Document new beat behavior
Enhancement #1788: Create dedicated converter maps for input and output ports