Class Conflict

All Implemented Interfaces:
Serializable, EventListener, Locatable, EventListenerInterface, EventProducerInterface, Identifiable, Drawable, ObjectInterface, LaneBasedObject

public final class Conflict
extends AbstractLaneBasedObject
implements EventListenerInterface
Conflicts deal with traffic on different links/roads that need to consider each other as their paths may be in conflict spatially. A single Conflict represents the one-sided consideration of a conflicting situation. I.e., what is considered a single conflict in traffic theory, is represented by two Conflicts, one on each of the conflicting Lanes.

This class provides easy access to upstream and downstream GTUs through PerceptionIterables using methods getUpstreamGtus and getDownstreamGtus. These methods are efficient in that they reuse underlying data structures if the GTUs are requested at the same time by another GTU.

Copyright (c) 2013-2019 Delft University of Technology, PO Box 5, 2600 AA, Delft, the Netherlands. All rights reserved.
BSD-style license. See OpenTrafficSim License.

Version:
$Revision$, $LastChangedDate$, by $Author$, initial version Sep 7, 2016
Author:
Alexander Verbraeck, Peter Knoppers, Wouter Schakel
See Also:
Serialized Form