You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the Xenium example dataset from 10X to generate a SpatialExperiment object. I first create a SingleCellExperiment object and then pass it to the constructor.
Below I have two SpatialExperiment constructor calls. The first call does not capture all the information from the sce object. The second call is a workaround to include this information explicitly.
The expected behavior is that the SpatialExperiment constructor provide a very similar SPE (if not identical) to the latter when provided with a SingleCellExperiment object.
Unfortunately, it seems that the mainExpName, rowData, and altExpNames (and possibly the reducedDimNames) are lost when an SCE is provided to the constructor.
I think the information should be kept as is as much as possible.
Note that as(sce, "SpatialExperiment") does a good job at keeping the information in the object.
Hi Dario, @drighelli
I am using the Xenium example dataset from 10X to generate a
SpatialExperiment
object. I first create aSingleCellExperiment
object and then pass it to the constructor.Below I have two
SpatialExperiment
constructor calls. The first call does not capture all the information from thesce
object. The second call is a workaround to include this information explicitly.The expected behavior is that the
SpatialExperiment
constructor provide a very similar SPE (if not identical) to the latter when provided with aSingleCellExperiment
object.Unfortunately, it seems that the
mainExpName
,rowData
, andaltExpNames
(and possibly thereducedDimNames
) are lost when an SCE is provided to the constructor.I think the information should be kept as is as much as possible.
Note that
as(sce, "SpatialExperiment")
does a good job at keeping the information in the object.Best regards,
Marcel
Created on 2024-12-09 with reprex v2.1.1
The text was updated successfully, but these errors were encountered: