ASSERT condition for driving vehicles in Veins is not met
I have created a set of routes (~ 90,000 +), using SUMO ACTIVITYGEN/DUAROUTER
configuration file and different durations ( --duration-d 1
, --duration-d 7
, ...).
The resulting .rou.xml
SUMO runs successfully with no major errors. Just some warnings about not valid departPos
.
But when using Veins, the following error message appears:
<!> Error in module (Veins::TraCIScenarioManagerLaunchd)
Scenario.manager (id=6) at event #2327172, t=25619.2: Model error:
ASSERT: condition count == drivingVehicleCount false in function
processVehicleSubscription,
veins/modules/mobility/traci/TraCIScenarioManager.cc line 640.
I removed the ASSERT condition and displayed both values. count
always higher than drivingVehicleCount
.
The included example "lived" works without problems.
I use:
- SUMO 0.22.0
- OMNeT ++ 4.6
- Veins 4 alpha 2.
Also, I tested Veins 3.0 and got the same error message.
Has anyone faced the same problem?
source to share
The remark is ASSERT
totally fine.
In SUMO, any car can have one of five states (according to statesvehicleStates_sm.uxf
): first, it is loaded, goes into run mode when it starts moving, and then goes to arrival when it arrives at its destination. Additionally, running vehicles can temporarily become teleportable or standing.
Veins subscribes to these state changes to keep track of the number of vehicles moving. To ensure that the accounting is correct, he compares his own account with SUMO's reported number of active vehicles.
I don't know why the numbers sometimes don't match. This appears to be happening on large congested networks.
source to share