Skip to content

Commit

Permalink
Merge pull request #37 from ccb-hms/learner_profiles
Browse files Browse the repository at this point in the history
Learner profiles
  • Loading branch information
andrewGhazi authored Sep 16, 2024
2 parents ef217e4 + b950951 commit d77ef7d
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 7 deletions.
29 changes: 23 additions & 6 deletions episodes/intro-sce.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -128,19 +128,20 @@ We can think of this (and other) class as a _container_, that contains several d

Depending on the object, slots can contain different types of data (e.g., numeric matrices, lists, etc.). Here we'll review the main slots of the SingleCellExperiment class as well as their getter/setter methods.


:::: challenge

Before `SingleCellExperiment`, coders working with single cell data would sometimes keep all of these components in separate objects e.g. a matrix of counts, a data.frame of sample metadata, a data.frame of gene annotations and so on. What are the main disadvantages of this sort of "from scratch" approach?

Try to get the data for a different sample from `WTChimeraData` (other than the fifth one)
::: solution

1. You have to do tons of book-keeping! If you perform a QC step that removes dead cells, now you also have to remember to remove that same set of cells from the cell-wise metadata. Dropped un-expressed genes? Don't forget to filter the gene metadata table too.
Here we assign the sixth sample to `sce6`:

2. All the downstream steps have to be "from scratch" as well! All the data munging, analysis, and visualization code has to be customized to the idiosyncrasies of your input. Agh!
```{r, message = FALSE, warning=FALSE, eval=FALSE}
sce6 <- WTChimeraData(samples = 6)
sce6
```
:::

::::

### `assays`
Expand Down Expand Up @@ -265,6 +266,22 @@ combined_sce

:::::::::::::::::::::::::::::::::::::::::::::

:::: challenge

#### Extension Challenge 1

Before `SingleCellExperiment`, coders working with single cell data would sometimes keep all of these components in separate objects e.g. a matrix of counts, a data.frame of sample metadata, a data.frame of gene annotations and so on. What are the main disadvantages of this sort of "from scratch" approach?

::: solution

1. You have to do tons of book-keeping! If you perform a QC step that removes dead cells, now you also have to remember to remove that same set of cells from the cell-wise metadata. Dropped un-expressed genes? Don't forget to filter the gene metadata table too.

2. All the downstream steps have to be "from scratch" as well! All the data munging, analysis, and visualization code has to be customized to the idiosyncrasies of your input. Agh!

:::

::::

:::::::::::::: checklist

## Further Reading
Expand Down
5 changes: 4 additions & 1 deletion instructors/instructor-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,7 @@
title: 'Instructor Notes'
---

This is a placeholder file. Please add content here.

This workshop is based on the [OSCA tutorial](https://github.com/Bioconductor/ISMB.OSCA) that Davide Risso, Dario Righelli, Marcel Ramos, and myself gave at the ISMB conference last year. The tutorial is a light version of the [OSCA book](https://bioconductor.org/books/release/OSCA/) that concentrates on essential aspects for getting started with the book ("The OSCA book in a day"). The tutorial is in large parts a faithful copy of the OSCA book, but also adds contents that are not (yet) covered in the OSCA book such as interoperability with other popular single-cell analysis ecosystems and accessing data from the Human Cell Atlas.

The learner profiles page covers the pre-requisites including the basics of statistics, R, and molecular biology. Point this out to students in order to help direct those missing large pieces of the foundation toward where they need to go.

0 comments on commit d77ef7d

Please sign in to comment.