Argo Technical Community of Practice
active 2025-04-07 → 2026-01-14 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 283 days from 2025-04-07 to 2026-01-14. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 24 total, peak 20 in a day. Comments: 7 total, peak 4 in a day. Stars: 1 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| cgrdn | 29 | 0 | 0 | 5 |
| EdLeymarie | 1 | 0 | 0 | 1 |
| RomainCancouet | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#23EdLeymarie2025-10-24 16:05Recommend default settings for sensors and expected interaction with float controller board
- Issue#24cgrdn2025-10-24 15:57Coordinate with TTT sensor tasks, likely other tasks in common especially on BGC side
- Issue#24cgrdn2025-10-24 15:56Coordinate with TTT sensor tasks, likely other tasks in common especially on BGC side
- Issue#22cgrdn2025-10-21 19:10Establish system for storing current best practices, application notes, etc.
- Issue comment#6RomainCancouet2025-06-05 07:36Enhance understanding of float failure modes.
- Issue comment#21cgrdn2025-06-04 21:40Installation (or not) of TBT in CTDs before delivery to end-user
- Issue#21cgrdn2025-06-04 21:35Installation (or not) of TBT in CTDs before delivery to end-user
- Issue#20cgrdn2025-04-07 01:50User groups will use ticketing systems provided by vendors for all float issues. Manufacturers will ensure their responsiveness.
- Issue comment#19cgrdn2025-04-07 01:49Argo Tech will send a representative to the UNOLS RVTEC (Research Vessel Technical Enhancement Committee) meeting annually.
- Issue#19cgrdn2025-04-07 01:48Argo Tech will send a representative to the UNOLS RVTEC (Research Vessel Technical Enhancement Committee) meeting annually.
- Issue#18cgrdn2025-04-07 01:47Ability to check voltage on individual battery packs without opening the float on future platforms or alternative method to verify all packs are connected to the controller
- Issue#17cgrdn2025-04-07 01:47Enhanced language surrounding float performance.
- Issue#16cgrdn2025-04-07 01:47Temperature tracking throughout shipping.
- Issue comment#15cgrdn2025-04-07 01:46Clarification of SBS commercial and hardware nomenclature.
- Issue#15cgrdn2025-04-07 01:45Clarification of SBS commercial and hardware nomenclature.
- Issue#14cgrdn2025-04-07 01:45Results for a zero frequency test stored on board SBS CTD sensors in the same way as calibration coefficients
- Issue#13cgrdn2025-04-07 01:44How can users efficiently access manufacturer test results?
- Issue#12cgrdn2025-04-07 01:44Float depth control and pressure sensor requirements for end of life.
- Issue#11cgrdn2025-04-07 01:44Include humidity sensors in floats for leak detection.
- Issue#10cgrdn2025-04-07 01:43Energy budget determination for float missions
- Issue#9cgrdn2025-04-07 01:43Recommend best practices for float testing.
- Issue#8cgrdn2025-04-07 01:43Map appropriate float parameters to meta file variables, manufacturers and users log during checks.
- Issue#7cgrdn2025-04-07 01:42Improve fault identification and record-keeping.
- Issue#6cgrdn2025-04-07 01:42Enhance understanding of float failure modes.
- Issue#5cgrdn2025-04-07 01:41Create default profiling regimes. This includes cycle timing (not equal to integer number of days), vertical resolution, and park depth sampling.
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.