Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

README: the green and red points are swapped (green = .fset tracking, red = .fset3 detection)

Open Beginner friendly
  • Is something wrong?
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
documentation

Research direction

Read the README’s “What you get” section and compare its color descriptions with the .fset and .fset3 behavior outlined in the issue. Update the wording wherever the demo text repeats the mix-up; done when it consistently describes .fset tracking points as green and .fset3 detection points as red.

Written by the indexing model from the issue text.

Description

The README says the demo draws the detection feature points as light green circles and the tracking points as small red circles ("What you get"). The code does the opposite:

  • .fset is read with ar2ReadSurfaceSet(path, "fset") (AR2 tracking data), becomes nftPoints, and is drawn light green (#34FF19, radius 10).
  • .fset3 is read with kpmLoadRefDataSet(path, "fset3") (KPM detection data), becomes nftFsetPoints, and is drawn red (#FF0119, radius 4).

For the pinball marker the demo draws 165 green and 4850 red circles, matching the log lines "NFT number of feature points: 165" (.fset) and "num = 4850" (.fset3).

WebARKitLib agrees: ARToolKitNFTCore detects with KPM, then hands the pose to AR2 with ar2SetInitTrans, which tracks.

Suggested fix: swap the wording in the README ("What you get") and anywhere else the demo text says the same.

Dominant language
JavaScript
Stars
8
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from webarkit/FeatureSET-Display

All issues in webarkit/FeatureSET-Display

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.