In a de novo genome assembly using Tell-Seq, why does Universal sequencing Tell-read pipelines generate "erroeneous barcode" files "?
0
0
Entering edit mode
19 months ago
Vijith ▴ 30

Hi

I have recently started a bioinformatics project, i.e de novo assembly of reads generated from Novaseq 6000. I have been using universal sequencing Tell-Seq software package for the purpose. As of now, I am at the stage where it generates linked-reads using "Tell-read" pipelines. This is supposed to generate files such as, run190530_I1_T503.fastq.gz.corrected.fastq.err_barcode_removed.fastq.gz, run190530_R1_T503.fastq.gz.corrected.fastq.err_barcode_removed.fastq.gz, and run190530_R2_T503.fastq.gz.corrected.fastq.err_barcode_removed.fastq.gz.

These files have been generated but they are of size 0 bytes; additionally, another file titled, "Result_I1_T500.fastq.gz.erroneous.fastq", of size 23 GB, has been created. I am supposed to use the former three files for further downstream processes. Can someone provide insights into this problem? I here with attach the "Tell-read" commands provided.

  1. sudo docker load -i docker-tellread

  2. sudo chmod g+s /path/to/directory/

  3. sudo setfacl -d -m g::rwx /path/to/directory/

  4. sudo setfacl -d -m o::rwx /path/to/directory/

  5. sudo tellread_rerun_tellread_fq.sh \ -i1 SVA-1_S1_I1_001.fastq.gz \ -r1 SVA-1_S1_R1_001.fastq.gz \ -r2 SVA-1_S1_R3_001.fastq.gz \ -o /path/to/output_folder \ -g NONE

NGS Tell-seq next sequencing generation • 478 views
ADD COMMENT

Login before adding your answer.

Traffic: 2219 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6