Skip to content
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

runGenePeakcorr error: the condition has length > 1 #16

Open
lizakulaeva opened this issue Dec 1, 2022 · 3 comments
Open

runGenePeakcorr error: the condition has length > 1 #16

lizakulaeva opened this issue Dec 1, 2022 · 3 comments

Comments

@lizakulaeva
Copy link

Hi, I'm trying to run the function runGenePeakcorr with the sparse matrix for scRNAseq and SummarizedExperiment object of scATACseq and get this error:

Error in if (!class(obj) %in% c("SummarizedExperiment", "RangedSummarizedExperiment", :
the condition has length > 1

How I can solve it?

Thank you in advance!

@vkartha
Copy link

vkartha commented Dec 31, 2022

Hi there!

A bit odd because that exact condition check doesn't exist in the current codebase (i.e. it was changed from the check above to stopifnot(inherits(ATAC.se,"RangedSummarizedExperiment")), for this very reason). How recently did you pull/install/update this FigR repo?

Can you tell me what is returned when you run the following on your input SummarizedExperiment object, which I denote as SE below (for the scATAC data):

class(SE)

@vkartha
Copy link

vkartha commented Jan 8, 2023

@lizakulaeva The code that was throwing this error was from an internal function centerCounts, that takes either a SummarizedExperiement or Matrix-like object and normalizes the ATAC-seq peak counts for each cell. The check is to make sure your input is in the right format, as per my comment above. I've changed the check such that it won't throw that conditional error (the check is still performed, but differently). It would still be good for you to make sure your input is in the accepted format. Happy to provide more assistance if you can confirm the input class, as per above (perhaps after first updating FigR on your end to include the latest update). Thanks so much!

@vkartha
Copy link

vkartha commented Feb 9, 2023

@lizakulaeva were you able to get this working? Thanks, appreciate the feedback. Otherwise I'll close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants