I am a bit confused about the changes introduced in edde19f1b0788f2464c9c852c31b0d691ae5bbed and further. It seems the LocationDecisionKS now always also add segmentationHypothesis to the blackboard, without option to prevent this? However usually, the StreamSegregationKS will be used to produce segmentationHypotheses. Since the LocationDecisionKS is supposed to be used always because of its included time-integration, the two will interfere and the SegmentIdentityKS be confused.
Could you clarify / add a switch to LocationDecisionKS's constructor to disable segments production?
I am a bit confused about the changes introduced in edde19f1b0788f2464c9c852c31b0d691ae5bbed and further. It seems the LocationDecisionKS now always also add segmentationHypothesis to the blackboard, without option to prevent this? However usually, the StreamSegregationKS will be used to produce segmentationHypotheses. Since the LocationDecisionKS is supposed to be used always because of its included time-integration, the two will interfere and the SegmentIdentityKS be confused.
Could you clarify / add a switch to LocationDecisionKS's constructor to disable segments production?