Bowtie error: Could not locate a Bowtie index corresponding to basename
1
0
Entering edit mode
5.7 years ago
cilgaiscan ▴ 60

Hi everyone! I am an undergrad and pretty new in ChIP-seq. And I need to use bowtie with hg19. I indexed hg19 with bowtie-build and completed it. I would like to run my single-end fastq files with bowtie. I am using this to run bowtie.

bowtie --large-index </home/cilga/Desktop/VPC/ref/bowtie_indexes/bt1/hg19> -q /home/cilga/Desktop/VPC/chipseq/samples/dht_treatment/SRR3728821_pass.fastq  -S SRR3728821.sam

I am not sure whether I do wrong. And I got this error:

Could not locate a Bowtie index corresponding to basename "/home/cilga/Desktop/VPC/chipseq/samples/dht_treatment/SRR3728821_pass.fastq" Command: bowtie --wrapper basic-0 -S /home/cilga/Desktop/VPC/chipseq/samples/dht_treatment/SRR3728821_pass.fastq SRR3728821.sam

Is there anyone can help me? Thank you for your helps.

PS.. can someone write an example command for bowtie?

bowtie ChIP-Seq single-end hg19 alignment • 7.8k views
ADD COMMENT
0
Entering edit mode

I believe the error message does not match with the command you pasted above. Can you check again that it is effectively the command you used?

ADD REPLY
0
Entering edit mode

yes i double checked. i use same command and got same error..

ADD REPLY
0
Entering edit mode

The error says:

Command: bowtie --wrapper basic-0 -S /home/cilga/Desktop/VPC/chipseq/samples/dht_treatment/SRR3728821_pass.fastq SRR3728821.sam

Are you sure you didn't swap some arguments there?

ADD REPLY
0
Entering edit mode

i am.i used the arguments i shared in my question :(

ADD REPLY
0
Entering edit mode

cilgaiscan : You are not actually including <> around the large index file location in your command, correct?

ADD REPLY
0
Entering edit mode
5.7 years ago
h.mon 35k

Try the following:

bowtie -S -q --large-index /home/cilga/Desktop/VPC/ref/bowtie_indexes/bt1/hg19 /home/cilga/Desktop/VPC/chipseq/samples/dht_treatment/SRR3728821_pass.fastq > SRR3728821.sam

The problem, I believe, is for bowtie -S is just a boolean flag, and you are using it as in bowtie2, where -S file.sam creates the output file, instead of using stdout.

ADD COMMENT

Login before adding your answer.

Traffic: 2768 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6