Closed rainwala closed 1 year ago
I found something that could be related online: https://github.com/nanoporetech/dorado/issues/69
Update, I ran dorado v 0.2.4 successfully with my data with the --modified_bases flag on with on my setup. Telllingly, on the dorado versions page, this version was made specifically to "https://github.com/nanoporetech/dorado/commit/92ef398874e9f4d09c7a57e5d979d4e704a12a74 - Fix out of bound access when modbase calling"
I think to get around this issue on this wrokflow, it may be necessary to change the dorado version in the nextflow.config file
basecaller_container = "dorado:sha097d9c8abc39b8266e3ee58f531f5ef8944a02c3"
@rainwala Thanks for confirming the newer Dorado fixes your issue. We are working to update the basecalling component of wf-human-variation to have compatibility with the downstream models used by the workflow.
That sounds good. FYI the current wf-human-variation workflow works for me on my setup when using r9.4.1 basecalling models with Dorado.
What happened?
I was running wf-human-variation on Ubuntu 20.04, with 4 A100s, I think it's the Docekr profile. I ran the following command, and then it crashed:
sudo nextflow run epi2me-labs/wf-human-variation -w workspace -profile standard --snp --sv --methyl --fast5_dir /fast5 --basecaller_cfg 'dna_r10.4.1_e8.2_400bps_hac@v4.0.0' --remo ra_cfg 'dna_r10.4.1_e8.2_400bps_hac@v4.0.0_5mCG_5hmCG@v2' --ref /Homo_sapiens.GRCh38.106_no_alt_chrs.fa --out_dir patient31_drug/ --threads 16 --cuda_device="cuda:0,1,2,3"
Operating System
ubuntu 20.04
Workflow Execution
Command line
Workflow Execution - EPI2ME Labs Versions
No response
Workflow Execution - CLI Execution Profile
Docker
Workflow Version
1.4.0
Relevant log output