Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discuss cost functions #168

Open
fxjung opened this issue May 14, 2021 · 1 comment
Open

Discuss cost functions #168

fxjung opened this issue May 14, 2021 · 1 comment

Comments

@fxjung
Copy link
Member

fxjung commented May 14, 2021

How should cost functions be implemented/specified and which dispatchers/cost functions should go into the main repository?

Deb:

Thanks. After reading your replies, I would like to start a discussion on the merits of the distance minimization + user-selected external cost pattern. Especially:

  • What is the use case?
  • Will that use case + potentially other use cases be more effectively taken care of by a different design, e.g. a modular notion of cost.
    Users should be able to implement dispatchers of their own liking externally as well, not everything should go into ridepy, as far as I understand. Maybe the zero detour stuff should also be refactored this way...
@fxjung
Copy link
Member Author

fxjung commented May 17, 2021

Cost functions may have distinct "goals". Suitable candidates might

  • minimize the detour that results through any new insertion
  • minimize a quality-of-service parameter for the customer, e.g. the dropoff time
  • maximize efficiency, i.e. the quotient of sum of the direct requested times/distances and the resulting driven time/distance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant