Skip to content
  • Benedikt Kleinmeier's avatar
    Fixed processor names in two salient behavior names to avoid exceptions · 60068778
    Benedikt Kleinmeier authored
    But three scenarios still throw exceptions:
    - 11-RiMEA11-ExitSelection-OSMEventDriven-SBEnabled:
      ClassCastException: TimestepPedestrianIdKey cannot be cast to EventtimePedestrianIdKey
    - TestSpeedInAreaProcessor-SpeedByTrajectory:
      ClassCastException: FootStepProcessor cannot be cast to class FootStepProcessor
    - TestSpeedInAreaProcessor-SpeedByWidth:
      ClassCastException: FootStepProcessor cannot be cast to class FootStepProcessor and PedestrianVelocityDefaultProcessor are in unnamed module of loader 'app'
    60068778