-
Notifications
You must be signed in to change notification settings - Fork 18
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
Unable to install mikado with mamba via multiple strategies #445
Comments
Hi, This is the same with me. I have been trguggling for a month. I tried conda and pip on different machines and servers, and it didn't work. The package installed via conda create emply configuration file. And when I use the mashmallow version as suggested, it crashes. thanks, |
For me it worked I made it all the same way as you. Hope it will help |
Thank you for the suggestion, though unfortunately it still does not work for me. With the most promising, simple strategy (#2), there just seems to be a problem with the path that Mikado thinks it should find the example configuration files at. When I try to install mikado on the Windows subsytem for linux, the stated path does seem to exist and there are non-empty configuration files at the path, but perhaps there is a problem with how it deals with the mounted file system. On the shared linux system that I have tried to install it on (a university HPC cluster), the stated path to the configuration files does not actually exist, leading to the error message regarding "empty" configuration files. This seems similar to #431, though in that case the proposed solution was more dependency pinning, the likes of which I have already tried. |
Hey! Just asking if there has been an update here? If I install mikado through conda I am having the same issues still, is there a new conda installation recipe? Best, |
Hello,
I have tried several strategies to install version 2.3.4 of mikado via mamba, all of which have led to problems in the installation preventing me from running
mikado --help
without throwing an error. The errors discussed below were generated on a Windows machine running the subsystem for Linux with mamba version 1.4.1 and conda version 23.1.0. I have reproduced the same errors on a shared cluster running Red Hat Enterprise Linux version 8.6, mamba version 1.4.2, and conda version 23.3.1.Strategy 1: Simplest mamba strategy
Code:
mamba create -c bioconda --name mikado mikado
Installation proceeds without error
Error message when running
mikado --help
:Issue #438 had mentioned needing to pin the sqlalchemy version, so I tested that next.
Strategy 2: Strategy 1 + pinned sqlalchemy version
Code:
mamba create -c bioconda -c anaconda --name mikado mikado sqlalchemy=1.4.46
Installation proceeds without error
Error message when running
mikado --help
:This error is concerning as it seems to imply something wrong with the provided
plant.yaml
scoring file, which I wouldn't know how to fix. Despite this, I moved on to try some radically different strategies inspired by a number of previously raised Issues and Pull Requests.Strategy 3: Full environment specification from #443
Code:
mamba env create -f environment.yaml
I used the following environment.yaml file, which is from #443, though I added mikado to the list of dependencies as the documentation edits included in that pull request suggested that it should have been included:
I'll note that this strategy only works with a flexible channel priority. The installation proceeds without error though.
Error message when running
mikado --help
:A new sqlalchemy error! Fun. As this yaml file was part of a yet to be accepted pull request though, I realized that some of the changes made to the existing environment.yaml file might be dependent on other changes in the pull request, so next I tried to use the existing environment.yaml file on main branch of the repo.
Strategy 4: Existing environment.yaml file
Code:
mamba env create -f environment.yaml
I used the following environment.yaml file from the main branch of the Github repo, though I added mikado to the list of dependencies:
The installation proceeds without error.
I got the same error message when running
mikado --help
as with Strategy 3Since this was a sqlalchemy problem again, I tried Strategy 3 plus the exact version pinning from Strategy 2
Strategy 5: Strategy 3 + Strategy2
Code:
mamba env create -f environment.yaml
Here is the yaml file I used, same as Strategy 3 but with pinned sqlalchemy version
When running
mikado --help
, got the same error as in Strategy 3 and 4.Strategy 6: mamba + pip
Decided to use mamba to try and install mikado via the pip route discussed in the mikado README
Code:
Installation failed with following error:
Which seems like the problem discussed in issue #444. which hasn't been officially addressed with a pull request yet.
The same error arises when installing with
pip3 install mikado
if run within the environments specified in Strategies 3 and 4.Strategy 7: #443 + #265
After combing through some more issues, I wanted to try installing via the instructions given in a much older issue (#265), combined with the fixes implemented in a recent (though not yet merged) pull request (#443) from which I derived the environment specification used in several strategies discussed above.
Code:
Installation succeeded but running
mikado --help
yielded the sameplant.yaml
error as in Strategy 2.I am happy to provide any additional information or test additional strategies, and am grateful for any help that can be provided.
Best,
Isaac
The text was updated successfully, but these errors were encountered: