-
Notifications
You must be signed in to change notification settings - Fork 926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with running IntegrateData -- failing to select a single reference model #4355
Comments
HI, @tcikezu |
Hi @yuhanH, here is a script to replicate the error:
Many thanks for looking into this. |
Hi, |
Hi @yuhanH -- default assay used was 'integrated'. I re-tried again, this time adding this line:
before running |
A safest strategy is that you create an object only containing RNA assay of your subset cells. |
Okay, thank you! |
@tcikezu It is fixed in the develop branch. Thanks for reporting this. |
Hi ! it's not fixed. I had the same error with Seurat 4.2
Merging dataset 1 into 2 |
any solution for this problem? |
@BenjaminDEMAILLE Were you able to resolve this issue? |
Not. I update to 5.1 |
I still face the same issue. Any updates? |
I ran the integration pipeline, clustered, and then found a subset that I wanted to analyze further. I re-ran the integration pipeline with this subset (beginning from the RNA assay, recomputed SCT assay, ...), and found this error while calling IntegrateData:
The error is produced if we set
reference=1
while callingIntegrateData
on a previously integrated dataset. Relevant lines are fromintegration.R
(lines 1094 - 1119)The issue is
Tool(object = reference.integrated, slot = "Integration"))
does not returnNULL
, even ifreference.integrated
is the result of runningPairwiseIntegrateReference
on ananchorset
withreference.object
slot of length 1. (TheIntegration
Tool slot probably remains from the previous integration.) Is there an easy way to remove this slot from just the reference model in case it exists? If that can be done inPairwiseIntegrateReference
then I think this issue can be resolved.The text was updated successfully, but these errors were encountered: