-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fix A* star selection logic #22
Open
victorreijgwart
wants to merge
11
commits into
feature/clang_format_reorder_includes
Choose a base branch
from
fix/a_star_update_rule
base: feature/clang_format_reorder_includes
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
0862b56
Fix A* star update rule to take shortest, not longest evaluated branch
victorreijgwart e08c457
Merge branch 'feature/clang_format_reorder_includes' into fix/a_star_…
victorreijgwart f9a8f72
Merge pull request #21 from ethz-asl/feature/clang_format_reorder_inc…
victorreijgwart 38b6783
Update the GLocal ArXiv link to the right paper
victorreijgwart 71a5e07
Merge pull request #24 from ethz-asl/fix/correct_glocal_arxiv_link
Schmluk a2d0474
Update README.md
Schmluk 095a63b
Merge pull request #25 from ethz-asl/feature/add_source_pt1
Schmluk af03498
Update README.md
Schmluk 18d5110
Update README.md
Schmluk 3783213
Merge pull request #26 from ethz-asl/feature/cite_readme
Schmluk d3e7525
Merge remote-tracking branch 'origin/master' into fix/a_star_update_rule
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Is this intentionally called h_score and then assigned to the f_score_map? I'm not too familiar with the terminology but might lead to confusions.
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.
Strictly speaking, the update equation here should be
f[neighbor] = g[neighbor] + h[neighbor]
. The code above only initializes the starting vertices and will result in all of them being expanded before any regular vertex, so it won't affect the result. But I agree it's confusing and there's no advantage of not using the standard update equation.In general, this whole
getPathBetweenVertices(...)
method grew organically and got quite messy. I'll do some refactoring.