Closed mbdabrowska1 closed 1 year ago
Hi,
By default, we have set the assembled HIV size to around 5k, which exceeds your current bed setting of 3k.
flye --nano-raw /mnt/parscratch/users/md1mbdx/HIV_mehmet_13072023/clusterv_test/results/consensus/barcode87_1/barcode87_1_ori_r.fasta --threads 8 --out-dir /mnt/parscratch/users/md1mbdx/HIV_mehmet_13072023/clusterv_test/results/consensus/barcode87_1/barcode87_1_flye -m 1000 -g 5k >/dev/null 2>&1
To analyze data with a smaller amplicon size, can you please try to run the following to test whether Flye can run without error?
flye --nano-raw /mnt/parscratch/users/md1mbdx/HIV_mehmet_13072023/clusterv_test/results/consensus/barcode87_1/barcode87_1_ori_r.fasta --threads 8 --out-dir /mnt/parscratch/users/md1mbdx/HIV_mehmet_13072023/clusterv_test/results/consensus/barcode87_1/barcode87_1_flye -m 500 -g 2.5k >/dev/null 2>&1
If this command executes without any issues, you can rerun your analysis by incorporating the following option into your pipeline:
python cv.py ClusterV ... \
--flye_genome_size 2.5k --flye_genome_size_olp 500
If not, could you please share your bam with me? I will check the problem in my local environment.
JH
Hi, I ran it as suggested but still the same issue. What email address would you like me to send the bam file to?
Update to v1.2 and solve the problem.
Hi, I'm running your tool for my amplicon ONT HIV data, but the pipeline fails at the Flye step:
When I ran the Flye on its own to check what the log and the reason for failing I got the following error:
Attaching the full flye log: flye.log
Any help would be greatly appreciated!