-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature/nav 17 simple algorithm implementation #15
Feature/nav 17 simple algorithm implementation #15
Conversation
# Conflicts: # src/test/java/ch/naviqore/Benchmark.java
…ections without duplicates.
…s greater than best arrival time.
…or all stops or target stop.
…tor build for testing.
- Connection and Leg implement comparable, change to sorting based on this class property. Connections are sorted according to the earliest arrival time. Legs are sorted according to departure time. - Change access of Raptor.Leg and Raptor.ArrivalType to private since they are not needed from outside the class. - Refactor the connections class, make it initializable and immutable. Hide building methods outside the package.
- Introduce raptor test builder with test extension for parameter injection. - Refactor input validation in raptor and add test cases.
- Introduce generic value object cache in the utils package. - Memory usage stays the same. Closes: #9
…-cache ENH: NAV-43 - Generic value object cache
- Add trip validator wit test cases. - Add validation in stop time construction. - Place todo in raptor builder.
…ound (entering to earlier trip not possible in same round)
…r builder - Raptor builder validates trips and stop times. The order of adding trips and stop times does not matter anymore. - Adjusted GtfsToRaptorConverter to new Raptor builder.
…le-algorithm-implementation' into feature/NAV-42-input-validation-raptor-builder-trip-id
- Some cosmetics: Remove sys.out.print call and correct log config file path in benchmark javadoc.
Wait for #18 and a fix of the benchmark. Then we should merge and tag our first algorithm version 🚀 |
…or looking for next trip departures.
…on' into feature/NAV-42-input-validation-raptor-builder-trip-id
- Only request valid stop ids from raptor. - Write more information to the results. - Add converters to ServiceDayTime.
- Check for invalid minute (0,60) and seconds (0, 60) in service day time constructor. Update tests. - Rename non-existent trips in route builder test.
…raptor-builder-trip-id Feature/nav 42 input validation raptor builder trip
Would say this branch is ready for a final review @munterfi, @Brunner246 Open Tasks for new Issues:
|
Perfect, thanks. from my side the PR is ready. Should we tag after merge with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not ready to merge: