-
Notifications
You must be signed in to change notification settings - Fork 0
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
Instructions on how to use / save / read TileDBArrays in a SummarizedExperiment #17
Comments
I wasn't planning to. I suppose it would be possible to fit in the multiple assays as separate TileDB attributes, and the metadata can probably be serialized for storage in the TileDB metadata, but I don't have a clear idea of how to deal with the |
I interpreted the question differently. The HDF5Array functions only save the assay data to HDF5, the rowData, colData, etc. are serialised as .rds. Is that what you're asking for @tomsing1 ? |
Thanks a lot for the quick responses! Yes, I was thinking along the lines of what the Of course, if @LTLA has an even smarter idea to keep everything inside tiledb, that would be more than welcome, too. |
(Just chiming in to say that we're all ears and happy to help. We can do some R-specific things in the tiledb R package for metadata serialization, we can (and very likely will "soon") do something generic at the TileDB library level (as we need similar features in other projects). It is all relatively new stuff, and I am currently focussed on gettting a TileDB Cloud R package up and running.) |
So great to see the
TileDBArray
backend join the Bioconductor family 👍 .A quick question: are you planning to create helper functions to save / read
SummarizedExperiments
withTileDBArray
backends? Analogous to what Herve Pages has provided in theHDF5Array
package here for instance?Or perhaps there already are examples of how to persist
TileDBArray
-backedSummarizedExperiments
that I could learn from?The text was updated successfully, but these errors were encountered: