christopher-vollmers / C3POa

Computational pipeline for calling consensi on R2C2 nanopore data
GNU General Public License v2.0
7 stars 6 forks source link

Couldn't open splint.fa , No such file or directory #6

Closed ericmalekos closed 8 months ago

ericmalekos commented 9 months ago

Im encountering an error related to the --splint_file input. The output indicates it's treating the first splint header as a path to open?

$ C3POa --reads qc_fastqs/qc_test.fastq --splint_file ./splints.fa --out_path qc_fastqs/ --numThreads 8
C3POa v3 - It's over Anakin. I have the consensus! 
Generating consensus sequences from R2C2 read data
Starting consensus calling iteration - if input is directory it will check for files that are new since last iteration
        Read input is a file
        1 file(s) provided
Couldn't open >UMI_Splint_1_F , No such file or directory

The splint file is:

$ cat splints.fa                                                                                                                                                              
>UMI_Splint_1_F
ACTCTGCGTTGATACCACTGCTTTGAGGCTGATGAGTTCCATANNNNNTATATNNNNNATCACTACTTAGTTTTTTGATAGCTTCAAGCCAGAGTTGTCTTTTTCTCTTTGCTGGCAGTAAAAG
>UMI_Splint_1_R
ACTCTGCGTTGATACCACTGCTTAAAGGGATATTTTCGATCGCNNNNNATATANNNNNTTAGTGCATTTGATCCTTTTACTCCTCCTAAAGAACAACCTGACCCAGCAAAAGGTACACAATACTTTTACTGCCAGCAAAGAG

It seems like the file is being read in with mm.fastx_read correctly. If I add print(splint_dict) after line 177 of C3POa.py I see:

{'UMI_Splint_1_F': ['ACTCTGCGTTGATACCACTGCTTTGAGGCTGATGAGTTCCATANNNNNTATATNNNNNATCACTACTTAGTTTTTTGATAGCTTCAAGCCAGAGTTGTCTTTTTCTCTTTGCTGGCAGTAAAAG', 'CTTTTACTGCCAGCAAAGAGAAAAAGACAACTCTGGCTTGAAGCTATCAAAAAACTAAGTAGTGATNNNNNATATANNNNNTATGGAACTCATCAGCCTCAAAGCAGTGGTATCAACGCAGAGT'], 'UMI_Splint_1_R': ['ACTCTGCGTTGATACCACTGCTTAAAGGGATATTTTCGATCGCNNNNNATATANNNNNTTAGTGCATTTGATCCTTTTACTCCTCCTAAAGAACAACCTGACCCAGCAAAAGGTACACAATACTTTTACTGCCAGCAAAGAG', 'CTCTTTGCTGGCAGTAAAAGTATTGTGTACCTTTTGCTGGGTCAGGTTGTTCTTTAGGAGGAGTAAAAGGATCAAATGCACTAANNNNNTATATNNNNNGCGATCGAAAATATCCCTTTAAGCAGTGGTATCAACGCAGAGT']}

ericmalekos commented 8 months ago

This seems to have been an installation issue, after a clean install the issue is resolved!