-
Notifications
You must be signed in to change notification settings - Fork 5
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
LINCS hit query #14
Comments
Thanks for setting up this issue. I agree with the motivation and the authorship, if we include this. I can definitely give you that output. But it will take a bit longer to build that df. You proposed df also has a lot more information then needed for the simple histogram. |
We should also add the MOAs of both compounds to that df since that will allow for more MOA focussed plots instead of counting the compounds |
Sounds good! I am aiming for a July 1 submission, so in order for us to include it, I will need it before then. Two additional points that you might want to consider:
Thanks! |
Yea good points! |
@gwaygenomics Can you point me to which level5 I should be using |
level 5 links: Thanks! |
@michaelbornholdt produced the analysis here: broadinstitute/neural-profiling#2 (comment) I will ingest the output files in this repo for visualization |
@michaelbornholdt presented an analysis on querying "hits" during profiling checkin today.
I'd love to be able to include this analysis in the LINCS complementarity paper. Michael estimated that his analysis would take ~2 hours.
Specification
Input data
Output
I think I need to understand the "hit" analysis better. Given a compound, you're asking if you match another replicate as the top hit? So essentially the output is a ranked list of matches per compound and whether or not they map to the same category?
If so, then can you output the following data frame?
Let's iterate on the final output specifications if my understanding above is limited in any way.
A couple preliminary figures and statistics would also be helpful.
Motivation
The text was updated successfully, but these errors were encountered: