Thanks for posting back the logs. The message “mimodd: command not found” could be a cluster configuration issue OR some input issue the tool doesn’t understand how to handle.
Examples: an empty or header-only BAM could be a trigger. A mismatched reference genome or poor alignment rates would probably produce something more informative. If that BAM was from Upload and not a job run in Galaxy, or from using a custom reference genome+build, more could be going on data-wise leading to the error.
Thanks for your kind reply. My history link is (Galaxy). And I submited a bug report just now. Actually I tried re-running the MiModD Variant Calling (by ‘Run Job Again’) in a previous successful analysis history but got the same error (command not found).
Wolfgang said this maybe an issue with MiModD installation in usegalaxy.org.