home.social

#p2solo — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #p2solo, aggregated by home.social.

fetched live
  1. @nanopore We're running another lot of cDNA samples on our P2 Solo. Flow cell loading and available pores looks great. Not quite a full sea of green, but that's to be expected from an older PromethION flow cell. They seem to be more time-sensitive than the MinION and Flongle flow cells.

    #P2Solo

  2. @nanopore We're running another lot of cDNA samples on our P2 Solo. Flow cell loading and available pores looks great. Not quite a full sea of green, but that's to be expected from an older PromethION flow cell. They seem to be more time-sensitive than the MinION and Flongle flow cells.

    #P2Solo

  3. @nanopore We're running another lot of cDNA samples on our P2 Solo. Flow cell loading and available pores looks great. Not quite a full sea of green, but that's to be expected from an older PromethION flow cell. They seem to be more time-sensitive than the MinION and Flongle flow cells.

    #P2Solo

  4. @nanopore We're running another lot of cDNA samples on our P2 Solo. Flow cell loading and available pores looks great. Not quite a full sea of green, but that's to be expected from an older PromethION flow cell. They seem to be more time-sensitive than the MinION and Flongle flow cells.

    #P2Solo

  5. @nanopore We're running another lot of cDNA samples on our P2 Solo. Flow cell loading and available pores looks great. Not quite a full sea of green, but that's to be expected from an older PromethION flow cell. They seem to be more time-sensitive than the MinION and Flongle flow cells.

    #P2Solo

  6. @nanopore Super-accuracy basecalling is done for our most recent P2 Solo runs. I'm seeing about q20 modal accuracy from mapped reads.

    #p2Solo #cDNA #nanopore

  7. @nanopore Super-accuracy basecalling is done for our most recent P2 Solo runs. I'm seeing about q20 modal accuracy from mapped reads.

    #p2Solo #cDNA #nanopore

  8. @nanopore Super-accuracy basecalling is done for our most recent P2 Solo runs. I'm seeing about q20 modal accuracy from mapped reads.

    #p2Solo #cDNA #nanopore

  9. @nanopore Super-accuracy basecalling is done for our most recent P2 Solo runs. I'm seeing about q20 modal accuracy from mapped reads.

    #p2Solo #cDNA #nanopore

  10. @nanopore Super-accuracy basecalling is done for our most recent P2 Solo runs. I'm seeing about q20 modal accuracy from mapped reads.

    #p2Solo #cDNA #nanopore

  11. @nanopore I now have a comparison of the same sample on Flongle (cleanup using SFB) and PromethION (cleanup using LFB) flow cells.

    These were both called with the new bacterial caller in simplex mode. According to LAST-train, the qScore-adjusted substitution accuracy for the Flongle was q41, and the qScore-adjusted substitution accuracy for the PromethION was q45.

    #P2Solo #DNAladder

  12. @nanopore I now have a comparison of the same sample on Flongle (cleanup using SFB) and PromethION (cleanup using LFB) flow cells.

    These were both called with the new bacterial caller in simplex mode. According to LAST-train, the qScore-adjusted substitution accuracy for the Flongle was q41, and the qScore-adjusted substitution accuracy for the PromethION was q45.

    #P2Solo #DNAladder

  13. @nanopore I now have a comparison of the same sample on Flongle (cleanup using SFB) and PromethION (cleanup using LFB) flow cells.

    These were both called with the new bacterial caller in simplex mode. According to LAST-train, the qScore-adjusted substitution accuracy for the Flongle was q41, and the qScore-adjusted substitution accuracy for the PromethION was q45.

    #P2Solo #DNAladder

  14. @nanopore I now have a comparison of the same sample on Flongle (cleanup using SFB) and PromethION (cleanup using LFB) flow cells.

    These were both called with the new bacterial caller in simplex mode. According to LAST-train, the qScore-adjusted substitution accuracy for the Flongle was q41, and the qScore-adjusted substitution accuracy for the PromethION was q45.

    #P2Solo #DNAladder

  15. @nanopore I now have a comparison of the same sample on Flongle (cleanup using SFB) and PromethION (cleanup using LFB) flow cells.

    These were both called with the new bacterial caller in simplex mode. According to LAST-train, the qScore-adjusted substitution accuracy for the Flongle was q41, and the qScore-adjusted substitution accuracy for the PromethION was q45.

    #P2Solo #DNAladder

  16. @nanopore hmm... looks like I messed up on the 3kb and 1.5kb ladder bands.

    This new kmer-based mapper seems to be doing the right things, though. I'm very pleased.

    #DNAladder #P2Solo

  17. @nanopore hmm... looks like I messed up on the 3kb and 1.5kb ladder bands.

    This new kmer-based mapper seems to be doing the right things, though. I'm very pleased.

    #DNAladder #P2Solo

  18. @nanopore hmm... looks like I messed up on the 3kb and 1.5kb ladder bands.

    This new kmer-based mapper seems to be doing the right things, though. I'm very pleased.

    #DNAladder #P2Solo

  19. @nanopore hmm... looks like I messed up on the 3kb and 1.5kb ladder bands.

    This new kmer-based mapper seems to be doing the right things, though. I'm very pleased.

    #DNAladder #P2Solo

  20. @nanopore hmm... looks like I messed up on the 3kb and 1.5kb ladder bands.

    This new kmer-based mapper seems to be doing the right things, though. I'm very pleased.

    #DNAladder #P2Solo

  21. #P2Solo Data upload to our experimental archive. 641.15 GB of raw pod5 files. This was the lower end of acceptable data output for a P2 Solo run (about 50 Gb of sequence data).

  22. #P2Solo Data upload to our experimental archive. 641.15 GB of raw pod5 files. This was the lower end of acceptable data output for a P2 Solo run (about 50 Gb of sequence data).

  23. #P2Solo Data upload to our experimental archive. 641.15 GB of raw pod5 files. This was the lower end of acceptable data output for a P2 Solo run (about 50 Gb of sequence data).

  24. #P2Solo Data upload to our experimental archive. 641.15 GB of raw pod5 files. This was the lower end of acceptable data output for a P2 Solo run (about 50 Gb of sequence data).

  25. #P2Solo Data upload to our experimental archive. 641.15 GB of raw pod5 files. This was the lower end of acceptable data output for a P2 Solo run (about 50 Gb of sequence data).

  26. @nanopore #P2Solo another cDNA run that has exceeded 25M reads. The computer froze [again] in the middle of a sequencing run, after getting 6.24M reads, but I now have >25M reads from after the restart.

    [FWIW, I care about 25M because that's the maximum that could ever be generated from a single Revio run, assuming perfect performance from all ZMWs]

  27. @nanopore #P2Solo another cDNA run that has exceeded 25M reads. The computer froze [again] in the middle of a sequencing run, after getting 6.24M reads, but I now have >25M reads from after the restart.

    [FWIW, I care about 25M because that's the maximum that could ever be generated from a single Revio run, assuming perfect performance from all ZMWs]

  28. @nanopore #P2Solo another cDNA run that has exceeded 25M reads. The computer froze [again] in the middle of a sequencing run, after getting 6.24M reads, but I now have >25M reads from after the restart.

    [FWIW, I care about 25M because that's the maximum that could ever be generated from a single Revio run, assuming perfect performance from all ZMWs]

  29. @nanopore #P2Solo another cDNA run that has exceeded 25M reads. The computer froze [again] in the middle of a sequencing run, after getting 6.24M reads, but I now have >25M reads from after the restart.

    [FWIW, I care about 25M because that's the maximum that could ever be generated from a single Revio run, assuming perfect performance from all ZMWs]

  30. @nanopore #P2Solo another cDNA run that has exceeded 25M reads. The computer froze [again] in the middle of a sequencing run, after getting 6.24M reads, but I now have >25M reads from after the restart.

    [FWIW, I care about 25M because that's the maximum that could ever be generated from a single Revio run, assuming perfect performance from all ZMWs]

  31. @nanopore Canu-corrected #P2Solo read, demonstrating qInf (i.e. 100% accuracy)

  32. @nanopore Canu-corrected #P2Solo read, demonstrating qInf (i.e. 100% accuracy)

  33. @nanopore Canu-corrected #P2Solo read, demonstrating qInf (i.e. 100% accuracy)

  34. @nanopore Canu-corrected #P2Solo read, demonstrating qInf (i.e. 100% accuracy)

  35. @nanopore Canu-corrected #P2Solo read, demonstrating qInf (i.e. 100% accuracy)

  36. #P2Solo @nanopore Currently sequencing *Nippostrongylus brasiliensis* on a PromethION flow cell, prepared using LSK114 ligation sequencing kit (using ligase enzyme that is about 2 years past its claimed expiry date).

    We're about 50 minutes into the run, and it has covered the 300~400Mb genome about 5 times.

    I'm hoping to get coverage above 30X before flow cell degredation sets in. If, against the odds, the flow cell survives for a long time, I might get enough reads for a population analysis.

  37. #P2Solo @nanopore Currently sequencing *Nippostrongylus brasiliensis* on a PromethION flow cell, prepared using LSK114 ligation sequencing kit (using ligase enzyme that is about 2 years past its claimed expiry date).

    We're about 50 minutes into the run, and it has covered the 300~400Mb genome about 5 times.

    I'm hoping to get coverage above 30X before flow cell degredation sets in. If, against the odds, the flow cell survives for a long time, I might get enough reads for a population analysis.

  38. #P2Solo @nanopore Currently sequencing *Nippostrongylus brasiliensis* on a PromethION flow cell, prepared using LSK114 ligation sequencing kit (using ligase enzyme that is about 2 years past its claimed expiry date).

    We're about 50 minutes into the run, and it has covered the 300~400Mb genome about 5 times.

    I'm hoping to get coverage above 30X before flow cell degredation sets in. If, against the odds, the flow cell survives for a long time, I might get enough reads for a population analysis.

  39. #P2Solo @nanopore Currently sequencing *Nippostrongylus brasiliensis* on a PromethION flow cell, prepared using LSK114 ligation sequencing kit (using ligase enzyme that is about 2 years past its claimed expiry date).

    We're about 50 minutes into the run, and it has covered the 300~400Mb genome about 5 times.

    I'm hoping to get coverage above 30X before flow cell degredation sets in. If, against the odds, the flow cell survives for a long time, I might get enough reads for a population analysis.

  40. #P2Solo @nanopore Currently sequencing *Nippostrongylus brasiliensis* on a PromethION flow cell, prepared using LSK114 ligation sequencing kit (using ligase enzyme that is about 2 years past its claimed expiry date).

    We're about 50 minutes into the run, and it has covered the 300~400Mb genome about 5 times.

    I'm hoping to get coverage above 30X before flow cell degredation sets in. If, against the odds, the flow cell survives for a long time, I might get enough reads for a population analysis.

  41. @nanopore #P2Solo digital electrophoresis plot showing estimated tail lengths from various cDNA samples (bottom two lines are after two PCR cycles; all the others are after 14 PCR cycles).

  42. @nanopore #P2Solo digital electrophoresis plot showing estimated tail lengths from various cDNA samples (bottom two lines are after two PCR cycles; all the others are after 14 PCR cycles).

  43. @nanopore #P2Solo digital electrophoresis plot showing estimated tail lengths from various cDNA samples (bottom two lines are after two PCR cycles; all the others are after 14 PCR cycles).

  44. @nanopore #P2Solo digital electrophoresis plot showing estimated tail lengths from various cDNA samples (bottom two lines are after two PCR cycles; all the others are after 14 PCR cycles).

  45. @nanopore #P2Solo digital electrophoresis plot showing estimated tail lengths from various cDNA samples (bottom two lines are after two PCR cycles; all the others are after 14 PCR cycles).