Troubleshooting MiModD

Hi everyone,

I’m trying to use MimodD variant calling for the first time with default settings in galaxy.eu and I’m getting the following error: /data/jwd02f/main/062/368/62368537/tool_script.sh: line 27: mimodd: command not found

galaxy tool id: toolshed.g2.bx.psu.edu/repos/wolma/mimodd_main/mimodd_varcall/0.1.8_1

Reads are aligned with BWA-MEM2, and other downstream calling variants tools like bcftools mpileup are able to call the variants.

I read that there were some problems earlier this summer with MimodD but that they got resolved, I was wondering whether others are having problems again or whether something I’m doing wrong is causing this error?

I was first using galaxy.org and got a similar error, therefore I tried at galaxy.eu.

Many thanks for the help!

Marie

Hi @marie62743

Are you getting the same error at both servers? Could you share more details about those errors? The server and tool version will matter for each.

A shared history link would be great, or you can post back the contents of the job details page (“i” icon). See Troubleshooting errors. At the same time, you can submit a bug report at the ORG server – please include a link to this topic in the report comment section, so we can link the two and make sure to be reviewing the same problem. If you already did that, please submit again with the update comments.

Let’s start there. Agree that this could be a configuration problem but let’s double check not usage first. :slight_smile:

Hi @jennaj

Thank you very much for the follow-up! Errors are not exactly the same, but also tool version is different, so maybe this makes it hard to compare (see details below). An extra difference between the two is that I used the build-in Arabidopsis TAIR10 reference genome for mapping in case of usegalaxy.eu, which was not an option on usegalaxy.org, so over there I used a TAIR10 reference genome from history. In the meantime I’ve also tried to perform the mapping with MiModD Read Alignment. This is now running on usegalaxy.org to check if I get a similar error when mapping is performed with MiModD itself, however on usegalaxy.eu I’m already getting an error at step 1 when trying to make the annotation file required for the read alignment (added info below as well).

UPDATE: got it working on usegalaxy.org, both with the BWA-MEM mapped reads and Mimodd mapped reads. I had to edit the attributes (set database/build = Arabidopsis TAIR) for the BWA-MEM data and then it worked fine.

Details from use.galaxy.eu:

Job Information

Galaxy Tool ID toolshed.g2.bx.psu.edu/repos/wolma/mimodd_main/mimodd_varcall/0.1.8_1
Job State error
Command Line mimodd varcall ‘/data/db/data_managers/TAIR10/seq/TAIR10.fa’ ‘/data/dnb09/galaxy_db/files/0/2/3/dataset_0238d27e-178e-4985-880f-7c37b641ea9f.dat’ --index-files ‘/data/dnb09/galaxy_db/files/_metadata_files/d/2/9/metadata_d293ba47-3f32-4330-b041-9971561dcc80.dat’ --ofile ‘/data/jwd02f/main/062/368/62368537/outputs/dataset_1e4ac260-730e-402c-97b8-9a2f799faeb5.dat’ --max-depth 250 --verbose --quiet
Tool Standard Output empty
Tool Standard Error /data/jwd02f/main/062/368/62368537/tool_script.sh: line 27: mimodd: command not found
Tool Exit Code 127
Job Messages * { “code_desc”: “”, “desc”: “Fatal error: Exit code 127 ()”, “error_level”: 3, “exit_code”: 127, “type”: “exit_code” }
Job API ID 11ac94870d0bb33a70713db2dc109913

Details from usegalaxy.org:

Job Information

Galaxy Tool ID toolshed.g2.bx.psu.edu/repos/wolma/mimodd_main/mimodd_varcall/0.1.9
Job State error
Command Line empty
Tool Standard Output empty
Tool Standard Error /jetstream2/scratch/main/jobs/52414003/tool_script.sh: line 10: mimodd: command not found
Tool Exit Code 127
Job Messages * { “code_desc”: “”, “desc”: “Fatal error: Exit code 127 ()”, “error_level”: 3, “exit_code”: 127, “type”: “exit_code” }
Job API ID bbd44e69cb8906b583fde36f284d65d5

Details from usegalaxy.eu (MiModD Run Annotation):

Job Information

Galaxy Tool ID toolshed.g2.bx.psu.edu/repos/wolma/mimodd_main/mimodd_header/0.1.8_1
Job State error
Command Line mimodd header --rg-id ‘test_testing’ --rg-sm ‘test’ --ofile ‘/data/jwd02f/main/062/458/62458363/outputs/dataset_fa494809-cd21-4d10-9026-8f1401de0285.dat’
Tool Standard Output empty
Tool Standard Error /data/jwd02f/main/062/458/62458363/tool_script.sh: line 27: mimodd: command not found
Tool Exit Code 127
Job Messages * { “code_desc”: “”, “desc”: “Fatal error: Exit code 127 ()”, “error_level”: 3, “exit_code”: 127, “type”: “exit_code” }
Job API ID 11ac94870d0bb33a63eedf632ca28e6f

Let me know if you need any additional info!

Best,
Marie

1 Like

Hi @marie62743

The tool suite likely needs some changes at EU, and the version does seem relevant. I’ve made the request here if you’d like to follow the issue ticket: Update MiModD suite at EU · Issue #625 · galaxyproject/usegalaxy-tools · GitHub

Thanks for all the testing, and glad you were able to get this working at ORG by adjusting some of the metadata!