Closed hubentu closed 5 years ago
Hi @hubentu
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: Rcwl
Title: Wrap Command Tools and Pipelines Using CWL
Version: 0.99.8
Authors@R: person("Qiang", "Hu", email = "qiang.hu@roswellpark.org", role = c("aut", "cre"))
Description: The package can be a simple and user-friendly way to manage command line tools and build data analysis pipelines in R using Common Workflow Language (CWL).
Depends: R (>= 3.6), yaml, methods, S4Vectors, batchtools, DiagrammeR, reticulate
Imports: utils, stats, BiocParallel
License: GPL
Encoding: UTF-8
LazyData: true
Suggests: testthat,
knitr,
rmarkdown
VignetteBuilder: knitr
RoxygenNote: 6.1.1
biocViews: Software, WorkflowStep
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: "skipped, UNSUPPORTED, 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.
On one or more platforms, the build results were: "WARNINGS, skipped, UNSUPPORTED, 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.
@hpages @lshep This package requires the python module(s) cwltool
.
Received a valid push; starting a build. Commits are:
fd99d3b add SystemRequirements
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: "skipped, ERROR, UNSUPPORTED, 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.
So as a general comment - We feel like you shouldn't be changing or writing to a users system in the vignette or examples/tests. You should include instructions of what the user needs to do to set up to use the package and run the code assuming that this set up has been done (ie. there should be no system install or upgrades for the user )
Received a valid push; starting a build. Commits are:
e86c8ba remove scripts to install cwltool
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: "skipped, ERROR, UNSUPPORTED, 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.
Hi @lshep , I have removed the scripts to install the cwltool and give an installation URL instead. Thanks!
Thank you. Please see initial review below.
[ ] (optional) I recommend the vignette be Rcwl.Rmd rather than user guide as it is more intuitive for an R users to do vignette("Rcwl") rather than vignette("user_guide") to open the vignette.
[ ] All output in vignette should be shown and written to tempdir() or tempfiles() and not on a users system. When I'm running the commands all output is saved to current directory. You hid the global option for this in the vignette so while its true the builder should respect this, if a user is working through the code blindly it will be to their working directory - as happened with me and I polluted your package directory with output.txt and random file names like b87c26e2605a9b297621cf046edb678d7dcb9a8 which seems to be writing the output of runCWL.
cat 9b87c26e2605a9b297621cf046edb678d7dcb9a8
-A a b c -B=d -B=e -B=f -C=g,h,i
And I end up with many more as I run through all your examples manually.
[ ] Where is the WARNING coming from? Why are these different when I run interactively? Is this expected?
> readLines(tres$output)
[1] "WARNING: ignoring environment value of R_HOME"
[2] "[1] 4 2 1 9 5"
> readLines(r7$output)
[1] "WARNING: ignoring environment value of R_HOME"
[2] "[1] 6 9 10 1 3"
[http://www.commonwl.org]().
The same with this:
[https://www.commonwl.org/v1.0/CommandLineTool.html#CWLType]()
generally looks pretty good. The following are general statements that I saw throughout multiple .R files:
[ ] I would shorten the cat
statements in the show
methods where applicable
i.e
cat("class:", class(object), "\n")
cat("cwlClass:", cwlClass(object), "\n")
cat("cwlVersion:", cwlVersion(object), "\n")
doesn't need separate statements
cat("class:", class(object), "\n",
"cwlClass:", cwlClass(object), "\n",
"cwlVersion:", cwlVersion(object), "\n")
- [ ] There is WARNING in the build report about library/require call
- [ ] There is a NOTE about sapply vs vapply that should be updated
- [ ] For what its worth there is an ifelse function that could be a cleaner syntax for single input
It takes the for ifelse(test_expression, x, y)
i.e
if(cwlClass(cwl) == "Workflow"){
ilist <- c(id = names(inputList)[i], inputList[[i]])
}else{
ilist <- inputList[[i]]
}
Could be written as
ilist <- ifelse((cwlClass(cwl) == "Workflow"), c(id = names(inputList)[i], inputList[[i]]), inputList[[i]])
Totally optional but I'm generally in favor of concise code.
- [ ] There are occassionally comment out code chunks that should be removed.
# Man
- [ ] I would expand the package documentation maybe have a seealso link to main
package function
<br>
<br>
<br>
When the above have been addressed please kick off a new build with a version bump and comment back here with response/how the code has been updated.
Thank you and I look forward to getting your package accepted into Bioconductor
~Lori
Hi @lshep ,
 Installation instructions added.
outdir
option.readLines
outputs. The warning was not shown when I run check in the bioconductor/devel_core2 container. It might be caused by the R environment set in Renviron via google.RcwlPipelines
. A new section of Resources was added to give more details about how this package could be used in practice.runFun
is used to assign Rcwl
functions and inputs to each computing nodes in cluster server via the BiocParallel
, so library(Rcwl)
is used in this function.seealso links added to main package man.
Thanks, Qiang
Received a valid push; starting a build. Commits are:
3b58fd8 bump version
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: "skipped, UNSUPPORTED, 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: "skipped, UNSUPPORTED, 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.
Sorry for the delay - I'm looking at the package and should have a review within the next day or two.
Received a valid push; starting a build. Commits are:
90f7140 Add cwltool version check
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: "skipped, UNSUPPORTED, 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.
I still would also add the Bioconductor installation instructions to the README.md
if (!requireNamespace("BiocManager", quietly = TRUE))
install.packages("BiocManager")
BiocManager::install("Rcwl")
But otherwise looks good.
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/hubentu.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("Rcwl")
. The package 'landing page' will be created at
https://bioconductor.org/packages/Rcwl
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.