Question about --glitches
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 302
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
thank you very nice for this nice tool! I am working on the analysis of repeat expansions in few human genes from different patients. Basically we amplify a target region containing some repetitive elements and then we sequence with Nanopore in order to estimate the length of the repetitive elements. Each patient has a different length of the repetitive elements which should appear with the analysis of the Nanopore data.
I am trying to use Badread in order to simulate reads from the same amplicon regions in order to evaluate how well we can estimate the repetitive content using a controlled dataset. I would like to know what is your recommendation for the "glitches" parameter. I noticed that in the help you suggested the settings for the "identity" parameter for an OK run, could you do provide the same suggestion for the "glitches" parameter? Is there a way to estimate the best settings starting from my own sequencing data in order to simulate reads which are very close to my real data?
Thank you very much for your support,
Riccardo
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is a usage question about Badread's --glitches and --identity settings, not a specified code change. Start with the existing help text and documentation for those parameters, then determine whether the requested recommendations can be documented from the user's Nanopore simulation context. Done would be a clear maintainer response or documentation update addressing suitable settings and how real sequencing data could inform them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- bioinformatics
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100