-
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
Add microarray gene ID conversion example #212
Conversation
- make appropriate updates to `references.bib`, `Snakefile`, and `_navbar.html` file
- add references to `references.bib` - update comments and documentation - rerun Snakefile
- rerun Snakefile
- fix formatting
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good start! This doesn't yet discuss the multivals
argument that I mentioned here: #212 (comment) so the last check in you did isn't exactly reflective of what's going on with the mappings.
I think the meaning of the multivals
argument and how it influences the output is a worthwhile thing for us to dive into. Because if you are confused by this argument, our users will definitely be confused by this too (I don't like that they have a default for this, I think it makes it easy for people to miss it). We should aim for making the multivals
argument and what it means, as clear as possible for our users.
So I think next you may want to take another closer look at the mapIds
docs and we can always schedule a zoom/Google hangout/Slack/Teams chat to discuss if that would be helpful.
Per a discussion with @cansavvy re the above comment, the plan moving forward is as follows:
|
- rename the file and propagate change in `Snakefile` and `navbar.html` - update references - rearrange notebook and rerun Snakefile
@cansavvy, I believe that I implemented the plan that we discussed and outlined in the last comment of this PR. I also implemented the suggestions you provided through your most recent review of this PR (the main ones being changing the file name, keeping the use of Please let me know if I misinterpreted any of your suggestions or missed any! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! Just have a few comments about a couple things to rearrange, I think this is close!
…xamples into cbethell/add-id-conversion-microarray
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two tiny-ish comments! LGTM after that!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple little comments. Looks like there's some template changes that might need to be done too; some that got lost: #216 (comment)
But I will probably file a separate PR to change these everywhere since this will affect every module and I haven't yet figured out the full extent of what needs to be changed.
Co-authored-by: Candace Savonen <cansav09@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'm playing with the settings that require branches to be up to date before merging. I am going to merge this despite the lack of status check (that I do not currently understand). |
Purpose:
What issue(s) does your PR address?
This PR closes #113 (the issue on creating a microarray gene ID conversion example notebook).
Strategy
What was your strategy for this new or edited analysis?
I followed the comments on issue #113 and found a new (larger than n = 4 samples) mouse microarray dataset.
The dataset used in this paper is a [mouse glioma cancer stem cell dataset](Cancer Stem Cells Are Enriched In The Side-Population Cells In A Mouse Model Of Glioma) with n = 15 samples (which has been uploaded to the S3 bucket for testing/review).
I then copied the analysis steps from the RNA-seq gene ID conversion notebook, but changed the annotation package being loaded in to that relevant to the mouse genome.
Concerns/Questions for reviewers:
What things should reviewers look out for?
Explore mapped data frame
section seem helpful? Are the added steps clear? Is there anything that should be added/removed from this section?Analysis Pull Request Check List (roughly in order):
Content checks
{{BLANKS}}
have been replaced with the correct content.Formatting Checks
Add datasets to S3
Docker/Snakemake rendering components
.html
link to the navigation bar.