Closed seandavi closed 3 years ago
Hi @seandavi
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: sars2pack
Title: COVID-19 data resources and analysis tools
Description: On January 30, 2020, the World Health Organization declared
coronavirus disease 2019 (COVID-19) a Public Health Emergency of
International concern (PHEIC) and within six weeks had
characterized the outbreak as a pandemic. Compared to the 2003-2004
severe acute respiratory syndrome (SARS) PHEIC, the COVID-19
pandemic spreads more quickly and with a much higher death
toll. However, the current pandemic is occurring in a more digital
and interconnected world. Traditional public health organizations
as well as data-mature organizations not traditionally involved
directly in public health have rapidly developed digital disease
surveillance infrastructuree that provides nearly realtime epidemic
tracking data. These data resources have proven invaluable to
understanding disease spread, to drive non-pharmacologic
intervention (NPI), and, when combined with additional data
resources, to project impacts to communities and healthcare systems
around the world. Even as the urgency of the initial “hammer” of
the COVID-19 pandemic begins to abate, the need for timely, robust,
and granular datasets will inform business, policy, and even
personal decisions for months or even years to come. This package provides
documentation and access to highly-cited COVID-19 datasets and
secondary data that allow real-time analysis, visualization, and
interpretation of the state of COVID-19 at a community, national,
or international level. By exposing these resources easily to the
enormous community of data scientists using R, we hope to increase
value and accelarate reporting, analysis, and decision-making.
Version: 0.99.0
Date: 2020-12-23
Authors@R: c(person("Sean", "Davis", role = c("aut","cre"),
email = 'seandavi@gmail.com',
comment = c('ORCID'="0000-0002-8991-6458")),
person("John C", "Mallery", role = c("ctb")),
person("Kevin","Rue-Albrecht", role=c("ctb")),
person("Charles", "Morefield", role = c("ctb")),
person("Joe","Wasserman", role=c("ctb")),
person("VJ", "Carey", role = c("aut"), email='stvjc@channing.harvard.edu'))
Suggests:
knitr,
BiocStyle,
data.table,
testthat,
pkgdown,
DT,
tmap,
tigris,
tidycensus,
htmltools,
htmlwidgets,
plotly,
magick,
listviewer,
dbplyr,
rmarkdown,
geofacet,
zoo,
cowplot,
tsibble,
rcmdcheck,
sessioninfo,
covr,
timetk,
DBI,
RSQLite
Depends: R (>= 4.0.0), R0, sf
Imports: methods, utils, lubridate, magrittr, dplyr, countrycode,
openxlsx, tibble, jsonlite, httr, readr, BiocFileCache, readxl,
stringr, ggplot2, yaml, rlang, EpiEstim,
RSelenium, wdman, purrr, ape, tidyr
Url: https://seandavi.github.io/sars2pack, https://github.com/seandavi/sars2pack
BugReports: https://github.com/seandavi/sars2pack/issues/new
License: MIT + file LICENSE
LazyLoad: yes
LazyData: yes
VignetteBuilder: knitr
biocViews: TimeCourse,
DataImport,
ThirdPartyClient,
DataRepresentation,
Phylogenetics
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.1.1
Encoding: UTF-8
SystemRequirements:
libgdal: libgdal-dev (deb), libgdal-devel (rpm)
A reviewer has been assigned to your package. Learn what to expect during the review process.
IMPORTANT: Please read this documentation for setting up remotes to push to git.bioconductor.org. It is required to push a version bump to git.bioconductor.org to trigger a new build.
Bioconductor utilized your github ssh-keys for git.bioconductor.org access. To manage keys and future access you may want to active your Bioconductor Git Credentials Account
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, 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. This link will be active for 21 days.
Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
git@git.bioconductor.org:packages/sars2pack
to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Please adjust your package to not TIMEOUT before the review process will continue.
Hi, @lshep. I'm going to go ahead and close this. I could go the long-test route, but the only tests that are relevant are the long tests, so the project just isn't going to fit in the Bioconductor build process.
Sorry to have wasted your time!
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.
Note to reviewers: sars2pack is not really about genomics, but about COVID-19 data. I expect this will be of interest to the Bioconductor community, but if this is outside the scope of Bioconductor, I can go elsewhere.
[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.
[X] 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:
For help with submitting your package, please subscribe and post questions to the bioc-devel mailing list.