Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • xctrack-public xctrack-public
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 331
    • Issues 331
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • xcontest-public
  • xctrack-publicxctrack-public
  • Issues
  • #756
Closed
Open
Issue created Jul 16, 2021 by Wirtz Julien@Jantallus

Route optimisation issue

During a PWC comp in Serbia (Kopaonik), me and all Pilots who used xctrack have noticed a bad optimisation route compare to LK8000 and to PWC model used to calculate the leading bonus... You can see on the joined pictures the difference between PWC and LK8000 (who give 82.9 km for the task) compare to xctrack (87.5 km task). And XCtrack take a while to change the route North to South as we already flew on south route.IMG_20210716_132903_482

IMG_20210716_132700_623

IMG_20210716_132634_271Screenshot_20210720_062736_org.xcontest.XCTrackScreenshot_20210716_112552_org.xcontest.XCTrack

Edited Jul 20, 2021 by Wirtz Julien
Assignee
Assign to
Time tracking