broadinstitute / oncotator

Other
67 stars 33 forks source link

Issue 343 fix ex ac ds #344

Closed LeeTL1220 closed 8 years ago

LeeTL1220 commented 8 years ago

This PR:

LeeTL1220 commented 8 years ago

Closes #346 Closes #345 Closes #343 Closes #288 Closes #338 Closes #232

LeeTL1220 commented 8 years ago

@lbergelson I filed an issue for broken travis. The unit tests all pass on both my laptop and on a Broad VM using create_oncotator_venv.sh. I also manually checked some mutations and the ExAc and new COSMIC annotations were there and correct.

LeeTL1220 commented 8 years ago

@lbergelson So when you have a chance... if you could review...

LeeTL1220 commented 8 years ago

Closes #348

coveralls commented 8 years ago

Coverage Status

Changes Unknown when pulling fcfeff951e45e72806ea3fbf1b9e8c5c6edad3d2 on issue-343-Fix_ExAC_ds into \ on develop**.

LeeTL1220 commented 8 years ago

@lbergelson HA! And it works on docker as well. Try it when you can... (Monday I hope)

coveralls commented 8 years ago

Coverage Status

Changes Unknown when pulling 34b3b80c4a46ba8e08c05282cb8c4a30e3061752 on issue-343-Fix_ExAC_ds into \ on develop**.

LeeTL1220 commented 8 years ago

Hopefully, Travis passes...

Using a small maflite file on the new candidate April default datasource corpus.

Deployment tests:

Additionally:

And travis seems to pass consistently as of this writing.

LeeTL1220 commented 8 years ago

@lbergelson Please do not merge until the checkboxes above are done. I discovered a nasty little error that did not manifest on travis, but did on my local machine.

LeeTL1220 commented 8 years ago

@lbergelson All set! Please review and tell me if I can merge. Whew... that was a slog.

LeeTL1220 commented 8 years ago

@lbergelson If you'd be willing to retry your test and see if you can create the venv, it'd be appreciated.

LeeTL1220 commented 8 years ago

@lbergelson Can you think of any downside to pegging the versions of software in the setup.py? If not, I still need to do that.

lbergelson commented 8 years ago

@LeeTL1220 I don't see any downside to specifying versions in setup.py other than that it means we need to specify versions in both the setup and the create_venv.

LeeTL1220 commented 8 years ago

@lbergelson create_oncotator_venv.sh looks like it just uses the latest version of dependencies. I'll have to update that. I'll peg versions to what was used in docker image.

LeeTL1220 commented 8 years ago

docker versions are same as my clean venv...

(oncotator_venv_clean)lichtens@OncobuntuMk3:~$ pip freeze
bcbio-gff==0.6.2
biopython==1.66
Cython==0.24
enum34==1.1.2
futures==3.0.5
more-itertools==2.2
natsort==4.0.4
ngslib==1.1.18
nose==1.3.7
numpy==1.11.0
Oncotator==1.9.0.1.dev0
pandas==0.18.0
parse==1.6.6
pysam==0.9.0
python-dateutil==2.5.2
python-memcached==1.57
pytz==2016.3
PyVCF==0.6.8
shove==0.6.6
six==1.10.0
SQLAlchemy==1.0.12
stuf==0.9.16
LeeTL1220 commented 8 years ago

@lbergelson Made updates to peg versions in setup.py and create_oncotator_venv.sh and make the version numbers the same. I was able to install successfully using both of these scripts on my local VM.

coveralls commented 8 years ago

Coverage Status

Changes Unknown when pulling c3a627cb7821ef51481df68b0b93db683dcce5c5 on issue-343-Fix_ExAC_ds into \ on develop**.

lbergelson commented 8 years ago

@LeeTL1220 Installation works on my machine now. (running python 2.7.11)

lbergelson commented 8 years ago

@LeeTL1220 Review complete!

LeeTL1220 commented 8 years ago

Everything addressed. Running unit tests with new default datasource corpus on my local VM, since we cannot do that on Travis. I'll post back here when complete (<10 minutes)

LeeTL1220 commented 8 years ago

All unit tests complete successfully on my laptop VM, which includes new default datasource corpus.

coveralls commented 8 years ago

Coverage Status

Changes Unknown when pulling a8fb014b2580368b5b25e80888da8abf625a4199 on issue-343-Fix_ExAC_ds into \ on develop**.

lbergelson commented 8 years ago

@LeeTL1220 :+1: