nanoporetech / nanoporetech/minknow_api
rebasecalling after a run using the api
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 73
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Hey,
Is it possible to start basecalling after a run has finished ? I tried to (using chatgpt/copilot) but it doesn't seem to find a solution.
As I understand these should be the steps :
- connect to MinKNOWN manager
- get the basecaller endpoint
- connect to basecaller service and start a basecall run ?
import grpc
from minknow_api.manager import Manager
from minknow_api.basecaller_service import Basecaller
manager = Manager(host="localhost", port=9501)
# 2. Discover available basecaller API ports
api_endpoints = manager.basecaller()
# in my case returned server:localhost port:9504
# 3. Connect to the basecaller service
channel = grpc.insecure_channel(f"{basecaller_host}:{basecaller_port}")
basecaller = Basecaller(channel)
# 4. Start basecalling
response = basecaller.start_basecalling(
input_reads_directories=["/path/pod5_skip"],
output_reads_directory="/path/basecalls",
configuration="dna_r10.4.1_e8.2_400bps_sup@v5.0.0"
)
This however doesn't seem the way as its giving me : status = StatusCode.UNAVAILABLE
Did I miss something ? Is there an example somewhere ? I checked start_protocol.py but that needs to connect to a position, which I don't have cause its a server not connected to ONT device directly. (its after the run)
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 start_protocol.py and the Manager and Basecaller usage shown in the issue, then trace how the basecaller endpoint is exposed for completed runs. Reproduce the StatusCode.UNAVAILABLE response with the provided connection flow. Done means documenting or demonstrating a working post-run basecalling workflow for a server without a directly connected ONT device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, python
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100