Not sure if the Dorado version slorado uses will give you the same network problem or not.

What are you using Dorado for? If you only need FASTQ output and no modifications, then maybe @hasindu2008.bsky.social and company might have a tool might work. For example BonsonW/slorado: A simplified version of Dorado built on top of S/BLOW5 format. share.google/Kc5sVXTWawcD... might work.

does sup@v5.0.0 or sup@v5.2.0 look similar to the predicted vs actual/empirical? In other words does sup look like hyper?

I think you should double check this. I could have sworn there was an announcement of a 2×500 kit or was that for the NovaSeq?

Tagging with #Julialang

Well, if you have AMD GPUs Slorado | slorado share.google/y5aV5QzNwVXC...

And there is a new one coming in 2027- do not have a link handy.

If you decide to add hi-c later, you might be able to reuse some of the same binary intermediate files from hifiasm from the initial assembly for the hi-c assembly

On second thought, you could use hifiasm and --ont option like @psy-fer.bsky.social suggested and use the Illumina reads for k-mer evaluation such as completeness, assembly quality value, etc with Merqry or yak ( from @lh3lh3.bsky.social ).

If you plan on Hi-C, I did get good results a few years ago with error-correct PacBio first with graphaligner, Flye corr, Octopus for polishing, and yahs for Hi-C scaffolding. See more details here - github.com/jelber2/geno...

Wait? So are you at Uni Greifswald or Uni Münster?

Thank you Tommy!
The link you gave is good but points to a 2yr old rendering. This one uses recent versions of R and all packages and has all the latest typo fixes:
www.huber.embl.de/msmb/

Yes, it has worked really well. I should mention that I'm porting to the Godot game engine. Zig and Claude work great together, but Godot brings some advantages that outweigh how well they work together. Godot brings WebGL support, platform pipeline, visual UI editor, and some debugging tools.

Are you successfully vibe coding in #ziglang? If so, I am interested.

There is also a branch that takes nanopore reads as input, which works reasonably well. We are putting some final code touches on it, but maybe helpful - github.com/wwood/single...