-
Notifications
You must be signed in to change notification settings - Fork 167
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 running test #661
Comments
Hi @ytakemon , Not an author of CNVkit, but if I understand correctly you installed CNVkit from sources ? Installing each Python package through
Also using conda is the recommended and much easier way to install CNVKit (and a lot of other tools by the way) Hope this helps. |
Thanks for the tip, Felix! I was semi-resolved this initial issue by opening the Makefile and editing the 5th file to This partially ran the Makefile, but now similar to the first issue I need to specify which executable Perhaps a note to the authors of CNVkit is to allow the paths to python/R to be set initially to avoid this problem as not everyone will be running this in a local environment with only a single version of python or R is installed. |
Good to know it is working for you! Here you were in a specific case of running CNVkit's tests, meaning a serie of commands on internal test data through a written Makefile A not-costly way to do what you say would be to set a variable inside Makefile, similar to 5th line Have a nice day. |
Should be closed by #699. Kind regards, |
I'm rather new to python, so apologies for the naive question. I installed all the dependencies as in your tutorial but for some reason, I can't get the test to run correctly. It seems to be that pandas was not installed, but after checking pandas seemed to have been installed correctly.
Also, I am using an alias for python
py-3.9
(due to how my institution had structured our environment), which I see wasn't used properly below in the error message. Is there a way to specify which Python version to use in this make execution?The text was updated successfully, but these errors were encountered: