Tavi Nathanson
Tavi Nathanson
@jburos yup, should be fixed with the latest `varcode`.
@jburos that `.pyc` code looks old; can you delete all the `.pyc`s and see if that helps? Are you using `0.4.0` there?
More generally, all columns in cohorts should be specifiable as functions. We can probably centralize that concept and get rid of some code.
Indeed, @jburos ran into this very issue: https://github.com/hammerlab/cohorts/issues/120#issue-171240320
I like the idea of a `StratifiedCohort` class.
This seems related to https://github.com/hammerlab/cohorts/pull/112/commits/067efef7e9816cdc384a10853186ee425f7954ba
Or, at least, consider this modification
@arahuja I think my logic was: I was running into issues where I had a few missing VCFs and wanted to load the others, but the `IOError` blew up the...
We discussed offline that it's okay for incorrect paths to blow up the whole thing, and any logic to the contrary can live outside of `cohorts` since it's counter-intuitive.
Also related: tracking provenance. `cohorts` tracks `Python` package versions in `PROVENANCE` files inside the `cache` directory. I'm not sure how to pull out the software versions that `epidisco` used?