The
issue encountered is that, although the examined road cross-section appears to
have three lanes, after adding the following command to the.sumocfg
file, observations are not produced for all lanes.<queue-output
value="queue_output.xml"/>
More
specifically, as shown below from the output file, observations are not
recorded for every lane at every time step, regardless of whether the
corresponding value is zero or not. In some cases, a lane is explicitly
included with a value of 0, while in other cases no entry or value is
provided at all for certain lanes. As a result, it is unclear whether the
absence of an entry should be interpreted as zero value or as the lack
of recording for that particular lane in the output. Below are some
indicative excerpts from the queue output at successive time steps, in
order to illustrate the issue more clearly:
<lane
id="Egnatia_0_1_se_1" queueing_time="4.60"
queueing_length="10.01"
queueing_length_experimental="10.01"/>
<lane id="Egnatia_0_1_se_3"
queueing_time="6.70" queueing_length="20.33"
queueing_length_experimental="20.33"/>
In the above
case, no entry is provided for lane Egnatia_0_1_se_2
<lane
id="Egnatia_0_1_se_3" queueing_time="0.00"
queueing_length="0.00" queueing_length_experimental="29.27"/>
In this case,
entries for lanes Egnatia_0_1_se_1 and Egnatia_0_1_se_2 are also missing,
even though the output does include the lane with a value of 0.00.
The question
is whether the above behavior is the expected mode of operation of queue-output
or whether it indicates an error or inconsistency in the generation of the
output file. More specifically, in cases where no entry is shown for a given
lane, should this be interpreted as a zero value, or is there a
possibility that an entry corresponding to a real, non-zero value is
being omitted?
The queue-output.xml
file was generated using both SUMO version 1.25 and version 1.23.1.
Thank you in
advance for your time and assistance.
_______________________________________________