Lukas Weber

Hi all, following up here regarding some of the discussion above. Is the plan to essentially move `DropletUtils::read10xCounts()` and `SpatialExperiment::read10xVisium()` into this package instead? I think this could make sense,...

Hi @HelenaLC @drighelli , I'm following up here regarding our discussions last week about moving `read10xVisium()` and the new molecule-based platform loading functions into a new package. I think my...

Hi all, I had a discussion with @estellad today and we would like to propose the following plan to move this forward. (i) @estellad has set up a new package...

> and will not include read10xVisium() > Why not? Doesn't the function read visium data into a SpatialExperiment and would thus fit very well into the SpatialExperimentIO package which has...

Thank you!

Hmm, I had thought our solution above balanced the two sets of use cases, but maybe not. Just so I am understanding correctly -- are you moving your `outs/` directories...

Thanks @PeteHaitch for the detailed examples. I agree that some of these differences vs. the defaults from `DropletUtils::read10xCounts()` could be improved, although some of them are probably also too locked...

Hi @estellad , thank you, yes I will have a look at this soon!

Hi @estellad , thanks again for this PR. I'm following up to let you know we are currently in the middle of some discussions about whether to move all the...

Hi all, updating this discussion to mention that @estellad has now submitted the separate reader package `SpatialExperimentIO` to Bioc: https://github.com/Bioconductor/Contributions/issues/3342. This contains functions for CosMx, MERSCOPE, Xenium, and STARmap. The...