-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mulea #3328
Comments
Hi @stitam Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
|
Some comments: We have already submitted
I would rather not do this because then R CMD check will fail on oldrel-1 (ELTEbioinformatics/mulea#24). The package does not require R 4.3.0. (I have turned off GitHub workflows for the Bioconductor submission process)
I am registered to both the mailing list and the support forum. |
Your package has been added to git.bioconductor.org to continue the IMPORTANT: Please read this documentation for setting Bioconductor utilized your github ssh-keys for git.bioconductor.org |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. On one or more platforms, the build results were: "ERROR". Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
Please fix ERROR in build report before the package will more forward in review. |
Hi @lshep it seems I cannot interact with the upstream ( |
everything is fine on our end. Please see about that you should activate your account and then if need be add additional ssh keys |
Received a valid push on git.bioconductor.org; starting a build for commit id: 0417dfeadc43a7a1b52933236f2525e38af17be7 |
Thanks @lshep, my Bioconductor Git Credentials account was not activated. |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. On one or more platforms, the build results were: "WARNINGS". Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
Received a valid push on git.bioconductor.org; starting a build for commit id: 7514578d23c591d0ff75460cf5cad3b0d4a5e832 |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on the Bioconductor Single Package Builder. On one or more platforms, the build results were: "WARNINGS". Please see the build report for more details. The following are build products from R CMD build on the Single Package Builder: Links above active for 21 days. Remember: if you submitted your package after July 7th, 2020, |
A quick note about the warning: |
A reviewer has been assigned to your package for an indepth review. |
I have trialled the package and noted some issues to be addressed.
> library(S4Vectors)
> d <- DataFrame(x = 1:5)
> is(d, "data.frame")
FALSE Also, code uses parallel package instead of BiocParallel. For example,
# if there are duplicated Gene.symbols keep the first one only
geo2r_result_tab_filtered <- geo2r_result_tab %>%
# grouping by Gene.symbol to be able to filter
group_by(Gene.symbol) %>%
# keeping the first row for each Gene.symbol from rows with the same
# Gene.symbol
filter(row_number()==1) %>%
# ungrouping
ungroup() %>%
# arranging by logFC in descending order
arrange(desc(logFC)) %>%
select(Gene.symbol, logFC)
import(magrittr)
importFrom(magrittr,"%<>%")
importFrom(magrittr,"%>%")
create_random_db <- function() {
DB <- list()
for (cat_i in seq_len(10)) {
DB_cat_values <- c() Refer to Vectorize. |
Many thanks @DarioS for reviewing the package, we'll address these ASAP. It was unclear to us whether Bioconductor requires camel case or snake case is also accepted, we decided to go with snake case and only harmonised this for uer facing functions. Please advise, for a successful review 1. should we moveo to camel case? 2. should we use harmonise for internal functions as well? Regarding your observation on the namespace file: If there is complete import there is no need to include selective import as well, this is the issue, right? |
camelCase for user-facing functions is sufficient. Yes, import either completely or selectively, depending on how many functions. |
Thank you Bioconductor Team for all your work! It was not feasible for us to implement these changes so we decided to publish the package on CRAN instead of Bioconductor. The package has been released: https://cran.r-project.org/web/packages/mulea/index.html. |
Dear Bioconductor Team,
With this issue we would like to submit the
mulea
package.mulea
is a comprehensive overrepresentation and functional enrichment analyser R package which reads ontologies (gene and protein sets) in a standardised GMT (Gene Matrix Transposed) format.Kind regards,
Tamás
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]'
I understand that by submitting my package to Bioconductor,
the package source and all review commentary are visible to the
general public.
I have read the Bioconductor Package Submission
instructions. My package is consistent with the Bioconductor
Package Guidelines.
I understand Bioconductor Package Naming Policy and acknowledge
Bioconductor may retain use of package name.
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.
My package addresses statistical or bioinformatic issues related
to the analysis and comprehension of high throughput genomic data.
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.
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:
months, for bug fixes.
(optionally via GitHub).
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.
The text was updated successfully, but these errors were encountered: