Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Effect of using reference other than hg19 in getMutationTypes.pl #11

Open
MUppal opened this issue Mar 15, 2020 · 1 comment
Open

Effect of using reference other than hg19 in getMutationTypes.pl #11

MUppal opened this issue Mar 15, 2020 · 1 comment

Comments

@MUppal
Copy link

MUppal commented Mar 15, 2020

Quick question here regarding extending TrackSig beyond the hg19 reference build. In src/getMutationTypes.pl, line 16 has the explicit delineation of using hg19:
my %fastaHandles = ("path" => "annotation/hg19/");

My question is, could other reference files be used, like hg38, with the corresponding set of chromosomes used, and simple alteration of line 16? Would this result in any meaningful change of performance in TrackSig? Or is TrackSig meant to be used only with hg19-aligned genomes?

@YuliaRubanova
Copy link
Collaborator

Hi!
In theory, TrackSig should still run after changing hg19 to hg38. However, the signature definitions that we use were derived from tumours with hg19 calls.

The definitions of COSMIC mutational signatures also should be agnostic to the version of the genome: https://cancer.sanger.ac.uk/cosmic/signatures?genome=38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants