Skip to content

Improve tuning of cost function by analyzing cost breakdown. #26

@tylerlum

Description

@tylerlum

As of right now, when we run: ./build/bin/pathfinder_cli -p 10 --navigate 48 235 20 206, it simply generates the path and wind kml files that we can visualize in Google Maps.

However, there is a lot of important information we should know about to properly improve the system.

How long was the total path length? What was the total path cost? What was the "weather factor" portion of the cost? What was the wind speed throughout the journey (maybe have something that tells us 10% of journey was 0-10 knots, 30% was 10-20, 40% was 20-30, 20% was 30+)

This can either be printed to the terminal, output to a text file, visualized in some other way, etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions