Skip to content

url-kaist/patchwork-plusplus

View on GitHub ↗Related repositories →

Patchwork++: Fast and robust ground segmentation method for 3D LiDAR scans. @ IROS'22

active 2024-11-232026-07-01 (UTC)

Partial coverage12,929 / 15,101 hourly files (86%) · 2 absent upstream · 2,166 failed, retryable2024-11-202026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
223
Pushes
20
Pull requests
6
Issues
12
Stars
134
Forks
14

Activity over time

Daily event counts in the loaded window

Line chart, 586 days from 2024-11-23 to 2026-07-01. Pushes: 20 total, peak 8 in a day. Pull requests: 6 total, peak 2 in a day. Issues: 12 total, peak 3 in a day. Comments: 13 total, peak 2 in a day. Stars: 134 total, peak 6 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
LimHyungTae322054
ewak5012
siyiovo3001
a1204712001
yichun-git2001
moonsheep992001
enricocovili2001
Navsea1000
Xuanrrr1001
youwyu1001

Recent activity

Latest issues, pull requests and releases

  • Pull request#100LimHyungTae2026-05-23 05:08
  • Pull request#82LimHyungTae2026-05-10 01:11
  • Issue#77LimHyungTae2026-05-09 23:55
    Are these two parameters elevation and flatness set incorrectly/reversed in code and the paper?
  • Issue#52LimHyungTae2026-05-09 23:53
    How to set parameters for this type of point cloud
  • Issue comment#52LimHyungTae2026-05-09 23:53
    How to set parameters for this type of point cloud
  • Issue comment#75LimHyungTae2026-05-09 23:52
    Using Patchwork++ for Stereo Depth?
  • Issue#62LimHyungTae2026-05-09 23:18
    Question about input pointcloud
  • Pull request#79LimHyungTae2026-05-09 06:47
  • Issue comment#73yichun-git2025-09-21 15:23
    Patchwork++ for customed dataset
  • Issue#73yichun-git2025-09-21 12:04
    Patchwork++ for customed dataset
  • Issue#70siyiovo2025-03-27 05:32
    Question of inverted LiDAR
  • Issue comment#70siyiovo2025-03-16 14:03
    Question of inverted LiDAR
  • Issue#70siyiovo2025-03-16 10:18
    Question of inverted LiDAR
  • Issue comment#67ewak2025-03-12 00:21
    patchworkpp_ros::utils::EigenMatToPointCloud2() should use points.rows(), NOT points.size() when calling CreatePointCloud2Msg()
  • Issue#67ewak2025-03-12 00:21
    patchworkpp_ros::utils::EigenMatToPointCloud2() should use points.rows(), NOT points.size() when calling CreatePointCloud2Msg()
  • Issue#69Navsea2025-01-22 04:44
    Question about ringwise_flatness
  • Issue comment#60a1204712025-01-22 00:35
    Question about FP ground points in distant sectors
  • Issue#60a1204712025-01-22 00:35
    Question about FP ground points in distant sectors
  • Issue comment#67ewak2025-01-08 03:56
    patchworkpp_ros::utils::EigenMatToPointCloud2() should use points.rows(), NOT points.size() when calling CreatePointCloud2Msg()
  • Pull request#68ewak2025-01-08 03:50
  • Issue#67ewak2025-01-08 03:46
    patchworkpp_ros::utils::EigenMatToPointCloud2() should use points.rows(), NOT points.size() when calling CreatePointCloud2Msg()
  • Issue comment#59Xuanrrr2024-12-27 14:30
    Request for Assistance with Parameter Tuning in Patchwork++ for Ground Segmentation in ROS1
  • Issue comment#5youwyu2024-12-25 03:16
    About patchwork++ parameters
  • Issue#61moonsheep992024-12-21 05:57
    About the parameters in different environments
  • Issue comment#61moonsheep992024-12-21 05:57
    About the parameters in different environments

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