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 that way, it will populate the metadata with NA and shows show a warning instead.
I am not sure if it was discussed before. Otherwise, it would be nice to specify more clearly that the problem is within the metadata.
Here is an example of the problem if we add year_to_death column.
Sure, just replace the column with NULL like you would do with an R data.frame:
colData(se)$foo <- NULL
In my opinion, the current behavior is fine. If there are inconsistencies in the metadata, the user should do something explicit. For consistency, safety, etc, cbind() should just do rbind() on the column metadata. Maybe there could be a merge() method that is more forgiving.
On Aug 1, 2019, at 10:59 PM, Michael Lawrence ***@***.***> wrote:
Sure, just replace the column with NULL like you would do with an R data.frame:
colData(se)$foo <- NULL
In my opinion, the current behavior is fine. If there are inconsistencies in the metadata, the user should do something explicit. For consistency, safety, etc, cbind() should just do rbind() on the column metadata. Maybe there could be a merge() method that is more forgiving.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
Hello,
this is just a suggestion. If a have to SE, with the same data, but one has a metadata column that the other does not have.
The package gives the following error:
But instead of using a
rbind
wouldn't it be better to use arbind.fill
(https://www.rdocumentation.org/packages/plyr/versions/1.8.4/topics/rbind.fill)in this part code
SummarizedExperiment/R/SummarizedExperiment-class.R
Line 711 in 01aa07a
In that way, it will populate the metadata with NA and shows show a warning instead.
I am not sure if it was discussed before. Otherwise, it would be nice to specify more clearly that the problem is within the metadata.
Here is an example of the problem if we add year_to_death column.
The text was updated successfully, but these errors were encountered: