Skip to content

fast and robust point pair feature

active 2023-08-182026-03-24 (UTC)

Complete coverage26,376 / 26,376 hourly files (100%) · 2 absent upstream2023-08-152026-08-17 (UTC)
Events
77
Pushes
2
Pull requests
0
Issues
11
Stars
29
Forks
5

Activity over time

Daily event counts in the loaded window

Line chart, 950 days from 2023-08-18 to 2026-03-24. Pushes: 2 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 11 total, peak 2 in a day. Comments: 30 total, peak 4 in a day. Stars: 29 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
SurfaceMan152012
XiaXingLuo11009
mwwzbinf6006
jiangzhiwei20184001
Yfanmeng3002
Bainily0282000
songhc81000
YuehChuan1000

Recent activity

Latest issues, pull requests and releases

  • Issue#15jiangzhiwei20182025-09-15 06:05
    Are there any optimization suggestions for CUDA acceleration in this project?
  • Issue#14YuehChuan2025-08-25 01:41
    Wrong pose
  • Issue#13songhc82025-02-25 07:27
    Why update point position when computing normal
  • Issue#12Bainily0282024-10-28 08:15
    The main algorithms involved in the code
  • Issue comment#12SurfaceMan2024-10-15 13:19
    The main algorithms involved in the code
  • Issue#12Bainily0282024-10-15 08:33
    The main algorithms involved in the code
  • Issue comment#11XiaXingLuo2024-06-19 02:27
    The results are different every time. A memory leak?
  • Issue comment#10XiaXingLuo2024-06-17 07:12
    Why are my matches skewed?
  • Issue comment#10XiaXingLuo2024-06-17 03:15
    Why are my matches skewed?
  • Issue comment#10Yfanmeng2024-06-15 07:47
    Why are my matches skewed?
  • Issue comment#10XiaXingLuo2024-06-15 07:24
    Why are my matches skewed?
  • Issue comment#11SurfaceMan2024-03-12 14:29
    The results are different every time. A memory leak?
  • Issue comment#11mwwzbinf2024-03-12 14:22
    The results are different every time. A memory leak?
  • Issue comment#11SurfaceMan2024-03-12 14:16
    The results are different every time. A memory leak?
  • Issue comment#11mwwzbinf2024-03-12 13:48
    The results are different every time. A memory leak?
  • Issue comment#11SurfaceMan2024-03-10 14:05
    The results are different every time. A memory leak?
  • Issue comment#11mwwzbinf2024-03-10 00:51
    The results are different every time. A memory leak?
  • Issue comment#11SurfaceMan2024-03-08 15:11
    The results are different every time. A memory leak?
  • Issue comment#11mwwzbinf2024-03-08 15:03
    The results are different every time. A memory leak?
  • Issue comment#11SurfaceMan2024-03-08 14:58
    The results are different every time. A memory leak?
  • Issue comment#11mwwzbinf2024-03-08 14:34
    The results are different every time. A memory leak?
  • Issue#2SurfaceMan2024-03-07 12:21
    Sample execution takes a long time
  • Issue comment#11SurfaceMan2024-03-07 12:19
    The results are different every time. A memory leak?
  • Issue comment#11mwwzbinf2024-03-07 00:38
    The results are different every time. A memory leak?
  • Issue comment#11SurfaceMan2024-03-05 14:42
    The results are different every time. A memory leak?

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 29 stars here means stars gained during the window, not the repo's star count.