Conversation
|
Many thanks for doing this in a way that does not break all of our existing code (which passes in |
|
@timodonnell Fewer tests for me to fix, too! The intent of openvax/pyensembl#99 is also to keep the |
|
Finding lots of little bugs in the PyEnsembl PR we merged, but also finding a design flaw wherein each GenomeSource only tells you the command you need to download e.g. a protein FASTA but that command can't be run in isolation (since the pyensembl script always requires a GTF). I guess we'll figure out a better design when you come back. |
|
To clarify on the last comment, to install the mouse genome you need to run: but if this genome is missing you'll see errors like: |
|
Additionally, it looks like EnsemblReleaseSource no longer gets used and thus even human Ensembl references emit an error like the one above. |
|
Offline discussion re the design flaw: it still "works", but might be an annoyance to run multiple commands. We agreed to table that until openvax/pyensembl#100 is addressed. |
|
Re the bugs: @iskandr and I worked through them together and they're summarized/addressed here: openvax/pyensembl#108 Offline discussion re |
|
@iskandr I don't remember how we left it with this PR, since it's hacky but not entirely awful. What would you like to see before we merge? |
|
@tavinathanson Let's merge this, and get mouse epitope predictions out of Topiary, and figure out a better organization next week. |
Allow Varcode to work with mouse data via Genome
This is a quick fix to allow Varcode to work with mouse data (and an initial test for that) by accepting
Genomeobjects.It's certainly confusing to be using
ensemblandgenomesomewhat interchangeably here. I'd like a follow-up PR (and will create an issue, if this order-of-things sounds good to you) to liberate Varcode from Ensembl much like openvax/pyensembl#99, but for now this seems useful.