Skip to content

Eddy identification and tracking

active 2023-09-052026-03-13 (UTC)

Complete coverage26,746 / 26,746 hourly files (100%) · 2 absent upstream2023-08-152026-09-02 (UTC)
Events
351
Pushes
24
Pull requests
5
Issues
81
Stars
58
Forks
17

Activity over time

Daily event counts in the loaded window

Line chart, 921 days from 2023-09-05 to 2026-03-13. Pushes: 24 total, peak 6 in a day. Pull requests: 5 total, peak 1 in a day. Issues: 81 total, peak 3 in a day. Comments: 163 total, peak 13 in a day. Stars: 58 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

Recent activity

Latest issues, pull requests and releases

  • Issue comment#272AntSimi2026-01-19 11:59
    Inquiry Regarding Eddy Detection Parameters in META3.2 for Higher Resolution Data
  • Issue#274shivashankar112025-12-29 09:56
    Problem in eddy identification with py-eddy-tracker
  • Issue comment#2724418372972025-12-20 03:27
    Inquiry Regarding Eddy Detection Parameters in META3.2 for Higher Resolution Data
  • Issue comment#266kyang7-code2025-12-13 03:17
    An error in plotting figure
  • Issue comment#272AntSimi2025-12-05 11:48
    Inquiry Regarding Eddy Detection Parameters in META3.2 for Higher Resolution Data
  • Issue comment#2724418372972025-11-23 13:53
    Inquiry Regarding Eddy Detection Parameters in META3.2 for Higher Resolution Data
  • Issue comment#271AntSimi2025-11-19 07:24
    pip-installed py-eddy-tracker detects only 1 eddy, while git clone version detects dozens to hundreds
  • Issue#269berzinastella2025-11-04 10:12
    eddy propagation direction
  • Issue#270Imaravel2025-07-08 21:32
    When loaded everything in the data is inverted.
  • Issue#270Imaravel2025-07-05 02:59
    When loaded everything in the data is inverted.
  • Issue comment#268AntSimi2025-06-18 14:20
    Request for help: No extrema found in contour of xx pixels in level xxxx
  • Issue comment#268pexu12025-06-17 05:26
    Request for help: No extrema found in contour of xx pixels in level xxxx
  • Issue#268pexu12025-06-17 05:21
    Request for help: No extrema found in contour of xx pixels in level xxxx
  • Pull request#267AntSimi2025-06-06 12:43
  • Issue comment#266Y0ruki2025-06-05 18:51
    An error in plotting figure
  • Issue comment#266Y0ruki2025-06-05 11:21
    An error in plotting figure
  • Issue comment#266AntSimi2025-06-05 09:30
    An error in plotting figure
  • Issue comment#266AntSimi2025-06-05 07:49
    An error in plotting figure
  • Issue comment#266AntSimi2025-06-03 08:34
    An error in plotting figure
  • Issue#261AntSimi2025-05-16 07:24
    Plotting eddies in cmems
  • Issue#251AntSimi2025-05-15 10:26
    tracking over long timeseries
  • Issue comment#257rba272025-03-25 19:12
    Struggling with write_file() function
  • Issue comment#263AntSimi2025-03-12 16:55
    py_eddy_tracker_sample.get_demo_path() error
  • Issue#263LauraGomezNavarro2025-03-12 10:40
    py_eddy_tracker_sample.get_demo_path() error
  • Issue comment#262dienjiehaihete2025-03-07 05:37
    EddyTracking tracking bug

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