Skip to content

A pipeline for nanopore long-read metagenomic analysis.

active 2024-02-262026-04-12 (UTC)

Complete coverage26,780 / 26,780 hourly files (100%) · 2 absent upstream2023-08-152026-09-03 (UTC)
Events
293
Pushes
197
Pull requests
1
Issues
10
Stars
46
Forks
4

Activity over time

Daily event counts in the loaded window

Line chart, 777 days from 2024-02-26 to 2026-04-12. Pushes: 197 total, peak 36 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 10 total, peak 5 in a day. Comments: 9 total, peak 7 in a day. Stars: 46 total, peak 5 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
P-kai20619704
Syngenome4001
asogg2001
changan5222002
Lexu71001
JinwnK1000
YongxinLiu1010

Recent activity

Latest issues, pull requests and releases

  • Issue#9P-kai2025-11-28 05:33
    Figshare Download Returns 403 Forbidden
  • ReleaseP-kai2025-11-26 04:32
    v1.0.2
  • Issue#9JinwnK2025-11-26 03:50
    Figshare Download Returns 403 Forbidden
  • Issue comment#6changan5222025-04-29 11:42
    issue with GTDB-Tk 2.2.6 and Pydantic 2.7.
  • Issue comment#6asogg2025-04-29 09:54
    issue with GTDB-Tk 2.2.6 and Pydantic 2.7.
  • Issue#6P-kai2025-04-25 09:16
    issue with GTDB-Tk 2.2.6 and Pydantic 2.7.
  • Issue comment#6changan5222025-04-25 06:13
    issue with GTDB-Tk 2.2.6 and Pydantic 2.7.
  • Issue comment#8P-kai2025-04-25 04:39
    if the pipiline interupted/ closed during run due to power failure, is it possible to continue or resume from the point of stop.. if so, what command to use addtionally?
  • Issue comment#8Syngenome2025-04-25 04:05
    if the pipiline interupted/ closed during run due to power failure, is it possible to continue or resume from the point of stop.. if so, what command to use addtionally?
  • Issue#8P-kai2025-04-25 04:03
    if the pipiline interupted/ closed during run due to power failure, is it possible to continue or resume from the point of stop.. if so, what command to use addtionally?
  • Issue comment#8P-kai2025-04-25 03:41
    if the pipiline interupted/ closed during run due to power failure, is it possible to continue or resume from the point of stop.. if so, what command to use addtionally?
  • Issue#8Syngenome2025-04-25 03:04
    if the pipiline interupted/ closed during run due to power failure, is it possible to continue or resume from the point of stop.. if so, what command to use addtionally?
  • Issue#4P-kai2025-04-25 02:04
    Why do you specifically use Python to develop bioinformatics workflows?
  • Issue comment#4P-kai2025-04-25 02:04
    Why do you specifically use Python to develop bioinformatics workflows?
  • Issue#7P-kai2025-04-25 01:56
    downstream steps
  • Issue comment#7P-kai2025-04-25 01:55
    downstream steps
  • Issue comment#7Lexu72025-04-25 01:53
    downstream steps
  • Issue#5Syngenome2025-04-24 16:45
    easynanometa.sif
  • Issue#6asogg2025-04-16 13:57
    issue with GTDB-Tk 2.2.6 and Pydantic 2.7.
  • Issue#5Syngenome2025-04-12 14:31
    easynanometa.sif
  • ReleaseP-kai2024-11-25 01:34
    v1.0.1
  • ReleaseP-kai2024-09-24 03:04
    v1.0.0
  • Pull request#3YongxinLiu2024-07-28 05:43

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