{"action":"opened","issue":{"url":"https://api.github.com/repos/pachterlab/kallisto/issues/190","repository_url":"https://api.github.com/repos/pachterlab/kallisto","labels_url":"https://api.github.com/repos/pachterlab/kallisto/issues/190/labels{/name}","comments_url":"https://api.github.com/repos/pachterlab/kallisto/issues/190/comments","events_url":"https://api.github.com/repos/pachterlab/kallisto/issues/190/events","html_url":"https://github.com/pachterlab/kallisto/issues/190","id":384132125,"node_id":"MDU6SXNzdWUzODQxMzIxMjU=","number":190,"title":"request: put technology specs in a config file","user":{"login":"jamestwebber","id":963647,"node_id":"MDQ6VXNlcjk2MzY0Nw==","avatar_url":"https://avatars0.githubusercontent.com/u/963647?v=4","gravatar_id":"","url":"https://api.github.com/users/jamestwebber","html_url":"https://github.com/jamestwebber","followers_url":"https://api.github.com/users/jamestwebber/followers","following_url":"https://api.github.com/users/jamestwebber/following{/other_user}","gists_url":"https://api.github.com/users/jamestwebber/gists{/gist_id}","starred_url":"https://api.github.com/users/jamestwebber/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamestwebber/subscriptions","organizations_url":"https://api.github.com/users/jamestwebber/orgs","repos_url":"https://api.github.com/users/jamestwebber/repos","events_url":"https://api.github.com/users/jamestwebber/events{/privacy}","received_events_url":"https://api.github.com/users/jamestwebber/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-25T23:40:55Z","updated_at":"2018-11-25T23:40:55Z","closed_at":null,"author_association":"NONE","body":"With the release of `kallisto bus` and `bustools` I've been exploring how we could use these tools to upgrade our current scRNAseq pipelines. One thing that struck me is that the supported single-cell technologies are hard-coded in `main.cpp`, but the format appears to be pretty standardized.\r\n\r\nIt seems like it would be easy to break that out into a config file of some sort that the user could access, which would make it easy to 1) inspect the technology specification to verify that it matches the experiment, and b) add new specifications that might be non-standard. This could help people use kallisto when developing new sequencing protocols."}}
{"actor":{"display_login":"jamestwebber"}}