Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot specify a file on cmdline? #52

Open
wwood opened this issue Jan 7, 2021 · 0 comments
Open

Cannot specify a file on cmdline? #52

wwood opened this issue Jan 7, 2021 · 0 comments

Comments

@wwood
Copy link

wwood commented Jan 7, 2021

Hi Torsten,

Small thing - from the doco

Usage:
  barrnap [options] chr.fa

But

barrnap-0.9) $ barrnap a.fna
[barrnap] This is barrnap 0.9
[barrnap] Written by Torsten Seemann
[barrnap] Obtained from https://github.com/tseemann/barrnap
[barrnap] Detected operating system: linux
[barrnap] Adding /home/ben/e/barrnap-0.9/lib/barrnap/bin/../binaries/linux to end of PATH
[barrnap] Checking for dependencies:
[barrnap] Found nhmmer - /home/ben/e/barrnap-0.9/bin/nhmmer
[barrnap] Found bedtools - /home/ben/e/barrnap-0.9/bin/bedtools
[barrnap] Will use 1 threads
[barrnap] Setting evalue cutoff to 1e-06
[barrnap] Will tag genes < 0.8 of expected length.
[barrnap] Will reject genes < 0.25 of expected length.
[barrnap] Using database: /home/ben/e/barrnap-0.9/lib/barrnap/bin/../db/bac.hmm
[barrnap] ERROR: No input file on command line or stdin

Easy to workaround - just specify via stdin e.g. barrnap < a.fna, but figured I'd report.
ben

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant