Re: [Bioc-devel] [question about class extension]

Pleased to try also: ``` sapply(c("SummarizedExperiment", "MultiAssayExperiment"), library, character.only = T) new <- SummarizedExperiment() metadata(new) <- list(MultiAssayExperiment()) new ``` Again, it is a preference. kind regards, Sean On Wed, Jan 24, 2024 at 6:06 AM migdal migdal wrote

Re: [Bioc-devel] [question about class extension]

Hi Delphine, I had a similar dilemma while developing midasHLA package. There, we wanted to have unique features names across all experiments and colData as well as mandatory metadata. To this end I wrote a new class specific to my package that extends MAE.

Re: [Bioc-devel] [question about class extension]

There aren't strict standards imposed on many of the packages in Bioconductor introducing classes, but many other packages extend and impose standards and constraints for given areas/fields/subjects. If you are considering this route, something like the following could work to determine if introd

[Bioc-devel] [question about class extension]

Dear Bioc developer, We are developing a package and have used the MultiAssayExperiment class to manage our data. We need to impose a particular structure on the slot metadata of the MAE object (list => named list) because we havec defined methods that depend on this named list. Is it good pract