Hello,
regarding 1)
in config-files,
<additional-files value="file1 file2 file3"/> and
<additional-files value="file1,file2,file3"/> should both work. What error
message do you get?

regarding 2)
most likely there is something wrong with the route file itself. It should
generally be possible to use the -r option for route files.
Only if the routes are unsorted (wrt departure time) you need to use -a
because -a does not perform incremental loading but loads the whole file
instead.

Note, that in your route file any <route> elements must come before
<vehicle route=""> elements referencing the former.

regards,
Jakob




2014-02-04 Pieter Loof <[email protected]>:

> Hi all,
>
> I just tried using the --save-configuration option for both DFRouter and
> SUMO. It succesfully creates a config file, but I ran into a few small
> problems.
>
> Problem 1:
>
> I know that the additional files in a .sumocfg file is a space-separator
> list, like this:
>      <additional-files value="file1 file2 file3"/>
>
> Now, in whatever way I try to give the additional files as flag to a sumo
> command, it keeps saving it to the config file in the wrong format. As far
> as I know the flag for additional files should be a comma-separated list,
> like this:
>      sumo -a file1,file2,file
>
> But when I run the command and look at the produced config file, I see that
> the commas are stll there, it looks like this:
>      <additional-files value="file1,file2,file3"/>
>
> So there are still commas in between, and running SUMO with this config
> file gives errors that I do not receive when the list is space-separated. I
> tried a few different ways of formatting the "-a <FILE>" using commas or
> spaces as separator with and without enclosing braces, brackets or quotes,
> but the generated format is never correct. Am I doing something wrong?
>
> Problem 2:
>
> When generating the sumo config file, using the flag "-r <FILE>" to give
> the route file, then the route file is written as
>      <route-files value=file/>
>
> But when running SUMO using the generated config file, errors occur about
> invalid references to routes. The only solution seems to be to give the
> route file under the "-a <FILE>" flag. If the route file should be an
> additional file, then please fix the config generation process or change
> the documentation about providing the route file.
>
> Best regards,
> Pieter
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _______________________________________________
> sumo-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sumo-user
>
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
sumo-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sumo-user

Reply via email to