Closed lmyint closed 6 years ago
Hi @lmyint
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: mpra
Version: 0.99.0
Title: Analyze massively parallel reporter assays
Description: Tools to analyze & visualize massively parallel report assays (MPRA).
Authors@R: c(
person("Leslie", "Myint", role = c("cre", "aut"), email = "lmyint1@jhu.edu"),
person(c("Kasper", "D."), "Hansen", role = "aut"))
Depends:
R (>= 3.4.0),
methods,
BiocGenerics,
SummarizedExperiment,
limma
Suggests:
BiocStyle,
knitr,
rmarkdown,
RUnit
Imports:
S4Vectors,
scales,
stats,
graphics,
statmod
Collate:
mpra_set.R
utils.R
fit.R
VignetteBuilder: knitr
License: Artistic-2.0
URL: https://github.com/hansenlab/mpra
BugReports: https://github.com/hansenlab/mpra/issues
biocViews: Software, GeneRegulation, Sequencing, FunctionalGenomics
Your package has been approved for building. Your package is now submitted to our queue.
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.
Congratulations! The package built without errors or warnings on all platforms.
Please see the following build report for more details:
http://bioconductor.org/spb_reports/mpra_buildreport_20171004111006.html
Thanks for taking a look, Michael. Which functions were you referring to? The only place where we have specific processing for the cited publication (Inoue) is in inst/scripts
where we create the example data. Otherwise the functions that we export are related to general purpose analysis for any experiment. This is predicated on users to creating the MPRASet
object themselves though as we explain in the first section of the vignette. We have set it up this way because data from these experiments often come in a series of text files with no prescribed formatting, columns, etc.
Sorry, I meant to post that on a different issue but now I have no idea which one it was, because there are so many in play. I'll delete my comment.
Sorry I meant to post these brief comments earlier; your package looks really good, if you can make the changes outlined below in the next few days I will try to add it in time for the release at the end of October.
DESCRIPTION
vignettes
R
fit.R:8 use match.arg(model_type)
for validation
generally: spend more time validating inputs, especially to top-level functions, to avoid complicated or subtle errors later.
mpra_set.R:39 the show()
method seems to be a no-op, remove?
utils.R:3 using stop()
with sprintf()
is redundant; stop()
does the equivalent of paste()
internally.
man
good!
mpralm.Rd:14 provide some additional detail on need for agreement between dimensions of object
and design
.
Hi Martin, Thank you for the feedback. We have made the changes that you've suggested above, and bumped the version a few times, each without a triggered rebuild. With each push, I see that the webhook has a 404 error, so I'm not sure if something is down with the build system.
The specific changes we made include
match.arg(model_type)
for validationfit.R
show()
: we included information about the existence of barcode information, which is useful to users who want to know if their data may have been aggregated alreadystop()
design
to detail need for dimension agreementsReceived a valid push; starting a build. Commits are:
eee2a1b 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.
Congratulations! The package built without errors or warnings on all platforms.
Please see the following build report for more details:
http://bioconductor.org/spb_reports/mpra_buildreport_20171020131946.html
Your package has been accepted. It will be added to the Bioconductor Git repository and nightly builds. Additional information will be sent to the maintainer email address 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/lmyint.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 biocLite(\"mpra\")
. The package 'landing page' will be created at
https://bioconductor.org/packages/mpra
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.