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

Kmerstream sometimes fails when estimating the kmers to use #10

Closed
michaelbarton opened this issue Oct 7, 2016 · 4 comments
Closed

Comments

@michaelbarton
Copy link

Here is the error message I recieve:

Running: seqtk sample R1.fq.gz 10000 | paste - - - - | cut -f2 > readsample.txt
Read length looks like 150 bp
Estimated K-mers: 21 37 53 69 85 101 117 [kn=8, ks=16, kmin=21, kmax=127]
Using kmers: 21,37,53,69,85,101,117
Estimating genome size
Running: KmerStream -k 21,37,53,69,85,101,117 -o kmerstream-raw.tsv -t 8 --tsv --verbose --online R1.fq.gz R2.fq.gz
Running: KmerStreamEstimate.py kmerstream-raw.tsv > kmerstream-est.tsv
Traceback (most recent call last):
  File "/usr/local/bin/KmerStreamEstimate.py", line 43, in <module>
    x,e = EMfit2(F0,f1,F1,int(k))
  File "/usr/local/bin/KmerStreamEstimate.py", line 26, in EMfit2
    e = brentq(func, 0, 1)
  File "/usr/lib/python2.7/dist-packages/scipy/optimize/zeros.py", line 415, in brentq
    r = _zeros._brentq(f,a,b,xtol,rtol,maxiter,args,full_output,disp)
ValueError: f(a) and f(b) must have different signs
Error 256 running command

I am using the version from commit 84e56564a

@tseemann
Copy link
Owner

There are upstream bugs in Kmerstream:

I am waiting for @pmelsted to respond.

However I realise now his python code depends on scipy which is not something I want to depend on.

@tseemann tseemann added this to the Release 1.0 milestone Oct 12, 2016
@michaelbarton
Copy link
Author

Thanks for looking into this Torsten. A couple of options which don't use
scipy are kmergenie and bbtools. Perhaps @accopeland or @aclum can offer
some suggestions too.

On Wednesday, 12 October 2016, Torsten Seemann [email protected]
wrote:

There are upstream bugs in Kmerstream:

I am waiting for @pmelsted https://github.com/pmelsted to respond.

However I realise now his python code depends on scipy which is not
something I want to depend on.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#10 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAEdkXmNZumUwPUpHoHZqr4UPuLDh1vks5qzJOngaJpZM4KRh5i
.

@tseemann
Copy link
Owner

I've ditched KmerStream due to lack of response.

@michaelbarton
Copy link
Author

Thanks @tseemann

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

No branches or pull requests

2 participants