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

Error in NUMEXPR dependency #18

Closed
mscharmann opened this issue Feb 1, 2021 · 3 comments
Closed

Error in NUMEXPR dependency #18

mscharmann opened this issue Feb 1, 2021 · 3 comments

Comments

@mscharmann
Copy link

mscharmann commented Feb 1, 2021

Hello,
many thanks for going through a lot of work to spare a lot of people the trouble to force conventional tools into making meaningful statistics in the presence of missing data - I certainly have burned a lot of time doing that with cumbersome approaches, like fake VCFs that only contain read deth information, or bedtools etc to cheat PopGenome into not assuming reference alleles for regions without read coverage etc etc....

Unfortunately, I get this error (have pixy through conda) whatever I do, even with only "pixy --help", get:

Error. nthreads cannot be larger than environment variable "NUMEXPR_MAX_THREADS" (64)

See also: cggh/scikit-allel#285

Cheers, Mathias

@mscharmann
Copy link
Author

OK so it helps to just paste this into the pixy executable script in the conda path:

import os
os.environ["NUMEXPR_MAX_THREADS"]="272"

@kkorunes
Copy link
Collaborator

kkorunes commented Feb 2, 2021

Hi Mathias-- thanks for using pixy and posting here! It sounds like you have this working now? If not, would you mind posting your full pixy command, your OS, and the version of python you're running (since this error appears to be associated with pandas)?
I'll also note that the next version of pixy should be released very soon, and it includes a few key performance improvements, which might alleviate the error you're encountering.

@mscharmann
Copy link
Author

Hello,
yes many thanks, the issue is resolved for my case - but perhaps you can fix this in an upcoming version.

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

2 participants