-
Notifications
You must be signed in to change notification settings - Fork 83
V15 Fix molecular-subtype-chordoma analysis #590
Conversation
@jaclyn-taroni I have two fix ideas for the lack of chordoma samples in subset for this notebook.
At this point in time, we are thinking 2 would be okay, but I wanna clear it by you before I implement it. |
There is another option - have the first step of this module be it’s own subsetting where all resulting files are committed to the repository. That is what we do for other subtyping modules. |
I was just noticing this for the other subtyping modules. I will try to follow their suit then. |
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 few small things, while biggish changes are happening.
analyses/molecular-subtyping-chordoma/00-subset-files-for-chordoma.R
Outdated
Show resolved
Hide resolved
analyses/molecular-subtyping-chordoma/00-subset-files-for-chordoma.R
Outdated
Show resolved
Hide resolved
analyses/molecular-subtyping-chordoma/00-subset-files-for-chordoma.R
Outdated
Show resolved
Hide resolved
This reverts commit 400be46.
Meant to leave that comment in the main thread... |
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 once the comments below are addressed 👍
``` | ||
This bash script the same regardless of where it is called and will first subset the data to `Chordoma` samples |
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.
Looks like you're missing a verb here, correct?
# Subset metadata | ||
subset_metadata <- histologies_df %>% | ||
dplyr::filter(short_histology == "Chordoma") %>% | ||
select( |
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.
You're calling the filter
function above using dplyr::
but not doing the same for select
here. Is this because filter
was behaving similarly to rename
as you noted in your original comment? If so, then disregard this comment. If not, removing the dplyr::
altogether (except for in the case of the rename
function) or adding the dplyr::
to the rest of the functions would be nice for consistency purposes.
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.
filter
also has a base:: function that can mess with stuff sometimes.
# remove large expression matrix that's no longer needed | ||
rm(expression_data) | ||
# now only the columns correspond to chordoma samples | ||
smarcb1_expression <- smarcb1_expression[, which(colnames(subset_expression_data) %in% subset_metadata$Kids_First_Biospecimen_ID) ] |
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 line looks weird (format-wise), did you run this through a styler?
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.
I did but it doesn't do anything with really long lines. I'd rather use dplyr::filter here anyway but was trying to keep the original code here.
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!
Merging before expected CI failure. |
Purpose/implementation Section
There are not enough chordoma samples in the subset CircleCI files to test so I switched to the approach that was used in the other subtyping modules.
Looks like the
rename
steps were not working because of library load and it was not calling thedplyr::rename
but anotherrename
. So to fix I added a series ofdplyr::
, reran the notebook with v15 and pushed the results.What GitHub issue does your pull request address?
#574
Reproducibility Checklist
These items were all taken care of previously.
Documentation Checklist
README
and it is up to date.analyses/README.md
and the entry is up to date.