Conversation
|
Very slight nitpick: what do you think of |
|
Ah yea, I like |
|
Issue #128? |
|
Yes, updated, I meant #128 |
| row['is_indel'] = effect.variant.is_indel | ||
| row['is_transversion'] = effect.variant.is_transversion | ||
| row['is_transition'] = effect.variant.is_transition | ||
| row['is_transversion'] = effect.variant.is_transversion |
|
@iskandr seem to be running into the problem you have on pyensembl, where the py 2.7 tests on Travis on failing with |
|
@arahuja Should be fixed now but have to wait for Travis to run. The problem was that I was decoding byte strings into ASCII, which does the sane thing under Python 3 but under Python 2 causes us to leave the byte-per-character |
|
@iskandr Looks to be passing now |
|
@iskandr Good to merge? |
|
@arahuja Definitely |
| def row_from_effect(effect): | ||
| row = {} | ||
| row['chr'] = effect.variant.contig | ||
| row['position'] = effect.variant.start |
There was a problem hiding this comment.
might make sense to be clear here about the coordinate system, e.g. call it inclusive_start. Just a suggestion, feel free to ignore
There was a problem hiding this comment.
Similarly, I'll make it match the varcode field names
|
these are the column names i've been using. Not necessary to match them but just fwiw https://github.com/hammerlab/varlens/blob/master/varlens/variants_util.py#L26 |
This adds an
as_dataframeto EffectCollection - happy to add or rename any columns.Also, a few helper properties to
Variantthat I have been using:is_snvis_transitionis_transversionThis change is