Closed FedericaBrando closed 6 months ago
analysis of differences:
maybe has something to do with :
Everytime the container vep is run we have this warning:
found github issue on their web:
this PR will fix the warning on next release (v111)
Therefore the error (warning) is in the container. The problem is that, since we build the cache dir with a loop through chunks where we call the vep container multiple time, we have a smartwatch warning for each call.
waiting for monica to analyze
Some genes are no found in the datasets, Monica and I found out it is because they are filtered out in the ParseVep step. Specifically, an expected mane gene that is supposed to be annotated as mane, it is not.
I open an issue on vep github to report the bug.
To overcome the issue, we decided to use two conditional filtering:
if the transcript does not have MANE, then use the canonical.
Ensembl was updated to v111.
Something to keep in mind is that with the update of Ensembl v111 some gene name will change.
updat boostdm DriverSaturation to use MANE
DriverSaturation uses canonical.regions.tsv
TO DO (Federica): Run some cohorts as tests, updating the pipeline → Filter for MANE-Select → For the moment do NOT include the MANE- plus clinical