Closed jeremycfd closed 3 years ago
Hi Jeremy,
Thanks, I found the source of the problem; it is with the naming convention in Seurat objects. I am patching it and releasing a new version on CRAN. This does not change the underlying algorithm at all, just the naming convention. Thanks for bringing this up! I will comment again when the new version is up on CRAN; should be within 1-2 days.
Thanks so much! Really appreciate the quick response! Great work, by the way!
No problem Jeremy, and thank you. SignacX 2.2.2 is now up on CRAN. Can you give it a try and let me know if it fixes your issue? If I do not hear from you, I will close the issue in a few days.
Closing for now; please open a new issue if problem persists.
I've been using SignacX without issue for a while now. I recently updated a number of R packages, including Seurat, and now SignacX doesn't work. I've tried downgrading Seurat before creating the Seurat object, but that hasn't resolved the issue, so I'm wondering if another package that was automatically updated is causing the underlying problem. Strangely, loading an older Seurat object into R even with a new version of Seurat seems to work fine...
This produces "labels" but clearly only full of errors: