-
Notifications
You must be signed in to change notification settings - Fork 71
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
Trouble executing DragoNN #26
Comments
@hussius: Thanks for reporting this issue. I updated the Can you pull from master, install with The missing |
@jisraeli Thanks for the reply. I now have a running version of |
I'll create a new issue if this is unrelated, but I also had problems installing with linux-64 made it seem like there is not support for Python 3.5:
win-64 may have had problems installing
I've been able to install I'm working on installing from source and will add an update if anything interesting comes from that. I'll also try a Python 2.7 environment with the conda install, which seemed to work for @hussius. |
@agitter thank you for highlighting these issues. I think a python 3.5 build test in travis CI would be useful for catching these errors. I may be able to work through these issues next week, I would be happy to review a PR with travis test with python 3.5 so please feel free to contribute. On a separate note, we are in the process of forming a DragoNN organization which will offer this repo for workshops/tutorials and a more advanced repo that would be more appropriate for research. The more advanced repo will be designed based on patterns that have worked well for our lab, greater flexibility, and smaller set of dependencies. I look forward to making it public soon. |
@jisraeli I made a branch on my fork that runs a Travis CI test in Python 2.7 and 3.5 in parallel by creating different conda environments: https://github.com/agitter/dragonn/tree/travis The install worked in 2.7.13 and 3.5.3. However, the dragonn unit tests failed in 3.5.3: https://travis-ci.org/agitter/dragonn/jobs/211924331 I don't think I'll have time to dig in and see why the tests failed. Should I make a pull request to merge this into a new Travis CI branch so that you can check out the Python 3.5 tests when you have time? The DragoNN organization sounds great. I'm currently interested in the simpler version actually. I'd like to use this in my bioinformatics class, which is why I want to see how hard it will be for students to install. |
@agitter I looked briefly over the unit test failures, it looks like something I could fix sometime next week. Let's go ahead and open a PR with this. Thanks! |
For anyone else who had trouble installing and found this issue, I was able to install from source in Python 2.7 on my linux-64 server. I followed the install steps used in |
We also see the pydot-ng issue. For us the full working procedure to install is... conda create -n dragonn python
source activate dragonn
conda install -c kundajelab dragonn
conda remove pydot-ng
pip install pydot-ng==1.0.0
git clone [email protected]:kundajelab/dragonn.git
cd dragonn
python setup.py install
# Then it runs
dragonn train --pos-sequences examples/example_pos_sequences.fa --neg-sequences examples/example_neg_sequences.fa --prefix training_example |
@dctrud: Thanks for posting your fix. Which operating system did you use? I'm on vacation this week, will look through the pydot dependency in the conda package next week. |
@jisraeli - sorry for the delay. We are on Red Hat Enterprise Linux 6.8 in this case. |
Thanks for making this package available! However, I am having some trouble running it on an academic computing cluster where I have an account.
First, I tried to install it through
python setup.py install
. That appeared to work, but then I ran into the error below when trying to execute:On the other hand, using the Anaconda installer by
conda install dragonn -c kundajelab
, I run into this when executing:I used a Python 2.7 virtual environment because it seems DragoNN has extra functionalities with 2.7 as opposed to 3.x.
The text was updated successfully, but these errors were encountered: