Re: [sumo-user] Some ideas and proposals for repeated routes
Hello Dillip, various combinations are possible: - (begin, end, number) is permitted - the period is then computed as (end-begin)/number - (begin, end, period) is permitted - (begin, period, number) is permitted - (begin, end, period, number) is not permitted because the values might contradict each other regards, Jakob Am Di., 16. Juni 2020 um 09:21 Uhr schrieb Tripplanner Mumbai < tripplanner...@gmail.com>: > Hello Jakob, > > I understand your concern regarding the change or addition of new classes. > It is absolutely fine till things are working, especially with backward > compatibility. A splendid work has been done by you and your team, no > doubts. We are lucky to have your advice, time to time, majority of the > queries are sorted out within a day. > > It is pretty nice to see renaming of the period attribute of route to > cycleTime (also known as round trip time). It will be adopted and > appreciated soon by the users. Just a query regarding the coexistence of > *end* and *number* attributes in flow (see below). As per the current > verion, both cannot be used simultaneously, is it contradictory? > line="11" type="bus" route="11"/> > > Kudos to your team again for such evolving development of SUMO. > > thanks and regards, > Dillip Rout > > On Mon, 15 Jun 2020 at 22:27, Jakob Erdmann wrote: > >> Hello Harald, >> Thanks for your suggestions >> a) I agree that using the same attribute name for two related but subtly >> different things is adding unnecessary confusion (I fact, confusion was >> recently observed). >> Since the 'period' attribute of flows has a lot of history behind it I'll >> keep this unchanged. >> However, I renamed route attribute period to 'cycleTime' (see >> https://github.com/eclipse/sumo/issues/7168). >> >> b) Incidentally, I was thinking about the same thing recently and came up >> with this: https://github.com/eclipse/sumo/issues/7164 >> For an example. see >> https://github.com/eclipse/sumo/tree/master/tests/sumo/devices/rerouting/stops/public_transport_implicit_route >> >> c) This is already working with the recent fix: >> https://github.com/eclipse/sumo/tree/master/tests/sumo/devices/rerouting/stops/public_transport_implicit_route_depot >> >> >> @Dillip Rout: I generally avoid adding new input definitions as long as >> the existing ones can be used to achieve the desired results. Also, you may >> find that there is good reason in keeping the edges/stop-list separate from >> definition of the vehicles that run these stops (especially, when the >> departure times of the vehicles are not spaced regularly over the whole >> day). >> In terms of changing ambiguous names, there is a large cost associated >> with changing things that have been used by many people over many years. >> The case of route attribute period / cycleTime is special insofar that the >> feature was added recently and thus will not have been widely adopted yet. >> This is not to dismiss thoughts on improvements but rather to point out >> some of the constraints. Feel free to point out things that are confusing >> and/or inefficient. >> >> regards, >> Jakob >> >> >> >> Am Mo., 15. Juni 2020 um 11:03 Uhr schrieb Harald Schaefer < >> fechs...@gmail.com>: >> >>> Hello >>> >>> here are some proposals for enhancing the repeated route stuff: >>> >>> a) change of attribute names >>> >>> In route I would rename period to cycletime (German: Umlaufzeit) >>> >>> In flow I would rename period to headway (German: Taktzeit) >>> >>> b) Can we add the repeat features to trips, if we want to specify only >>> the stops and not the edges or allow an empty edge list? >>> >>> c) If I want to simulate a whole day, I need also the links to the depot >>> in the morning and evening >>> >>> The definition in the testcase >>> tests/sumo/rail/tramwayLoop/input_routes.rou.xml old (it has no >>> intermediate edges) >>> >>>>> from="Tdepot_1" to="Tdepot_1" type="RB628"> >>> >>> >>> >>> >>> >>> >>> >>> might look in the future >>> >>> >>> >>> >>> >>> >>> >>> >>>>> departSpeed="max" route="startLeft" headway="120"/> >>> >>> What do you think? >>> >>> Greetings, >>> >>> Harald >>> >>> ___ >>> sumo-user mailing list >>> sumo-user@eclipse.org >>> To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/sumo-user >>> >> ___ >> sumo-user mailing list >> sumo-user@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/sumo-user >> > ___ > sumo-user mailing list > sumo-user@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user > ___ sumo-user mailing list sumo-user@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
Re: [sumo-user] Some ideas and proposals for repeated routes
Hello Jakob, I understand your concern regarding the change or addition of new classes. It is absolutely fine till things are working, especially with backward compatibility. A splendid work has been done by you and your team, no doubts. We are lucky to have your advice, time to time, majority of the queries are sorted out within a day. It is pretty nice to see renaming of the period attribute of route to cycleTime (also known as round trip time). It will be adopted and appreciated soon by the users. Just a query regarding the coexistence of *end* and *number* attributes in flow (see below). As per the current verion, both cannot be used simultaneously, is it contradictory? Kudos to your team again for such evolving development of SUMO. thanks and regards, Dillip Rout On Mon, 15 Jun 2020 at 22:27, Jakob Erdmann wrote: > Hello Harald, > Thanks for your suggestions > a) I agree that using the same attribute name for two related but subtly > different things is adding unnecessary confusion (I fact, confusion was > recently observed). > Since the 'period' attribute of flows has a lot of history behind it I'll > keep this unchanged. > However, I renamed route attribute period to 'cycleTime' (see > https://github.com/eclipse/sumo/issues/7168). > > b) Incidentally, I was thinking about the same thing recently and came up > with this: https://github.com/eclipse/sumo/issues/7164 > For an example. see > https://github.com/eclipse/sumo/tree/master/tests/sumo/devices/rerouting/stops/public_transport_implicit_route > > c) This is already working with the recent fix: > https://github.com/eclipse/sumo/tree/master/tests/sumo/devices/rerouting/stops/public_transport_implicit_route_depot > > > @Dillip Rout: I generally avoid adding new input definitions as long as > the existing ones can be used to achieve the desired results. Also, you may > find that there is good reason in keeping the edges/stop-list separate from > definition of the vehicles that run these stops (especially, when the > departure times of the vehicles are not spaced regularly over the whole > day). > In terms of changing ambiguous names, there is a large cost associated > with changing things that have been used by many people over many years. > The case of route attribute period / cycleTime is special insofar that the > feature was added recently and thus will not have been widely adopted yet. > This is not to dismiss thoughts on improvements but rather to point out > some of the constraints. Feel free to point out things that are confusing > and/or inefficient. > > regards, > Jakob > > > > Am Mo., 15. Juni 2020 um 11:03 Uhr schrieb Harald Schaefer < > fechs...@gmail.com>: > >> Hello >> >> here are some proposals for enhancing the repeated route stuff: >> >> a) change of attribute names >> >> In route I would rename period to cycletime (German: Umlaufzeit) >> >> In flow I would rename period to headway (German: Taktzeit) >> >> b) Can we add the repeat features to trips, if we want to specify only >> the stops and not the edges or allow an empty edge list? >> >> c) If I want to simulate a whole day, I need also the links to the depot >> in the morning and evening >> >> The definition in the testcase >> tests/sumo/rail/tramwayLoop/input_routes.rou.xml old (it has no >> intermediate edges) >> >>> from="Tdepot_1" to="Tdepot_1" type="RB628"> >> >> >> >> >> >> >> >> might look in the future >> >> >> >> >> >> >> >> >>> departSpeed="max" route="startLeft" headway="120"/> >> >> What do you think? >> >> Greetings, >> >> Harald >> >> ___ >> sumo-user mailing list >> sumo-user@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/sumo-user >> > ___ > sumo-user mailing list > sumo-user@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user > ___ sumo-user mailing list sumo-user@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
Re: [sumo-user] Some ideas and proposals for repeated routes
Hello Harald, Thanks for your suggestions a) I agree that using the same attribute name for two related but subtly different things is adding unnecessary confusion (I fact, confusion was recently observed). Since the 'period' attribute of flows has a lot of history behind it I'll keep this unchanged. However, I renamed route attribute period to 'cycleTime' (see https://github.com/eclipse/sumo/issues/7168). b) Incidentally, I was thinking about the same thing recently and came up with this: https://github.com/eclipse/sumo/issues/7164 For an example. see https://github.com/eclipse/sumo/tree/master/tests/sumo/devices/rerouting/stops/public_transport_implicit_route c) This is already working with the recent fix: https://github.com/eclipse/sumo/tree/master/tests/sumo/devices/rerouting/stops/public_transport_implicit_route_depot @Dillip Rout: I generally avoid adding new input definitions as long as the existing ones can be used to achieve the desired results. Also, you may find that there is good reason in keeping the edges/stop-list separate from definition of the vehicles that run these stops (especially, when the departure times of the vehicles are not spaced regularly over the whole day). In terms of changing ambiguous names, there is a large cost associated with changing things that have been used by many people over many years. The case of route attribute period / cycleTime is special insofar that the feature was added recently and thus will not have been widely adopted yet. This is not to dismiss thoughts on improvements but rather to point out some of the constraints. Feel free to point out things that are confusing and/or inefficient. regards, Jakob Am Mo., 15. Juni 2020 um 11:03 Uhr schrieb Harald Schaefer < fechs...@gmail.com>: > Hello > > here are some proposals for enhancing the repeated route stuff: > > a) change of attribute names > > In route I would rename period to cycletime (German: Umlaufzeit) > > In flow I would rename period to headway (German: Taktzeit) > > b) Can we add the repeat features to trips, if we want to specify only > the stops and not the edges or allow an empty edge list? > > c) If I want to simulate a whole day, I need also the links to the depot > in the morning and evening > > The definition in the testcase > tests/sumo/rail/tramwayLoop/input_routes.rou.xml old (it has no > intermediate edges) > > from="Tdepot_1" to="Tdepot_1" type="RB628"> > > > > > > > > might look in the future > > > > > > > > > departSpeed="max" route="startLeft" headway="120"/> > > What do you think? > > Greetings, > > Harald > > ___ > sumo-user mailing list > sumo-user@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user > ___ sumo-user mailing list sumo-user@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
Re: [sumo-user] Some ideas and proposals for repeated routes
Hello Herald, Thanks for coming up with a proposal. In my opinion, the word route is ambiguous since it is used for defining a path as well as a public transit line (or route). Hence, a new class named line or ptLine should be formed. This class will contain all the properties of a public transit line (or route), may be some of those will be optional. Broadly, this class should combine route, flow, trip, etc. I would be happy to share the thoughts. thanks and regards, Dillip Rout On Mon, 15 Jun 2020 at 14:33, Harald Schaefer wrote: > Hello > > here are some proposals for enhancing the repeated route stuff: > > a) change of attribute names > > In route I would rename period to cycletime (German: Umlaufzeit) > > In flow I would rename period to headway (German: Taktzeit) > > b) Can we add the repeat features to trips, if we want to specify only > the stops and not the edges or allow an empty edge list? > > c) If I want to simulate a whole day, I need also the links to the depot > in the morning and evening > > The definition in the testcase > tests/sumo/rail/tramwayLoop/input_routes.rou.xml old (it has no > intermediate edges) > > from="Tdepot_1" to="Tdepot_1" type="RB628"> > > > > > > > > might look in the future > > > > > > > > > departSpeed="max" route="startLeft" headway="120"/> > > What do you think? > > Greetings, > > Harald > > ___ > sumo-user mailing list > sumo-user@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/sumo-user > ___ sumo-user mailing list sumo-user@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
[sumo-user] Some ideas and proposals for repeated routes
Hello here are some proposals for enhancing the repeated route stuff: a) change of attribute names In route I would rename period to cycletime (German: Umlaufzeit) In flow I would rename period to headway (German: Taktzeit) b) Can we add the repeat features to trips, if we want to specify only the stops and not the edges or allow an empty edge list? c) If I want to simulate a whole day, I need also the links to the depot in the morning and evening The definition in the testcase tests/sumo/rail/tramwayLoop/input_routes.rou.xml old (it has no intermediate edges) from="Tdepot_1" to="Tdepot_1" type="RB628"> might look in the future departSpeed="max" route="startLeft" headway="120"/> What do you think? Greetings, Harald ___ sumo-user mailing list sumo-user@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
