nanoporetech / nanoporetech/minknow_api

Error: Ensure each CTC is inserted correctly before running check again

Open
#92 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
73
Forks
16
PR merge metrics
No merged PRs in 30d

Description

Hello,

I need to downgrade my MinKNOW installation to version 25.09.16 and the public downloads page only lists the current release. Can you help me providing a direct download link to the 25.09.16 Windows Installer?

The reason to doing so is that I am having an issue into checking the hardware with the CTC test and flowcell check. I get the message: "1 of 1 selected positions have failed the position check" - "Ensure each CTC is inserted correctly before running check again".

The problem is that it only occurs in the latest version of MinKNOW. I tried in another 2 computers with this newer version and the error occurs in all of them. Luckily I had the version 25.09.16 in a third computer and it passed the hardware check, however when I installed the newest version of MinKNOW it failed again. And I don't have any installers of the older versions.

Thanks in advance!

My setup:

  • Nanopore device: MinION Mk1D;
  • OS Windows 11 Pro
  • GPU is an RTX 5070 12GB;
  • 32 GB of RAM;
  • CPU is a Ryzen 7 7800X3D.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no source file, test, or entry point. First reproduce the CTC and flowcell check on a MinION Mk1D with Windows 11 using MinKNOW 25.09.16 and the latest release, then inspect the relevant issue or release-tracking entry. Done requires confirming the version-specific regression and either a fix or a documented resolution.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems, testing-qa
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.