Closed martijnvanattekum closed 8 months ago
Hi @martijnvanattekum
Thanks for submitting your package. We are taking a quick look at it and you will hear back from us soon.
The DESCRIPTION file for this package is:
Package: cleanse
Type: Package
Title: Tidyverse functions for SummarizedExperiment
Version: 0.99.0
Authors@R: person("Martijn", "van Attekum", email = "martijnvanattekum@gmail.com",
role = c("aut", "cre"),
comment=c(ORCID="0000-0002-5063-8489"))
Description: cleanse (clean summarized experiment) extends the SummarizedExperiments class to use tidyverse methods such as dplyr's select, filter, and mutate functions.
License: MIT + file LICENSE
Encoding: UTF-8
Imports:
stringr (>= 1.2),
readr (>= 1.3),
magrittr (>= 1.5),
tibble (>= 3.0),
tidyr (>= 1.0),
SummarizedExperiment (>= 1.1),
S4Vectors (>= 0.30),
stats (>= 4.0)
Depends:
dplyr (>= 1.0),
R (>= 4.3.0)
RoxygenNote: 7.2.3
Suggests:
knitr
VignetteBuilder: knitr
biocViews: Sequencing, Transcriptomics, GeneExpression
URL: https://github.com/martijnvanattekum/cleanse
BugReports: https://github.com/martijnvanattekum/cleanse/issues
Thanks for this submission. Would you please have a look at https://github.com/tidyomics/tidyomicsWorkshopBioc2023 and consider joining the tidygenomics slack channel https://community-bioc.slack.com/archives/CEQD45CHK ... I believe there is a significant relationship between your project and the work developing there.
Thank you for your reply. I am familiar with the tidySummarizedExperiment package. The main difference is that it strictly uses tidy (long format) data, whereas cleanse stays closer to the original se dimensions (wide format). Particularly aggregate operations and arithmetic (also contained in cleanse) functions are easier/safer to perform on wide format data. As an example, randomly sampling columns (se %>% sample_slice(col, n=10)
in cleanse) is not easy/possible to do in tidySummarizedExperiment.
I therefore think my package can be considered an alternative approach compared to tidySummarizedExperiment, and I don't see an immediate solution to integrate both approaches into one package.
When published, I could note this difference in the readme, and join the tidyTranscriptomics community to ensure that there is no overlap between our packages.
A reviewer has been assigned to your package. Learn what to expect during the review process.
IMPORTANT: Please read this documentation for setting up remotes to push to git.bioconductor.org. It is required to push a version bump to git.bioconductor.org to trigger a new build.
Bioconductor utilized your github ssh-keys for git.bioconductor.org access. To manage keys and future access you may want to active your Bioconductor Git Credentials Account
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on the Bioconductor Build System.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
The following are build products from R CMD build on the Bioconductor Build System: Linux (Ubuntu 22.04.2 LTS): cleanse_0.99.0.tar.gz macOS 12.6.5 Monterey: cleanse_0.99.0.tar.gz
Links above active for 21 days.
Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
git@git.bioconductor.org:packages/cleanse
to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Hi Martijn, @martijnvanattekum
Thank you for your submission. Please see the review below. Best, Marcel
tidySummarizedExperiment
and / or providing solely
the function(s) that convert the data to tidy (wide) format.tibble
.axis
. Imports
, is is not
necessary.SummarizedExperiment
(as implemented) is the right direction.%>%
and use the native |>
SummarizedExperiment
into the tidy data class.SummarizedExperiment
versions of the data.tidySummarizedExperiment
implementation and consider depending on
their interface.Hi Martijn, @martijnvanattekum Any updates on the response to the review? Otherwise, we will close the issue due to inactivity. Best, Marcel
This issue is being closed because there has been no progress for an extended period of time. You may reopen the issue when you have the time to actively participate in the review / submission process. Please also keep in mind that a package accepted to Bioconductor requires a commitment on your part to ongoing maintenance.
Thank you for your interest in Bioconductor.
Update the following URL to point to the GitHub repository of the package you wish to submit to Bioconductor
Confirm the following by editing each check box to '[x]'
[x] I understand that by submitting my package to Bioconductor, the package source and all review commentary are visible to the general public.
[x] I have read the Bioconductor Package Submission instructions. My package is consistent with the Bioconductor Package Guidelines.
[x] I understand Bioconductor Package Naming Policy and acknowledge Bioconductor may retain use of package name.
[x] I understand that a minimum requirement for package acceptance is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. Passing these checks does not result in automatic acceptance. The package will then undergo a formal review and recommendations for acceptance regarding other Bioconductor standards will be addressed.
[x] My package addresses statistical or bioinformatic issues related to the analysis and comprehension of high throughput genomic data.
[x] I am committed to the long-term maintenance of my package. This includes monitoring the support site for issues that users may have, subscribing to the bioc-devel mailing list to stay aware of developments in the Bioconductor community, responding promptly to requests for updates from the Core team in response to changes in R or underlying software.
[x] I am familiar with the Bioconductor code of conduct and agree to abide by it.
I am familiar with the essential aspects of Bioconductor software management, including:
For questions/help about the submission process, including questions about the output of the automatic reports generated by the SPB (Single Package Builder), please use the #package-submission channel of our Community Slack. Follow the link on the home page of the Bioconductor website to sign up.