-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error running Vignette #56
Comments
Hi Adriano, Could you check if you're using the latest version of spicyR (1.18)? |
I was on 1.16 and upgraded now. The example with
This is how the
|
Could you share a subset of the data with us so we can reproduce and fix the issue? Additionally, could you try setting window = "square"? That might solve the problem of points lying outside the specified window |
find some example data and the script here: https://polybox.ethz.ch/index.php/s/4ZJGFlIUiRVSxbl I think the problem is if the interaction does not appear in a sample...the dataset I provide is a random subset with very few cells per sample with which spicy errors. However, if I ensure that I only have samples with the interaction it seems to work. Best, |
Thanks for the example data. It does look like the fact that there are very few cells per image is causing problems with model fit. Setting window = "square" gets rid of the error. You could also set weightsByPair = TRUE if evaluating the relationship for only one cell type pair so spicy won't take into account the other low frequency cell types when weighting images. Another quick note based on your code, spicy doesn't automatically pick up the subject column like it does for imageID and cellType, so you would need to specify subject = "subject" to build a mixed effects model. |
Hi!
Thanks for the great package. I wanted to try it out on our dataset however I run into an error running the Vignette.
Throws an error
If I run it on my data and a plain data.frame I get an error that one point was rejected because it lies outside the specified window.
Best,
Adriano
The text was updated successfully, but these errors were encountered: