departSpeed is an attribute for vehicles flows and trips. Do not put this
into the vType.
Am Mo., 10. Aug. 2020 um 23:31 Uhr schrieb Sumo User <
sumoquesti...@gmail.com>:
> Hello,
>
> I am trying to insert a slow moving car into my simulation. I used
> DFROUTER to make a routes file based on
1) In the latest development version there is traci.vehicle.getFollower (
https://sumo.dlr.de/docs/Downloads.php#sumo_-_latest_development_version)
2) the parameters and their defaults are listed at
Hello Harald,
No, I did not get any other errors. Should I try other version?
thanks and regards,
Dillip Rout
On Fri, 7 Aug 2020 at 11:20, Harald Schaefer wrote:
> Hello Dillip,
>
> there must be another error in the output of the makefile.
>
> If you run step 5 without the -j option (just
Hello,
I am trying to insert a slow moving car into my simulation. I used
DFROUTER to make a routes file based on real traffic data that was
downloaded online. I added a new vehicle type to the routes file and then
manually added it to my emitter file. When I run the simulation in the
command
Would you please answer my questions?
Thank you so much!
On Fri, Aug 7, 2020 at 12:17 AM wrote:
> Hi everyone!
> I have two questions and I would be glad if you answer them.
> 1) Is there any function to return the follower vehicle's information? For
> example, getLeader
>
I misread your flow definition so ignore my prior comment.
Please check if there are delayed insertions on the calibrator edge (
https://sumo.dlr.de/docs/Simulation/VehicleInsertion.html#investigating_insertion_delay).
If that is not the case, send in your input files so I can take a look.
Am
Hey Jakob,
thanks for your reply.
Where do I exactly have to add the end-attribute? In the flows it’s already
present, just not directly after the begin-attribute.
Best regards
Simon
From: sumo-user-boun...@eclipse.org On Behalf
Of Jakob Erdmann
Sent: Montag, 10. August 2020 14:17
To: Sumo
It would be helpful if you could report the symptoms of your problem (i.e
error messages).
Am Fr., 7. Aug. 2020 um 02:55 Uhr schrieb Padisala, Shanthan Kumar <
padisal...@buckeyemail.osu.edu>:
> Dear Jackob,
>
> I am using the latest build. However, I am unable to use this command. May
> I know
According to your command two conditions must be met:
- the vehicle must have stopped at least until time 100
- the vehicle must have stopped for at least 50s
You can activate 'show route' for the vehicle to see the remaining stop
duration in sumo-gui:
You need to define the 'end' attribute of the calibrator flows explicitly.
regards,
Jakob
Am Mo., 10. Aug. 2020 um 10:08 Uhr schrieb simon.frent...@umlaut.com <
simon.frent...@umlaut.com>:
> Hey guys,
>
>
>
> I’m currently running a simulation for one hour with calibrators, but they
> don’t
Hello,
When I use *setStop*(self, vehID, edgeID, pos=30.0, laneIndex=0, duration
=50.0, flags=0, startPos=-1073741824.0, until=100.0)
the vehicle still stop when specified time arrive
I tried reduce parameter but got same result.
I also tried recall setStop and set "duration" 0 after 50
Hey guys,
I'm currently running a simulation for one hour with calibrators, but they
don't behave as they should. The file with the calibrator definitions looks
like this:
http://www.w3.org/2001/XMLSchema-instance;
xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/additional_file.xsd;>
Hello,
the speed should be an emergent property that arises due to high traffic
density. Possibly the vehicles defined in the emitters file are not
inserted at the expected times due failed insertion safety checks. As a
result of this, the speed would remain higher than expected.
For details on
13 matches
Mail list logo
