-
Notifications
You must be signed in to change notification settings - Fork 18
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
[BUG/Question] What's the layer annotation variable in the spe object? #89
Comments
Hi, Since you are not using Lines 336 to 345 in c82c789
I haven't heard of this error before and would need more information, like the output of Error in inherits(ram, "try-error") || length(ram) == 0L || is.na(ram) :
'length = 3' in coercion to 'logical(1)' Maybe it's an issue with Windows 10 x64 but well, I'm not sure. Best, |
Hi Leo, That makes sense now. Thank you! For the bug, here's the traceback:
Best, |
I see, looks like Line 23 in c82c789
Line 12 in c82c789
What is the output of the following for you? ## Reproduce error
benchmarkme::get_ram()
traceback()
## R Session info
options(width = 120)
sessioninfo::session_info() It might be worth reporting the output of this at https://github.com/csgillespie/benchmarkme. Looks like csgillespie/benchmarkme#49 might be related, which coincidentally (aka suspicious now) was also reported by a Windows 10 user. Best, |
Hi Leo, This is the output of the code you provided.
|
Thanks @sluan-jh! Well, we now need to wait for a response about csgillespie/benchmarkme#49. |
Hello,
Since fetch_data returns error on my machine, I manually downloaded data from the https link for
type == "sce"
in the fetch_data() function and converted the downloaded sce to spe usingsce_to_spe()
.When I try to replicate the example code below:
I couldn't find a variable named "spatialLIBD" in the colData, but it seems using the column "layer_guess_reordered_short" produces the same result.
Is "layer_guess_reordered_short" the annotation of the layers?
Session info is attached below in case it's helpful
Thank you!
The text was updated successfully, but these errors were encountered: