Skip to content

Fixed Cost behaves oddly #951

@GuyBenhaim

Description

@GuyBenhaim

Seems that vehicle FixedCost is evaluated vs. a single Node's disjunction penalty: if the FixedCost is slightly higher the vehicle is not used and similarly no vehicle was used and all Nodes were dropped.
10 Vehicles, 80 Orders.

If Solver would have allocated the vehicle, it would server multiple Nodes and reduce penalty substantially.

When FixedCost was even a bit lower than disjunction penalty (of one Node) all necessary vehicles were allocated and served the Nodes.

Looks like the criteria to allocate was just based one vehicle vs. one Node. Correct?
If I'm not wrong, this creates undesired results.

Metadata

Metadata

Assignees

Labels

BugHelp NeededModeling/Usage problemSolver: RoutingUses the Routing library and the original CP solver

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions