adapted from NCBI-Hackathons/GoodDoc with some tweaks for analysis-driven projects
instructions in italics can be deleted as sections are filled in
most fields are optional, Conclusion and Important Resources are required
...and a link to the DOI: You can make a free DOI with zenodo, synapse, figshare, or other resources
- Additional kinome data from all drugs and compounds in the world
- Toxicity data based on kinases inhibited
- Pathway interactions from kinases to others, up and down regulating (Kegg?)
- More Kinome screening data from the tumors we're trying to identify drugs for (to cancel out error rates)
- Adding to the pipeline
- Implementing multiple pipeline components, such as feedback loops from drug screending data (both positive and negative)
- Ability to use Kinase expressions from a single tumor for personalized drug predictions
- Add toxicity predictions
- Add combination therapy predictions
- Add RNA predictions
- Toxicity prediction module
- Pathway extentions, to amend the kinase data with downstream regulating factors
- Implement module for feedback loop on durg screening data
- Math
- Biology, drug screening
- Scrape the Synodos Kinase profiling into database using
loadKinese
function - Download all Lincs data using the
downloadLincs
function to local machine - Populate kinase inhibition molecule data from Lincs data with function
loadLincs
- Use
scoreKinase
function to rank the important kinases for the relevant tumor sample, eg:baselines=Syn1_SF,Syn2_SF
andalternatives=Syn5_SF,Syn6_SF,Syn8,Syn10,Syn11
- Calculate the best drugs using the
scoreDrugs
function