Skip to content

Official PyTorch implementation of "Towards More Practical Group Activity Detection: A New Benchmark and Model"

active 2023-12-062026-03-13 (UTC)

Partial coverage22,947 / 26,312 hourly files (87%) · 2 absent upstream · 3,364 failed, retryable2023-08-152026-08-15 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
44
Pushes
5
Pull requests
0
Issues
13
Stars
11
Forks
1

Activity over time

Daily event counts in the loaded window

Line chart, 829 days from 2023-12-06 to 2026-03-13. Pushes: 5 total, peak 4 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 13 total, peak 2 in a day. Comments: 14 total, peak 3 in a day. Stars: 11 total, peak 1 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
dk-kim205012
JihuaPeng6001
remember90693001
LHYUNMIN1000
nianfd1000
pupubushilulu1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#12dk-kim2025-08-19 00:18
    Social-CAD and JRDB-act
  • Issue comment#11dk-kim2025-08-19 00:18
    the code for Social-CAD and JRDB-act
  • Issue#7dk-kim2025-08-19 00:12
    why set image_width = 1280 and image_height = 720?
  • Issue#11pupubushilulu2025-05-16 07:19
    the code for Social-CAD and JRDB-act
  • Issue comment#10dk-kim2025-04-30 03:30
    when setting the batch size to 4, the result is worse than that in the paper
  • Issue comment#8dk-kim2025-04-30 03:20
    Request for Camera Parameters of 4 views
  • Issue#2dk-kim2025-04-30 03:18
    Questions Regarding the Algorithm in Your Paper
  • Issue#1dk-kim2025-04-30 03:18
    could the model work without tracks?
  • Issue#10JihuaPeng2025-04-27 14:11
    when setting the batch size to 4, the result is worse than that in the paper
  • Issue#9remember90692025-04-06 22:58
    Overfitting and Reproducibility concerns
  • Issue comment#9dk-kim2025-04-04 08:18
    Overfitting and Reproducibility concerns
  • Issue#9remember90692025-03-27 03:04
    Overfitting and Reproducibility concerns
  • Issue comment#7dk-kim2025-02-24 02:13
    why set image_width = 1280 and image_height = 720?
  • Issue comment#7remember90692025-02-22 20:12
    why set image_width = 1280 and image_height = 720?
  • Issue comment#7dk-kim2025-02-17 15:19
    why set image_width = 1280 and image_height = 720?
  • Issue#7nianfd2025-02-16 15:49
    why set image_width = 1280 and image_height = 720?
  • Issue#6JihuaPeng2024-10-30 03:46
    train.py: error: argument --groundtruth: can't open './evaluation/gt_tracks_24.txt': [Errno 2] No such file or directory: './evaluation/gt_tracks_24.txt'
  • Issue comment#6dk-kim2024-10-29 02:29
    train.py: error: argument --groundtruth: can't open './evaluation/gt_tracks_24.txt': [Errno 2] No such file or directory: './evaluation/gt_tracks_24.txt'
  • Issue#5JihuaPeng2024-10-28 06:58
    ModuleNotFoundError: No module named 'RoIAlign.roi_align.crop_and_resize_gpu'
  • Issue#4JihuaPeng2024-10-16 06:27
    Download the Cafe dataset in the linux system
  • Issue comment#3dk-kim2024-10-15 07:57
    How to test the custom video?
  • Issue comment#3JihuaPeng2024-10-15 07:15
    How to test the custom video?
  • Issue comment#3dk-kim2024-10-15 07:06
    How to test the custom video?
  • Issue#3JihuaPeng2024-10-15 06:54
    How to test the custom video?
  • Issue comment#2dk-kim2024-10-14 05:31
    Questions Regarding the Algorithm in Your Paper

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