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

Scores for accessibility routing and other preferences #254

Conversation

trurlurl
Copy link
Contributor

@trurlurl trurlurl commented Oct 7, 2022

This is a proposal addressing #187 in a way that is compatible with the vision / roadmap discussed in #221,

Basic idea: Route plannig tries to optimize Scores which can be defined as a weighted sum over lower level Preferences.

I think to get a list of Trips the user is really happy with, two runs of a planning algorithm will typically be required (unless we had an algorithm optimising multiple Scores in parallel, perhaps as mentioned by Alexandre?):

  • a run optimizing a "fastest" Score on first priority, and, e.g., a "accessibility" Score on a second priority (to get the traditional fastest Trips with additonal accessiblity optimisation and information);
  • and a second run optimizing the other (e.g., "accessibility") Score on first priority (to get Trips that optimally fit the user's special needs, but that may result in Trips normally considered too late or too long).

Before removing OptimizationMethod
OptimisationMethod removed
<xs:enumeration value="environmentalFootprint"/>
-->
</xs:restriction>
</xs:simpleType>
Copy link
Contributor Author

@trurlurl trurlurl Oct 7, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Example` to illustrate a Score definition:

ExampleScore.txt

Refinement on Preferences
</xs:annotation>
</xs:enumeration>
<!-- The following seem less close to realisation:
<xs:enumeration value="onlyExtraReliableConnections"/>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add onlyGuaranteedInterchanges, evaluation based on guaranteedConnection (TransferModesEnumeration)?

@ue71603
Copy link
Contributor

ue71603 commented Nov 4, 2022

André: Waiting on some input from Malte before finalising.

@skinkie
Copy link
Contributor

skinkie commented Nov 24, 2022

I dislike this change... we should discuss this.

@ue71603
Copy link
Contributor

ue71603 commented Nov 24, 2022

new version fro Köln

@ue71603
Copy link
Contributor

ue71603 commented Dec 17, 2022

In my view now superseeded by #273. @trurlurl If you disagree, please complain.

@trurlurl
Copy link
Contributor Author

trurlurl commented Jan 8, 2023

Removed documentation label, documentation will be done for the follow-up PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request to be disussed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants