Ticket #18 (closed feature request: fixed)

Opened 3 years ago

Last modified 3 years ago

using to_cost values in shooting* algorithm

Reported by: siarhei Owned by: anton
Priority: major Milestone: Version 1.1
Component: Shooting* Version:
Keywords: Cc:

Description

I think that to_cost value can be spent time on passing through the edges. So as to restrictions if to_cost value is positive (as in documentation it can be traffic light ) it can take part in calculating shortest path( with to_cost values added to cost values of edges involved in restriction).

But if to_cost value is negative (-1) then restriction turn must not appear in shortest path result

Change History

Changed 3 years ago by anton

  • owner changed from somebody to anton
  • status changed from new to assigned
  • version 1.0.0a deleted
  • milestone changed from Version 1.0 to Version 1.1

Changed 3 years ago by anton

  • status changed from assigned to closed
  • resolution set to fixed

Actualy, 'to_cost' (just like 'cost') can be anything - length, time, price etc.

And we decided that if 'to_cost' value is negative, this edge is unpassable.

Note: See TracTickets for help on using tickets.