Closed Aufiero closed 5 years ago
Hi @Aufiero
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: circRNAprofiler
Type: Package
Title: circRNAprofiler: An R-Based Computational Framework for the Downstream Analysis of Circular RNAs
Version: 0.1.1
Author: Simona Aufiero
Maintainer: Simona Aufiero <simo.aufiero@gmail.com>
Description: R-based computational framework for a comprehensive in silico
analysis of circRNAs. This computational framework allows to combine and
analyze circRNAs previously detected by multiple publicly available
annotation-based circRNA detection tools. It covers different aspects of
circRNAs analysis from differential expression analysis, evolutionary
conservation, biogenesis to functional analysis.
License: GPL-3
Encoding: UTF-8
LazyData: TRUE
biocViews: Annotation, StructuralPrediction, FunctionalPrediction, GenePrediction, GenomeAssembly
Depends:
R(>= 3.6.0),
gwascat
RoxygenNote: 6.1.1
Suggests:
testthat,
knitr,
roxygen2,
rmarkdown,
citr,
devtools,
gridExtra,
ggpubr,
VennDiagram,
BSgenome.Mmusculus.UCSC.mm9,
BSgenome.Hsapiens.UCSC.hg38,
BSgenome.Mmusculus.UCSC.mm10,
remotes,
Imports:
dplyr,
magrittr,
readr,
rtracklayer,
stringr,
Biostrings,
BSgenome,
stringi,
DESeq2,
edgeR,
GenomicRanges,
IRanges,
seqinr,
R.utils,
reshape2,
ggplot2,
utils,
rlang,
S4Vectors,
stats,
AnnotationHub,
GenomeInfoDb,
BSgenome.Hsapiens.UCSC.hg19
VignetteBuilder:
knitr
A reviewer has been assigned to your package. Learn what to expect during the review process.
IMPORTANT: Please read the instructions for setting up a push hook on your repository, or further changes to your repository will NOT trigger a new build.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "TIMEOUT". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Received a valid push; starting a build. Commits are:
4396a9c changes package version number from 0.1.1 to 0.99.... d8d13f6 Removed files.... 82d2ffa add .Rproj and .Rproj.user/ to git ignore d454c1f Delete circRNAprofiler.Rproj 147e30b added *.Rproj to gitignore 7be826b Added comment tag # to the code in the @examples ... 12e62b6 Merge branch 'develop'
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "TIMEOUT". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "TIMEOUT, WARNINGS". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "WARNINGS, ERROR". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
Hi @Aufiero
Thanks for submitting your package to Bioconductor. An official review will be given shortly (within 2 weeks of last successful build).
Cheers, Qian
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
Hi @Aufiero ,
Here is part of your package review. I will post the 2nd half soon. Please seek to address the issues listed, and comment back here with updates / questions.
Best, Qian
LazyData:
field: For packages that include data, we recommend not including LazyData: TRUE. This rarely proves to be a good thing. In our experience it only slows down the loading of packages with large data.BugReports:
field: It is encouraged to include the relevant links to Github for reporting Issues.URL:
field: This field directs users to source code repositories, additional help resources, etc; It is recommended to include the link here. initCircRNAprofiler.R
file.path()
instead of paste(sep="/")
here, so that it could automatically adjust the separator based on different OS.file.path()
to construct the file path instead of the paste0()
. Same applies to the ther get*Tamplate
functions. get*Tamplate()
functions? Maybe you meant Template
? checkProjectFolder.R
%in%
, an edge case maybe that the file has 2 or more columns named as id
, although not very likely, but you never know and may be helpful to test. So maybe just using colnames()=="id"
or adding ncol() == 1
to exclude the edge case. getBackSplicedJunctions.R
if (nrow(experiment))
and remove the >0
and it will work sufficiently here. file.path()
here for constructing a file path. filterCirc.R
if(nrow(experiment))
to avoid checking twice. General
data.frame
as output, you may consider using DataFrame
instead, which basically has the same characteristics as data.frame
and has a better show method. You can try using DataFrame(data.frame(letters, LETTERS))
and compare with an ordinary data.frame
to have a feel. the
from the sentence.
BiocManager::install("circRNAprofiler")
You can also download the development version on github using BiocManager
:
BiocManager::install("Aufiero/circRNAprofiler")
Thanks Qian, I addressed all of the issues, except for the following 2.
-About the use of DataFrame The show method is indeed better. I did a test with the getBackSplicedJunctions() and mergeBSJunctions() functions. The output of getBackSplicedJunctions() is the input of mergeBSJunctions(). For the getBackSplicedJunctions() I returned a DataFrame object instead of a data.frame. I gave the DataFrame object to mergeBSJunctions() and I got the following error:
Error in UseMethod("mutate") : no applicable method for 'mutate' applied to an object of class "c('DataFrame', 'DataTable', 'SimpleList', 'DataTable_OR_NULL', 'List', 'Vector', 'list_OR_List', 'Annotated')"
mutate is a method of dplyr package. It seems that it does not work on a DataFrame object. Since I use a lot the dplyr package in the functions of circRNAprofiler I would prefer to keep the object data.frame also because I do not know how many issues it may cause if I change it.
S
Received a valid push; starting a build. Commits are:
f0adb65 Version: 0.99.5 to Version 0.99.6 72ce702 updated vignettes fd5737e updated Readme 2b05592 updated man doc with describe field 55a9a70 used file.path() insted of paste. corrected typo: ... bbd1dc9 typo ab13509 Added ncol() 5559f15 updated roxygem doc and fix typo 4781571 updated roxygen doc, used file.path() insted of pa...
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "TIMEOUT, WARNINGS". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "TIMEOUT, WARNINGS". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "WARNINGS". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "WARNINGS". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "TIMEOUT". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
On one or more platforms, the build results were: "TIMEOUT, WARNINGS". This may mean there is a problem with the package that you need to fix. Or it may mean that there is a problem with the build system itself.
Please see the build report for more details.
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
Hi @Aufiero ,
Sorry for the delay of responding. I have just reviewed the rest of your package, here are the comments:
getDeseqRes.R
if (nrow(experiment))
only to avoid double checking..
for the non-exported, utility functions, such as
getEdgerResDF
and getDeseqResDF
. See here for details.For your question about using DataFrame
, you are fine to use the data.frame
to get the best interoperability with dplyr grammars.
Bioconductor usually recommends removing the whole lazyData
field from DESCRIPTION
file. Your problem of R CMD CHECK doesn't seem to be related to the lazyData
. But I'll try to reproduce to see if there is any other problem.
Best, Qian
Hi @Aufiero ,
I couldn't reproduce your error with R CMD CHECK
. Can you remove the lazyData: TRUE
field from your DESCRIPTION
file, and redo the check to see if the result will change?
Qian
Hi Qian,
-About lazyData: I removed the lazyData field from the DESCRIPTION file and I ran the R CMD check. This is the error that I get (see attached file) check.txt
-About the Prefix . for the non-exported functions: shall I rename for example getEdgerResDF to .getEdgerResDF, right? Except getEdgerResDF and getDeseqResDF there are also other non- exported functions in my package, shall I rename all of them using the prefix ''."?
Hi @Aufiero ,
For your 2nd question, yes. It would be a good practice in developing R packages, by prefixing "." for non-exported functions. Highly recommended to make updates for all cases.
For the other review points, if you find similar cases, just update them all, not restricted to those I mentioned.
For the 1st question, first, you need to correct your vignette .Rmd file, L356, into eval=TRUE
. Rerun the R CMD check
, you should see some other errors in examples, and test functions as listed below. Fix all until you get a clean report, let me know for any questions.
errors in example and test function, in getRegexPattern.R
script. the
circRNAprofiler::inpac
usage , what is it? getMirSite.R
: remove the #
comment signal for the example of getMiRsite()
.
You should never use setwd
in your scripts!!
dir <- system.file("tests", "testthat", "testdata", package = "circRNAprofiler")
system.file(dir, "gencodeVM16.gtf")
test_getMirSites.R
. But also update all other functions that including setwd()
. Qian
Hi Qian,
-I added prefix "." for non-exported functions -I removed the # comment signal for the example of getMiRsite() -R CMD check now ends with no error without the lazyData field from the DESCRIPTION file
-about setwd for my package to work the user needs to set the project folder as working directory. The project folder contains project files and the circRNA prediction results. The package circRNAprofiler assumes that the circRNA prediction results are put in specific subfolders of the project folder. The names of the files containing the circRNA prediction results are specified in a file named experiment.txt.
Since I can not use system.file to point to circRNA prediction results for the unit test I need to set testdata as working directory. Can use file.path with setwd? In this way it should be ok on different building machines. setwd(file.path(getwd(), "testdata"))
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
Hi @Aufiero ,
Since the check is OK, and the setwd
didn't trigger any building error, I'll let it pass. Thank you for the contribution to Bioconductor.
Cheers, Qian
Your package has been accepted. It will be added to the Bioconductor Git repository and nightly builds. Additional information will be posed to this issue in the next several days.
Thank you for contributing to Bioconductor!
The master branch of your GitHub repository has been added to Bioconductor's git repository.
To use the git.bioconductor.org repository, we need an 'ssh' key to associate with your github user name. If your GitHub account already has ssh public keys (https://github.com/Aufiero.keys is not empty), then no further steps are required. Otherwise, do the following:
See further instructions at
https://bioconductor.org/developers/how-to/git/
for working with this repository. See especially
https://bioconductor.org/developers/how-to/git/new-package-workflow/ https://bioconductor.org/developers/how-to/git/sync-existing-repositories/
to keep your GitHub and Bioconductor repositories in sync.
Your package will be included in the next nigthly 'devel' build (check-out from git at about 6 pm Eastern; build completion around 2pm Eastern the next day) at
https://bioconductor.org/checkResults/
(Builds sometimes fail, so ensure that the date stamps on the main landing page are consistent with the addition of your package). Once the package builds successfully, you package will be available for download in the 'Devel' version of Bioconductor using BiocManager::install("circRNAprofiler")
. The package 'landing page' will be created at
https://bioconductor.org/packages/circRNAprofiler
If you have any questions, please contact the bioc-devel mailing list (https://stat.ethz.ch/mailman/listinfo/bioc-devel); this issue will not be monitored further.
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 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.
I am familiar with the essential aspects of Bioconductor software management, including:
For help with submitting your package, please subscribe and post questions to the bioc-devel mailing list.