You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This means I'm addressing the covariates twice—once in ScaleData and again in RunHarmony. My questions are:
Is this redundancy problematic?
Specifically, could correcting for covariates at both steps lead to overcorrection?
What are the potential consequences of regressing out covariates in both steps?
Could it affect downstream analyses like clustering or differential expression by reducing variability too much?
What would be the recommended best practice?
Should I regress out covariates only during RunHarmonyor OK to use them in both?
E.g. marker heatmap plots are based on ScaleData, that is one reason to correct already at scaling (of course I could redo scaling and PCA after Harmony).
I'd appreciate any guidance on whether I should adjust my workflow to correct for covariates in just one of these steps to avoid problems that you can foresee.
Thank you for your help!
The text was updated successfully, but these errors were encountered:
Hello,
Thank you for this cool method, I had very nice results with it!
When I'm analyzing scRNA-seq data using Seurat and Harmony, I'm regressing out covariates (e.g., library, sample type) at two steps:
This means I'm addressing the covariates twice—once in
ScaleData
and again inRunHarmony
. My questions are:RunHarmony
or OK to use them in both?ScaleData
, that is one reason to correct already at scaling (of course I could redo scaling and PCA after Harmony).I'd appreciate any guidance on whether I should adjust my workflow to correct for covariates in just one of these steps to avoid problems that you can foresee.
Thank you for your help!
The text was updated successfully, but these errors were encountered: