Question: stringtie Error: input file cannot be found
0
gravatar for mjavad2012
22 months ago by
mjavad20120
mjavad20120 wrote:

Hello,

I want to use StringTie to assemble transcripts for each sample, but when I run the stringtie, I have an error:

Error: input file –l cannot be found!

here is my command:

stringtie -p 8 -G /annotation/Ghirsutum_458_v1.1.gene.gff3.gz -o NMHT-80-23.gtf –l NMHT-80-23 NMHT-80-23.bam

Please kindly let me know what should I do?

ADD COMMENTlink modified 5 months ago by spriyar10 • written 22 months ago by mjavad20120

Have you tried giving a different name for your output transcripts for the -l option?

ADD REPLYlink written 22 months ago by genomax64k

yes, I did but i still have that error. what format supposed to be the output file after -l ?

ADD REPLYlink written 22 months ago by mjavad20120

For POC, try eliminating the -l, and let it use the default STRG. You can do a sed later, sed -i 's/STRG/NMHT-80-23/g' NMHT-80-23.gtf if it works.

The user manual also as the bam file in front of the options:

stringtie <aligned_reads.bam> [options]*
ADD REPLYlink modified 22 months ago • written 22 months ago by st.ph.n2.4k
3
gravatar for Ellango R
21 months ago by
Ellango R30
India
Ellango R30 wrote:

This error may be due to strings error in the script options. I do suffer the same problem while i copied the script directly from article and paste it into terminal. (*Name of output perfix –l =error (which i copied from article); -l = working)

ADD COMMENTlink written 21 months ago by Ellango R30

That's exactly what happened to me. Thanks :D

ADD REPLYlink written 14 months ago by marianocollantes0

That's right. As Pertea pointed, in the paper code we can found '–' instead of '-'; the first one is a character not recognized by stringtie. The problem is fixed just using the small '-'.

ADD REPLYlink written 6 months ago by jpuntomarcos20
0
gravatar for spriyar
5 months ago by
spriyar10
Ohio
spriyar10 wrote:

Have you tried using the full path for the reference files. I had the same problem and adding the path to the genome reference solved it! Good luck!

ADD COMMENTlink written 5 months ago by spriyar10
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1249 users visited in the last hour