Open henrikstranneheim opened 5 years ago
Would this be for a specific gene panel? Otherwise it will be tricky... What did you have in mind @henrikstranneheim ?
Preferably for all panels (going into an analysis) in one go. Then I do not have to post process the file. But it easy to call the CLI functions in a loop appending to the same file and then making the records unique. However, it should be upstreams of MIP most likely cg - adding to each analysis dynamically by querying Scout.
Ok I think one has to specify the panels on the command line. Something like this:
scout export penetrance --panel IEM --panel OMIM-AUTO
Looks great!
It would be great if info like this was available to penetrate the panel boundaries, or end up on a special case/manual annotation gene panel..
While inheritance patterns may sometimes be specific to one gene panel, as with multiple quite different disorders from one gene, most of the time this will be about the same gene and same disorder being on a bunch of different panels. Sometimes someone has annotated it as reduced penetrance, sometimes we don't know - cf OMIM-AUTO.
How would that be done in practice @dnil ?
Not simple with the current concept. Perhaps one could store local/tentative knowledge directly on genes, and make these persistent over gene updates. On panel creation / edit such info could be passed to the panels from the hgnc genes.
We use the this type of file in the analysis together with genmod to modify the inheritance models based on reduced penetrance: