Skip to content

CPP-Aerial-Vision-Analysis-System/progress-tracker

View on GitHub ↗Related repositories →

DO NOT TOUCH.

active 2024-09-072025-06-13 (UTC)

Complete coverage26,333 / 26,333 hourly files (100%) · 2 absent upstream2023-08-152026-08-16 (UTC)
Events
125
Pushes
0
Pull requests
0
Issues
123
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 280 days from 2024-09-07 to 2025-06-13. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 123 total, peak 47 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 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
dkingryan69000
joestrada102252000
Kestrel861000
suas-jetson1000

Recent activity

Latest issues, pull requests and releases

  • Issue#45suas-jetson2025-06-13 16:04
    Look into geofence feature mission planner
  • Issue#71dkingryan2025-06-11 20:32
    test out yolov8 versions L and X to see if jetson can handle them. also test out with imgsz set to 1280 instead of default (640)
  • Issue#42dkingryan2025-06-11 20:32
    gcs logger node
  • Issue#75dkingryan2025-06-11 20:28
    integrate payload drop with inserted waypoint
  • Issue#73dkingryan2025-06-11 20:27
    put mapping on jetson and figure out when to trigger it within the mission
  • Issue#84dkingryan2025-06-11 20:27
    make lap updating dynamic based on position of first inserted waypoint instead of just == 2
  • Issue#85dkingryan2025-06-11 20:27
    make message sent to mission planner once mapping transfer to usb is done
  • Issue#89dkingryan2025-06-11 20:26
    switch from loiter to guided
  • Issue#88dkingryan2025-06-11 02:59
    make mapping automatic by finding last do digi cam
  • Issue#90dkingryan2025-06-11 02:09
    unmount usb from jetson
  • Issue#89dkingryan2025-06-11 02:07
    switch from loiter to guided
  • Issue#87dkingryan2025-06-11 02:05
    make it unsubscribe from track node for mapping
  • Issue#81dkingryan2025-06-04 05:24
    why did the mission disappear on mission planner
  • Issue#80dkingryan2025-06-03 00:00
    figure out why it did an extra lap for simulation
  • Issue#50dkingryan2025-06-02 23:59
    test out launcher.sh on jetson
  • Issue#38dkingryan2025-06-02 23:59
    find a different way of launching nodes instead of launcher.py
  • Issue#86joestrada10222025-05-29 17:46
    add mission pull on restart
  • Issue#53joestrada10222025-05-29 16:29
    Make it save the photo that led to a detection
  • Issue#85joestrada10222025-05-28 03:26
    make message sent to mission planner once mapping transfer to usb is done
  • Issue#84joestrada10222025-05-28 00:36
    make lap updating dynamic based on position of first inserted waypoint instead of just == 2
  • Issue#48dkingryan2025-05-26 22:27
    Gps calculation
  • Issue#83dkingryan2025-05-26 20:44
    potentially make a new node for the plane scenario and have it where if we send a message on missionplanner like "resume" it resumes the mission
  • Issue#83dkingryan2025-05-26 07:41
    potentially make a new node for the plane scenario and have it where if we send a message on missionplanner like "resume" it resumes the mission
  • Issue#82dkingryan2025-05-26 07:40
    ask how we make drone fly. is the sequence guided -> arm - > auto -> mission take off
  • Issue#81dkingryan2025-05-25 19:18
    why did the mission disappear on mission planner

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