Wrong speed in fcd output of meso

[aminissn]

I am looking into the speed of cars using the fcd output in meso and i see some inconsistencies in the GUI. some cars that are standing behind a traffic light have a speed of 13.89, but their speed drops once light is green and they start moving. Here are some screenshots of the two cars in the upper road (middle and last car that are waiting in a queue for already some second):

I am using sumo Version v1_21_0+1829-db977ec3e8f on macOS.

[namdre]

which sumo options are you using?

[aminissn]

this is my config file :
`

<input>
    <net-file value="net_queue.net.xml"/>
    <route-files value="flow.rou.xml"/>
    <additional-files value="additional.add.xml"/>
</input>

<output>
    <vehroute-output value="routes.out.xml" />
    <vehroute-output.route-length value="true" />
    <vehroute-output.last-route value="true" />
    <vehroute-output.write-unfinished value="true" />
    <vehroute-output.exit-times value="true" />
    <vehroute-output.skip-ptlines value="true" />
    <summary-output value="summary.out.xml" />
    <summary-output.period value="900" />
    <fcd-output value="fcd.out.xml" />
    <fcd-output.geo value="true" />
    <fcd-output.attributes value="id,type,edge,queue,segment,pos,x,y,angle,speed,entryTime" />
</output>

<time>
    <step-length value="1" />
    <begin value="0" />
    <end value="3600" />
</time>

<routing>
    <routing-algorithm value="astar" />
    <weights.random-factor value="1.8" />
    <weights.priority-factor value="0.5" />
    <device.rerouting.probability value="1" />
    <device.rerouting.period value="180" />
    <device.rerouting.pre-period value="0" />
    <device.rerouting.adaptation-steps value="5" />
    <device.rerouting.adaptation-interval value="180" />
    <device.rerouting.with-taz value="true" />
    <device.rerouting.threads value="5" />
    <device.rerouting.synchronize value="true" />
</routing>

<report>
    <verbose value="true" />
    <xml-validation value="never" />
    <no-warnings value="true" />
    <error-log value="log.log" />
</report>

<mesoscopic>
    <mesosim value="true" />
    <meso-edgelength value="100" />
    <meso-tauff value="1.4" />
    <meso-taufj value="1.4" />
    <meso-taujf value="1.4" />
    <meso-taujj value="1.4" />
    <meso-jam-threshold value="-0.8" />
    <meso-multi-queue value="true" />
    <meso-junction-control value="true" />
    <!-- <meso-tls-penalty value="0.5" />
    <meso-tls-flow-penalty value="0.9" />  
    <meso-minor-penalty value="2" /> -->
    <meso-overtaking value="true" />
    <meso-lane-queue value="true" />
</mesoscopic>

<random_number>
    <seed value="17" />
</random_number>

` I think speeds are updated once a vehicle moves to a new meso edge-segment, at least I can see at certain positions speeds are changing.

[namdre]

I suspect this is because you combine --meso-junction-control with the additional macroscopic --meso-tls-flow-penalty. This is not a recommended/useful option combination and should probably raise a warning.

[aminissn]

but I have commented the penalty paramters <!-- <meso-tls-penalty value="0.5" /> <meso-tls-flow-penalty value="0.9" /> <meso-minor-penalty value="2" /> -->

[aminissn]

these are the warnings I get

[namdre]

but I have commented the penalty paramters <!-- <meso-tls-penalty value="0.5" /> <meso-tls-flow-penalty value="0.9" /> <meso-minor-penalty value="2" /> -->

nevermind. I misread the config file. Can you attach the simulation?

[aminissn]

sure. Archive.zip