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
Samuel,
Thanks for this package -- we love it in my lab!
We have mainly been using version 0.70 but several of us have recently upgraded to the latest 1.n release. There seems to be a change to FeaturePlot_scCustom in the new version that is breaking a bunch of our scripts. We often like to use the label = TRUE argument with FeaturePlot_scCustom so as to print the Ident name directly on the plot. In version 0.70 this argument was passed to Seurat::FeaturePlot and it worked just fine.
But in 1.02 there is now a newFeaturePlot_scCustom argument label_feature_yaxis. And for some reason the label = TRUE argument in our scripts is being interpreted as trying to set the label_feature_yaxis argument, instead of being passed to Seurat::FeaturePlot. Which unfortunately throws an error.
If one explicitly sets label_feature_yaxis = FALSE then label = TRUE is passed to Seurat::FeaturePlot as before, and it works. But this is a lot of extra text to add, all to set the argument to its default value. There are obviously other workarounds so ultimately this is a pretty minor issue, but it sure would be great if cluster name labeling could work as seamlessly as it did before.
With my limited knowledge of R I'm not sure if maybe there is a way to specify what should happen to the label argument? Or maybe this is something that needs to be addressed under the hood? Your help is much appreciated!
Code example
library (Seurat)
library (scCustomize)
library (SeuratData)
data("pbmc3k.final")
# Seurat function
FeaturePlot(pbmc3k.final, "CX3CR1", label=T)
# works in 0.70, not in 1.02
FeaturePlot_scCustom(pbmc3k.final, "CX3CR1", label=T)
# works in 1.02
FeaturePlot_scCustom(pbmc3k.final, "CX3CR1", label_feature_yaxis=F, label=T)
Thanks so much for kind words! I’ll take look at this. They should be interpreted independently but something going wrong obviously. I’ll work on fix this week.
Fix is now live for this issue in the dev branch (v1.0.2.9019). The issue was due to error collision and now solved by explicitly adding the label param to FeaturePlot_scCustom to mirror the Seurat FALSE by default. I just tested with code you posted FeaturePlot_scCustom(pbmc, "CX3CR1", label = T) and it works for me. The dev branch should be stable right now (it's in prep for CRAN submission) so shouldn't be any issues. If you continue to have any issues after updating to dev branch let me know and I'll reopen the issue.
Samuel,
Thanks for this package -- we love it in my lab!
We have mainly been using version 0.70 but several of us have recently upgraded to the latest 1.n release. There seems to be a change to
FeaturePlot_scCustom
in the new version that is breaking a bunch of our scripts. We often like to use thelabel = TRUE
argument withFeaturePlot_scCustom
so as to print the Ident name directly on the plot. In version 0.70 this argument was passed toSeurat::FeaturePlot
and it worked just fine.But in 1.02 there is now a new
FeaturePlot_scCustom
argumentlabel_feature_yaxis
. And for some reason thelabel = TRUE
argument in our scripts is being interpreted as trying to set thelabel_feature_yaxis
argument, instead of being passed toSeurat::FeaturePlot
. Which unfortunately throws an error.If one explicitly sets
label_feature_yaxis = FALSE
thenlabel = TRUE
is passed toSeurat::FeaturePlot
as before, and it works. But this is a lot of extra text to add, all to set the argument to its default value. There are obviously other workarounds so ultimately this is a pretty minor issue, but it sure would be great if cluster name labeling could work as seamlessly as it did before.With my limited knowledge of R I'm not sure if maybe there is a way to specify what should happen to the
label
argument? Or maybe this is something that needs to be addressed under the hood? Your help is much appreciated!Code example
sessionInfo() output
The text was updated successfully, but these errors were encountered: