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
In , @allyhawkins created a function spatial_coldata_to_df() that adds some of the data from the spatialData slot of a SpatialExperiment to the main colData contents after merging.
For scpcaTools, I think it would make sense to wrap that functionality into coldata_to_df(), where the function would check whether we were working with a SpatialExperiment, and if so, merge all contents of the spatialData slot with the colData contents.
There is a small wrinkle in that we expect spatialData to go away in a future version of the SpatialExperiment package drighelli/SpatialExperiment#84. We should plan to deal with that case as we write this for futureproofing.
The text was updated successfully, but these errors were encountered:
I would say that this is no longer needed, since we aren't doing any import of the spatial output into spatial experiments in R at all currently. It might be helpful to have in the package if we ever were planning to do downstream analysis on spatial libraries, but this isn't necessary for processing the spatial data to be available on the portal.
In , @allyhawkins created a function
spatial_coldata_to_df()
that adds some of the data from thespatialData
slot of a SpatialExperiment to the maincolData
contents after merging.For scpcaTools, I think it would make sense to wrap that functionality into
coldata_to_df()
, where the function would check whether we were working with a SpatialExperiment, and if so, merge all contents of thespatialData
slot with thecolData
contents.There is a small wrinkle in that we expect
spatialData
to go away in a future version of theSpatialExperiment
package drighelli/SpatialExperiment#84. We should plan to deal with that case as we write this for futureproofing.The text was updated successfully, but these errors were encountered: