Hey,
this might be a dump question, but I have snakemake workflow that I did run multiple times succesfully on and centOS cluster. I always used the sythax: bwa mem resources/genome.fasta path/to/read_1.fastq.gz path/to/read_2.fastq.gz -K 100000000 -Y.
I wanted to do a quick test using my Mac and it turns out that here I need to change the command to bwa mem -K 100000000 -Y resources/genome.fasta path/to/read_1.fastq.gz path/to/read_2.fastq.gz otherwise it won't work.
I know the official usage is bwa mem [options] <idxbase> <in1.fq> [in2.fq], so like in the latter example. I use a fixed version for bwa (0.7.17) installed via conda. So, I am just wondering how is it possible that it runs with the options in the last position on bash (Linux), but not on zsh (macOS).
Just looking for an explanation not a fix :).
0 answers
No answers yet.
Log in to answer this question.
-
Using BBtools to remove polyGs in Illumina data
written by hpapoli
-
BWA alignment failing after adding nextflow.config file?
written by Eliveri •
-
How do I find the percentage of paired-end fastq files containing a given string
written by lkianmehr
-
run-bwamem from BWAKIT does not work
written by laura.zalba •
-
error with BWA
written by storm1907 •
-
How to properly assemble the virus genome using map to reference strategy
written by xatabadich •
-
Addition of Y chromosome to the ref sequence
written by micro32uvas •
-
bwa mem problem with Illumina sequence
written by sevillaro1970 •
-
ABySS error at rescaffolding with long sequences
written by wstfljs
-
Using Bwa Sampe Using Illumna Pair End Reads
written by Juliofdiaz
I cannot tell you the definite answer but the official syntax is indeed
bwa mem [options] <idxbase> <in1.fq> [in2.fq]so just always use that and call it a day.How boring life would be, if we never asked why :).
No, actually there is a ton of important things to work out during a project. Position of arguments is none of it. Just do what everyone does and focus on the important stuff. I am not saying to mock you, it is really a lesson you need to learn early in your career. Nobody will give you credit for solving stuff like this.
There is nothing to solve here. Just wanna know why the arguments seem to be parsed differently in centOS vs. macOS. And it's not early in my career anymore and up to now it always turned out beneficial to ask such simple questions, because there's always something to learn behind those ;).
Are you using the same version of
bwaon both the linux and mac machines?Yes, they are defined by the yaml file
Can you be specific as to what does not work? Do you just get an error? I doubt that Heng Li made a mac specific version of
bwacode so the options should work identically. Unlesscondapeople built the binary is some specific way that is causing this to happen on Mac.Here are some more details:
centOS cluster:
bwa=0.7.17installed via conda.conda env export gives
bwa=0.7.17=he4a0461_11.Command:
bwa mem resources/genome.fasta path/to/read_1.fastq.gz path/to/read_2.fastq.gz -K 100000000 -Yresult: simply starts putting out bwa mem output to stdout (expected)
MacBook pro (Apple Silicon; macOS 14.3.1).
bwa=0.7.17installed via conda.conda env export gives
bwa=0.7.17=h45fc8d7_11(slightly different built).Command:
bwa mem resources/genome.fasta path/to/read_1.fastq.gz path/to/read_2.fastq.gz -K 100000000 -Y.result: giving usage error:
It's also weird that I wrote this workflow using my Macbook, so it must have worked earlier. Seem like there has been some change in
zshfrom one of the macOS updates.My (total) guess is that
zshis trying to be clever in some way with how it handles positional arguments which is maybe conflicting in weird ways. It does a lot of extra stuff behind the scenes that bash generally doesnt.That's my guess too. But it must be something that was changed just recently.
Out of curiosity, if you switch to
bashon MacOS does the program work? If it does then we can blame this quirk onzsh.It still does happen (meaning it still doesn't work). However, I am not sure if this was a "real" bash. I just ran
bash(and it looked like a bash), butecho $SHELLstill gives/bin/zsh(echo $0givesbashthough, I am not so familiar with switching shells). Also had to make conda available in the bash. conda might still be configured for zsh.