-
Notifications
You must be signed in to change notification settings - Fork 21
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updating a bit the documentation and small bug correction.
- Loading branch information
Showing
12 changed files
with
234 additions
and
128 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,27 +1,27 @@ | ||
Package: EPIC | ||
Type: Package | ||
Title: Estimate the Proportion of Immune and Cancer cells | ||
Version: 1.1.6 | ||
Authors@R: as.person(c( | ||
"Julien Racle <[email protected]> [aut, cre]", | ||
"David Gfeller <[email protected]> [aut]" | ||
)) | ||
Description: Package implementing EPIC method to estimate the proportion of | ||
immune, stromal, endothelial and cancer or other cells from bulk gene | ||
expression data. | ||
It is based on reference gene expression profiles for the main non-malignant | ||
cell types and it predicts the proportion of these cells and of the | ||
remaining "other cells" (that are mostly cancer cells) for which no | ||
reference profile is given. | ||
Depends: | ||
R (>= 3.2.0) | ||
License: file LICENSE | ||
LazyData: TRUE | ||
RoxygenNote: 7.2.1 | ||
Suggests: | ||
testthat, | ||
knitr, | ||
rmarkdown | ||
Imports: | ||
stats | ||
VignetteBuilder: knitr | ||
Package: EPIC | ||
Type: Package | ||
Title: Estimate the Proportion of Immune and Cancer cells | ||
Version: 1.1.7 | ||
Authors@R: as.person(c( | ||
"Julien Racle <[email protected]> [aut, cre]", | ||
"David Gfeller <[email protected]> [aut]" | ||
)) | ||
Description: Package implementing EPIC method to estimate the proportion of | ||
immune, stromal, endothelial and cancer or other cells from bulk gene | ||
expression data. | ||
It is based on reference gene expression profiles for the main non-malignant | ||
cell types and it predicts the proportion of these cells and of the | ||
remaining "other cells" (that are mostly cancer cells) for which no | ||
reference profile is given. | ||
Depends: | ||
R (>= 3.2.0) | ||
License: file LICENSE | ||
LazyData: TRUE | ||
RoxygenNote: 7.2.1 | ||
Suggests: | ||
testthat, | ||
knitr, | ||
rmarkdown | ||
Imports: | ||
stats | ||
VignetteBuilder: knitr |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
# Generated by roxygen2: do not edit by hand | ||
|
||
export(EPIC) | ||
# Generated by roxygen2: do not edit by hand | ||
export(EPIC) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -84,6 +84,21 @@ and David Gfeller ([[email protected]](mailto:[email protected])). | |
|
||
|
||
## FAQ | ||
##### Which proportions returned by EPIC should I use? | ||
* EPIC is returning two proportion values: *mRNAProportions* and *cellFractions*, | ||
where the 2nd represents the true proportion of cells coming from the different | ||
cell types when considering differences in mRNA expression between cell types. | ||
So in principle, it is best to consider these *cellFractions*. | ||
|
||
However, please note, that when the goal is to benchmark EPIC predictions, if | ||
the 'bulk samples' correspond in fact to in silico samples reconstructed for | ||
example from single-cell RNA-seq data, then it is usually better to compare the | ||
'true' proportions against the *mRNAProportions* from EPIC. Indeed, when | ||
building such in silico samples, the fact that different cell types express | ||
different amount of mRNA is usually not taken into account. On the other side, | ||
if working with true bulk samples, then you should compare the true cell | ||
proportions (measured e.g., by FACS) against the *cellFractions*. | ||
|
||
##### What do the "*other cells*" represent? | ||
* EPIC predicts the proportions of the various cell types for which we have | ||
gene expression reference profiles (and corresponding gene signatures). But, | ||
|
@@ -99,7 +114,7 @@ epithelial cells for example. | |
Please make sure that your bulk data is in the form of a matrix (and also | ||
your reference gene expression profiles if using custom ones). | ||
|
||
##### What is the meaning of the warning message telling that some mRNA_cell values are unknown? | ||
##### Is there some caution to consider about the *cellFractions* and *mRNA_cell* values? | ||
* As described in our manuscript, EPIC first estimates the proportion of mRNA | ||
per cell type in the bulk and then it uses the fact that some cell types have | ||
more mRNA copies per cell than other to normalize this and obtain an estimate of | ||
|
@@ -108,10 +123,10 @@ if you need the one or the other). For this normalization we had either measured | |
the amount of mRNA per cell or found it in the literature (fig. 1 – fig. | ||
supplement 2 of our paper). However we don’t currently have such values for the | ||
endothelial cells and CAFs. Therefore for these two cell types, we use an average | ||
value, which might not reflect their true value and this is the reason why we | ||
output this message. If you have some values for these mRNA/cell abundances, you | ||
can also add them into EPIC, with help of the parameter "*mRNA_cell*" or | ||
“*mRNA_cell_sub*” (and that would be great to share these values). | ||
value, which might not reflect their true value and this could bias a bit the | ||
predictions, especially for these cell types. If you have some values for these | ||
mRNA/cell abundances, you can also add them into EPIC, with help of the parameter | ||
"*mRNA_cell*" or “*mRNA_cell_sub*” (and that would be great to share these values). | ||
|
||
If the mRNA proportions of these cell types are low, then even if you don't | ||
correct the results with their true mRNA/cell abundances, it would not really | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -85,6 +85,24 @@ Julien Racle (<[email protected]>), and David Gfeller | |
|
||
## FAQ | ||
|
||
##### Which proportions returned by EPIC should I use? | ||
|
||
- EPIC is returning two proportion values: *mRNAProportions* and | ||
*cellFractions*, where the 2nd represents the true proportion of cells | ||
coming from the different cell types when considering differences in | ||
mRNA expression between cell types. So in principle, it is best to | ||
consider these *cellFractions*. | ||
|
||
However, please note, that when the goal is to benchmark EPIC | ||
predictions, if the ‘bulk samples’ correspond in fact to in silico | ||
samples reconstructed for example from single-cell RNA-seq data, then | ||
it is usually better to compare the ‘true’ proportions against the | ||
*mRNAProportions* from EPIC. Indeed, when building such in silico | ||
samples, the fact that different cell types express different amount | ||
of mRNA is usually not taken into account. On the other side, if | ||
working with true bulk samples, then you should compare the true cell | ||
proportions (measured e.g., by FACS) against the *cellFractions*. | ||
|
||
##### What do the “*other cells*” represent? | ||
|
||
- EPIC predicts the proportions of the various cell types for which we | ||
|
@@ -104,7 +122,7 @@ Julien Racle (<[email protected]>), and David Gfeller | |
matrix (and also your reference gene expression profiles if using | ||
custom ones). | ||
|
||
##### What is the meaning of the warning message telling that some mRNA_cell values are unknown? | ||
##### Is there some caution to consider about the *cellFractions* and *mRNA_cell* values? | ||
|
||
- As described in our manuscript, EPIC first estimates the proportion of | ||
mRNA per cell type in the bulk and then it uses the fact that some | ||
|
@@ -115,11 +133,11 @@ Julien Racle (<[email protected]>), and David Gfeller | |
mRNA per cell or found it in the literature (fig. 1 – fig. supplement | ||
2 of our paper). However we don’t currently have such values for the | ||
endothelial cells and CAFs. Therefore for these two cell types, we use | ||
an average value, which might not reflect their true value and this is | ||
the reason why we output this message. If you have some values for | ||
these mRNA/cell abundances, you can also add them into EPIC, with help | ||
of the parameter “*mRNA_cell*” or “*mRNA_cell_sub*” (and that would be | ||
great to share these values). | ||
an average value, which might not reflect their true value and this | ||
could bias a bit the predictions, especially for these cell types. If | ||
you have some values for these mRNA/cell abundances, you can also add | ||
them into EPIC, with help of the parameter “*mRNA_cell*” or | ||
“*mRNA_cell_sub*” (and that would be great to share these values). | ||
|
||
If the mRNA proportions of these cell types are low, then even if you | ||
don’t correct the results with their true mRNA/cell abundances, it | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -80,6 +80,21 @@ and David Gfeller ([[email protected]](mailto:[email protected])). | |
|
||
|
||
## FAQ | ||
##### Which proportions returned by EPIC should I use? | ||
* EPIC is returning two proportion values: *mRNAProportions* and *cellFractions*, | ||
where the 2nd represents the true proportion of cells coming from the different | ||
cell types when considering differences in mRNA expression between cell types. | ||
So in principle, it is best to consider these *cellFractions*. | ||
|
||
However, please note, that when the goal is to benchmark EPIC predictions, if | ||
the 'bulk samples' correspond in fact to in silico samples reconstructed for | ||
example from single-cell RNA-seq data, then it is usually better to compare the | ||
'true' proportions against the *mRNAProportions* from EPIC. Indeed, when | ||
building such in silico samples, the fact that different cell types express | ||
different amount of mRNA is usually not taken into account. On the other side, | ||
if working with true bulk samples, then you should compare the true cell | ||
proportions (measured e.g., by FACS) against the *cellFractions*. | ||
|
||
##### What do the "*other cells*" represent? | ||
* EPIC predicts the proportions of the various cell types for which we have | ||
gene expression reference profiles (and corresponding gene signatures). But, | ||
|
@@ -95,7 +110,7 @@ epithelial cells for example. | |
Please make sure that your bulk data is in the form of a matrix (and also | ||
your reference gene expression profiles if using custom ones). | ||
|
||
##### What is the meaning of the warning message telling that some mRNA_cell values are unknown? | ||
##### Is there some caution to consider about the *cellFractions* and *mRNA_cell* values? | ||
* As described in our manuscript, EPIC first estimates the proportion of mRNA | ||
per cell type in the bulk and then it uses the fact that some cell types have | ||
more mRNA copies per cell than other to normalize this and obtain an estimate of | ||
|
@@ -104,10 +119,10 @@ if you need the one or the other). For this normalization we had either measured | |
the amount of mRNA per cell or found it in the literature (fig. 1 – fig. | ||
supplement 2 of our paper). However we don’t currently have such values for the | ||
endothelial cells and CAFs. Therefore for these two cell types, we use an average | ||
value, which might not reflect their true value and this is the reason why we | ||
output this message. If you have some values for these mRNA/cell abundances, you | ||
can also add them into EPIC, with help of the parameter "*mRNA_cell*" or | ||
“*mRNA_cell_sub*” (and that would be great to share these values). | ||
value, which might not reflect their true value and this could bias a bit the | ||
predictions, especially for these cell types. If you have some values for these | ||
mRNA/cell abundances, you can also add them into EPIC, with help of the parameter | ||
"*mRNA_cell*" or “*mRNA_cell_sub*” (and that would be great to share these values). | ||
|
||
If the mRNA proportions of these cell types are low, then even if you don't | ||
correct the results with their true mRNA/cell abundances, it would not really | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.