![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Troubleshooting: Nexseq run completed but status is "failed" | thiNGS | Illumina/Solexa | 5 | 02-17-2018 08:15 AM |
blast "returned non-zero exit status 137" error, memory problems | adpolicarpo | Bioinformatics | 9 | 05-26-2015 05:11 AM |
MiSeq gDNA reads still fail "Kmer content" and "per base seq content" after trimming" | ysnapus | Illumina/Solexa | 4 | 11-12-2014 07:25 AM |
Forget to add "-I" option while run bwa aln | MissDona | Bioinformatics | 1 | 09-01-2013 05:30 AM |
![]() |
|
Thread Tools |
![]() |
#1 |
Junior Member
Location: Russia Join Date: Jan 2022
Posts: 3
|
![]()
Hello everyone! I need help.
Our last run is still on uploading stage. Is any way to trigger the next step (fastq generation)? Instr: NextSeq500 Illumina Basespce Thank you |
![]() |
![]() |
![]() |
#2 |
Junior Member
Location: Vancouver Join Date: Oct 2013
Posts: 2
|
![]()
This happened to me a few times. It was due to the internet connection dropping while the run was going/uploading. I contacted illumina basespace tech support. I verified with them that the entire run was uploaded and they manually triggered the fastq gen script on their end.
|
![]() |
![]() |
![]() |
#3 |
Junior Member
Location: Russia Join Date: Jan 2022
Posts: 3
|
![]()
Thank you. We contacted Illumina for support. In our case, the solution was to turn the instrument off and on again (facepalm)
|
![]() |
![]() |
![]() |
Thread Tools | |
|
|