-
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
cTRAP #906
Comments
Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
|
A reviewer has been assigned to your package. Learn what to expect IMPORTANT: Please read the instructions for setting |
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: "ERROR". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: cc87e27 Fix issue in Windows 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: "ABNORMAL". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: ccbfada Change mode depending on downloading a compressed ... |
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". Please see the build report for more details. |
Hello @vobencha, I have now fixed all issues with the package, but I am having trouble with running R CMD check within 5 minutes. The problem is that many examples/tests make use of data that is downloaded on demand. I asked the question at bioc-devel, to which Lori Shepherd replied to check BiocFileCache. Still, wouldn't this make the build fail since it has to download everything the first time to create the cache? |
Received a valid push; starting a build. Commits are: 0c232ca Avoid testing function to improve speed when runni... |
Received a valid push; starting a build. Commits are: 598419e Avoid testing function to improve speed when runni... |
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: "ERROR". 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". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 5c8c972 Avoid testing function to improve speed when runni... |
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: "ERROR". Please see the build report for more details. |
Hi @nuno-agostinho , I'd recommend creating small sample data files for the man pages and vignette. Put them in cTRAP/data/ or cTRAP/inst/extdata. Documentation on what type of file goes where is here: Once this is done you can load the file with system.file() or data() - there is no need to create your own function, loadInternalData(). This solution assumes you're downloading data in man pages or vignette, not internally with your package functions. The package functions should avoid downloading on the fly - they will be broken when the user has no internet access. Valerie |
We have until Oct 24th if you want this in Bioc 3.8: Otherwise the package will only be available in devel (Bioc 3.9) until the Spring 2019 release. |
Received a valid push; starting a build. Commits are: 009a160 Use smaller datasets for examples and vignettes |
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: "ERROR". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 2a306e0 Fix errors in R CMD 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: "ERROR". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: afef174 Add more runnable examples |
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". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 6257e75 Use smaller example datasets for faster R CMD chec... |
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 Please see the build report for more details. |
@nuno-agostinho If the package is ready for re-review please articulate what changes were made wrt |
Hey @vobencha, as per the comparison between commit 5c8c972 and the current master (commit 6257e75), the following changes were made:
Bug fixes, copy-editing and minor changes
|
Excellent. Thanks for making the changes. Just a few things left:
We have until COB Oct 24 to get this in Bioc 3.8. These last issues shouldn't take much time - we should be able to make it. Thanks. |
Hey @vobencha, thank you for the quick reply. I would like to make the following comments on your points:
Do man pages for internal functions also need examples? Regarding exported functions with no runnable examples, there are 3:
The vignette (previously named CTRAP: tutorial) will be renamed to cTRAP: differential expression comparison with cellular perturbations. |
Runable examples are only needed on man pages of exported functions. WRT the download functions, I agree you don't want to download during the nightly builds. You could put a code chunk there and wrap in
Re: vignette name, I was specifically thinking of the R code file name. Currently the filename is tutorial.Rmd. |
I will replace the
I will rename the vignette to As you suggested in your previous comment, I will also remove the |
Received a valid push; starting a build. Commits are: 2611ec8 Minor changes - Update vignette title - Fix docum... |
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 Please see the build report for more details. |
Looks good! Thanks. |
Your package has been accepted. It will be added to the 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/nuno-agostinho.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/ 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 https://bioconductor.org/packages/cTRAP 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]'
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 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 essential aspects of Bioconductor software
management, including:
months, for bug fixes.
(optionally via GitHub).
For help with submitting your package, please subscribe and post questions
to the bioc-devel mailing list.
The text was updated successfully, but these errors were encountered: