HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Walker-TW
Algorithm-Visualizer
JavaScript2020–2020
Walker-TW / Algorithm-Visualizer

Algorithm-Visualizer

View Algorithms in the Browser! - Built with ReactJs

2Distinct people
2Mentions
0Explicit recommenders
182GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

View Algorithms in the Browser! - Built with ReactJs

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2020-06-26 11:02:53 UTC to 2020-06-27 09:38:43 UTC.

012020-06-26 11:00:00 UTC to 2020-06-26 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 26, 11:002020-06-26 12:00:00 UTC to 2020-06-26 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 13:00:00 UTC to 2020-06-26 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 14:00:00 UTC to 2020-06-26 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 15:00:00 UTC to 2020-06-26 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 16:00:00 UTC to 2020-06-26 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 17:00:00 UTC to 2020-06-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 18:00:00 UTC to 2020-06-26 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 19:00:00 UTC to 2020-06-26 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 20:00:00 UTC to 2020-06-26 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 21:00:00 UTC to 2020-06-26 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-26 22:00:00 UTC to 2020-06-26 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 26, 22:002020-06-26 23:00:00 UTC to 2020-06-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 00:00:00 UTC to 2020-06-27 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 01:00:00 UTC to 2020-06-27 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 02:00:00 UTC to 2020-06-27 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 03:00:00 UTC to 2020-06-27 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 04:00:00 UTC to 2020-06-27 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 05:00:00 UTC to 2020-06-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 06:00:00 UTC to 2020-06-27 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 07:00:00 UTC to 2020-06-27 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 08:00:00 UTC to 2020-06-27 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-27 09:00:00 UTC to 2020-06-27 10:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 27, 09:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 26, 11:002020-06-26 11:00:00 UTC2020-06-26 12:00:00 UTC110
Jun 26, 12:002020-06-26 12:00:00 UTC2020-06-26 13:00:00 UTC000
Jun 26, 13:002020-06-26 13:00:00 UTC2020-06-26 14:00:00 UTC000
Jun 26, 14:002020-06-26 14:00:00 UTC2020-06-26 15:00:00 UTC000
Jun 26, 15:002020-06-26 15:00:00 UTC2020-06-26 16:00:00 UTC000
Jun 26, 16:002020-06-26 16:00:00 UTC2020-06-26 17:00:00 UTC000
Jun 26, 17:002020-06-26 17:00:00 UTC2020-06-26 18:00:00 UTC000
Jun 26, 18:002020-06-26 18:00:00 UTC2020-06-26 19:00:00 UTC000
Jun 26, 19:002020-06-26 19:00:00 UTC2020-06-26 20:00:00 UTC000
Jun 26, 20:002020-06-26 20:00:00 UTC2020-06-26 21:00:00 UTC000
Jun 26, 21:002020-06-26 21:00:00 UTC2020-06-26 22:00:00 UTC000
Jun 26, 22:002020-06-26 22:00:00 UTC2020-06-26 23:00:00 UTC000
Jun 26, 23:002020-06-26 23:00:00 UTC2020-06-27 00:00:00 UTC000
Jun 27, 00:002020-06-27 00:00:00 UTC2020-06-27 01:00:00 UTC000
Jun 27, 01:002020-06-27 01:00:00 UTC2020-06-27 02:00:00 UTC000
Jun 27, 02:002020-06-27 02:00:00 UTC2020-06-27 03:00:00 UTC000
Jun 27, 03:002020-06-27 03:00:00 UTC2020-06-27 04:00:00 UTC000
Jun 27, 04:002020-06-27 04:00:00 UTC2020-06-27 05:00:00 UTC000
Jun 27, 05:002020-06-27 05:00:00 UTC2020-06-27 06:00:00 UTC000
Jun 27, 06:002020-06-27 06:00:00 UTC2020-06-27 07:00:00 UTC000
Jun 27, 07:002020-06-27 07:00:00 UTC2020-06-27 08:00:00 UTC000
Jun 27, 08:002020-06-27 08:00:00 UTC2020-06-27 09:00:00 UTC000
Jun 27, 09:002020-06-27 09:00:00 UTC2020-06-27 10:00:00 UTC101

What Hacker News says

1 sources
I don't think this is true. From Wikipedia [1]: > The heuristic function is problem-specific. If the heuristic function is admissible, meaning that it never overestimates the actual cost to get to the goal, A* is guaranteed to return a least-cost path from start to goal. In this case the euclidean does not overestimate so I would guess there is a bug in the implementation. [1] https://en.wikipedia.org/wiki/A*_search_algorithm Edit: Having taken a look at the source code I believe the problems mostly stem from the `addNeighboursToOpen` function [2]. It sets the distance and parent of unvisited neighbors of the current node. However this may happen multiple times for a node before it is actually visited. Meaning that the distance and parent is updated multiple times and the value at the end is not the optimal one. A simple fix would be to d
Read the rest
o a if check to see if the node already has a distance assigned. [2] https://github.com/Walker-TW/Algorithm-Visualizer/blob/maste...
In Algorithm-Visualizer

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.