You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wow that's quite the difference! One issue might be that when getting the most severe consequence we might get it from the "wrong" hgnc id and then genmod will score that consequence rather than the intended. Just needs some thought to make sure we get it right 😅
Wow that's quite the difference! One issue might be that when getting the most severe consequence we might get it from the "wrong" hgnc id and then genmod will score that consequence rather than the intended. Just needs some thought to make sure we get it right 😅
I added filtering at the very end (one reason why it might be slower than in raredisease, although it looks like it still takes an hour or so there), so the most severe consequence is already set and everything else should be the same I think.
Well, agree with @jemten here - as long as the most severe consequences are not touched we should be reasonably good. I'm guessing the cutoff distances for "upstream" etc should be ok, but if they are generous we may be seeing more variants with multiple genes matched. They do take longer for the analysts to look at - not a whole lot, but one has to consider each of them, note they are not in the panel and see that the consequence is just nothing. But man hours spent vs the runtime, it this is more than just a handful of variants affected.
Description of feature
filter_vep is currently painfully slow for SNVs and INDELs (~2h 45m).
Other tools should be able to filter on HGNC ID, for example bcftools which completes in a couple of minutes.
It keeps the exact same sites, but does not remove annotations for HGNC IDs that are not a match. E.g. Only HNC_ID:4053 is kept with filter_vep:
but with split-vep both HNC_ID:4053 and HGNC:24149 are kept, even though only 4053 was in
hgnc_ids_with_hgnc_prefix.txt
:The text was updated successfully, but these errors were encountered: