nanoporetech / nanoporetech/minknow_api
Set minimum chunk size for adaptive sequencing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 73
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I would like to perform adaptive sequencing ("Read Until") on a dataset with relatively short reads. As a result, if I want to gain significant benefit from selective sequencing, reads need to be ejected as soon as possible. In order to do so, I would like to reduce MinKnow's default read chunk size.
According to the comments in this repository, the configuration is stored in minknow/conf/app_conf. This is incorrect and should be updated; this information is now stored in minknow/conf/tuning_params.toml.
Would you additionally be able to explain the difference between the following configuration options in minknow/conf/tuning_params.toml:
raw_data_intermediateraw_meta_data_intermediateread_data_intermediateevent_data_intermediate
Are there any limitations I should be aware of in terms of how low I can set these parameters? I assume once the data packets are too fragmented it becomes difficult to write them in real time. It looks like the default values are already significantly lower than they used to be (400 samples, not 2000). Is that correct?
Contributor guide
No contributing guide indexed for this repository
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
Start with the configuration comment in minknow_api/data.proto and compare it with minknow/conf/tuning_params.toml. Trace the four named parameters and their documented defaults or limits, then update the configuration location and explain their differences and constraints in the issue or relevant documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, python
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100