This repository has been archived by the owner on Jun 21, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 83
#932 Part N Kinase domain overlap as hotspot #940
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose/implementation Section
What scientific question is your analysis addressing?
We would like to gather all unique sites overlapping the kinase domain as snv/indel hotpsots in our dataset which are not Cosmic Census genes or in MSKCC cancer hotspots.
What was your approach?
I used biomaRt and files downloaded from http://hgdownload.soe.ucsc.edu/goldenPath/hg38/database/pfamDesc.txt.gz and http://hgdownload.soe.ucsc.edu/goldenPath/hg38/database/ucscGenePfam.txt.gz .
After gathering kinase domain locations I gathered mutation sites that overlap kinase domain as hotspots.
What GitHub issue does your pull request address?
#932
Directions for reviewers. Tell potential reviewers what kind of feedback you are soliciting.
Which areas should receive a particularly close look?
Does the function gathering the pfam location seem OK? I'm not sure how to version the downloaded pfam files might get out of date, not sure?
Is there anything that you want to discuss further?
I only used PF00069 domain, do we want to look at other kinase domains?
Is the analysis in a mature enough form that the resulting figure(s) and/or table(s) are ready for review?
Yes
Results
What types of results are included (e.g., table, figure)?
tables
What is your summary of the results?
2178 unique sites per Kids_First_Biospecimen_ID overlap a PF00069 domain location
Reproducibility Checklist
Documentation Checklist
README
and it is up to date.analyses/README.md
and the entry is up to date.