-
Notifications
You must be signed in to change notification settings - Fork 80
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
Compare: move get_similarities_at_index
into compare_parallel
function to help with memory
#1509
Compare: move get_similarities_at_index
into compare_parallel
function to help with memory
#1509
Conversation
Codecov Report
@@ Coverage Diff @@
## latest #1509 +/- ##
==========================================
+ Coverage 82.61% 90.09% +7.47%
==========================================
Files 113 86 -27
Lines 11995 8195 -3800
Branches 1513 1513
==========================================
- Hits 9910 7383 -2527
+ Misses 1830 557 -1273
Partials 255 255
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
For some reason the version appears as
|
yes, this sounds like something I had to fix when doing releases - you need
to install a package.
I think it's setuptools_scm_git_archive, installable with pip. I'll go find
the issue and link to it later when I get a chance!
On Sat, May 08, 2021 at 10:32:20AM -0700, Olga Botvinnik wrote:
For some reason the version appears as `0.0.0` -- any ideas why?
```
(nf-core--kmermaid-1.1.0dev)
Sat 8 May - 10:31 ??? ~/code/sourmash ??? ??? origin ??? olgabot/pranthi-fxn-in-fxn ??? ???
***@***.*** ??? sourmash info
== This is sourmash version 0.0.0. ==
== Please cite Brown and Irber (2016), doi:10.21105/joss.00027. ==
sourmash version 0.0.0
- loaded from path: /data_sm/home/olga_ibm/miniconda3/envs/nf-core--kmermaid-1.1.0dev/lib/python3.7/site-packages/sourmash-0.0.0-py3.7-linux-ppc64le.egg/sourmash/cli
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#1509 (comment)
--
C. Titus Brown, ***@***.***
|
@pranathivemuri Hmm there's still issues with pickling - do you know what would be the best way around this?
|
the version stuff can be fixed with |
This version is working for me! |
When running
compare
on large (~30,000 signature) datasets, even on beefy machines, the memory can lock up (ref: #1486). @pranathivemuri added this fix, which moves the functionget_similarities_at_index
into the inside ofcompare_parallel
, which reduces the amount of serialization passed between threads. I'm not 100% sure on how this works, @pranathivemuri is the expert here!