Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

estimated pass threshold with default settings very high (v0.5.0 and v.0.6.1)

Chiusa
#611 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
rust

Direzione di ricerca

Start with the modkit pileup and sample probs entry points using the default settings, reproducing the reported thresholds and comparing them with the documented lowest-10% behavior. Trace the threshold calculation from the logfile output and probability distributions; the issue is done when the threshold follows the intended percentile or the behavior and fix are clearly documented.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

troubleshooting

Hi!

I ran modkit pileup (v.0.5.0) on one of my ONT samples for 5mC and noticed that the pass threshold with the default settings was put very high. A lot of methylated calls were filtered out giving very low percentages. This is what the logfile shows:
estimated threshold too high 1, using 0.9941406

I also tried runnning it with the newer version (v0.6.1), but got the same issue. This is what the log file shows:
estimated threshold too high 1, using 0.9746094 (maximum explicit canonical probability)

I also ran the sample probs to see what the thresholds and distribution looks like. The threshold was the same as for the pileup for both versions, put at 1:
base percentile threshold
C 10 1
C 50 1
C 90 1

I understood from the documentation that with the default settings, the lowest 10% of probabilities are filtered out. But when i look at the probability distributions of this sample it does not seem to put the pass threshold at the 10th lowest percentile, but a lot higher (see attached picture)? This leads to the majority of data not passing the threshold and being filtered out.

For reference, all my ONT samples get the exact same threshold put. I've played around with the filter settings myself, but there is no best practice for what threshold to put it at (yet) so this is not the best option for me at this moment.

Could you tell me why this happens and how I could fix it?
Image

Lingua principale
Rust
Stelle
280
Fork
35
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nanoporetech/modkit

Tutte le issue di nanoporetech/modkit

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.