Hervé Pagès
Hervé Pagès
Alright. Let me take a look at **kmcut**. Sorry for the slow response.
Hi @ibkstore, Sorry again for the delay. Here is some feedback: 1. The vignette contains the following line: ``` Introduction to the KMCUT package ``` but the name of the...
Hi @ibkstore, do you intend to follow up on this submission? Best, H.
Hi @ibkstore, Thanks for getting back to me. > I do intend to follow-up on this submission. Great! > I am used to feedback from journal article reviewers The review...
@ibkstore Welcome back! > Does this look like a correct sequence? No, this is not how you are supposed to resync the **kmcut** repo at git.bioconductor.org with the repo on...
Our build machines have internet access. Generally speaking it's ok to assume that internet is available in your vignettes and man page examples. As for access to the Cytoscape Desktop...
Thanks @krlmlr !
Changing how a SumarizedExperiment gets displayed should not be a side effect of loading the package
Hi Stefano, See for a cleaner OO approach here: https://github.com/Bioconductor/Contributions/issues/3616#issuecomment-2423413619 The idea is to formalize the "SummarizedExperiment-tibble Abstraction" by wrapping the SummarizedExperiment object in an S4 shell. Maybe **tidySummarizedExperiment**, **tidySingleCellExperiment**,...
Changing how a SumarizedExperiment gets displayed should not be a side effect of loading the package
Thanks Stefano. I'm a little bit confused though. The **tidyprint** package changes again the default display of SE objects. How does that address the original issue? I appreciate the fact...
Changing how a SumarizedExperiment gets displayed should not be a side effect of loading the package
Displacing the problem to a dedicated package doesn't change the fact that, if we accept this new package, we will again have a package in the ecosystem that changes the...