bioc-issue-bot
commented
2 years ago Hi @CTrierMaansson
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: DNAfusion
Title: Identification of gene fusions using paired-end sequencing
Version: 0.99.0
biocViews: TargetedResequencing, Genetics, GeneFusionDetection, Sequencing
Authors@R:
c(person(given = "Christoffer Trier", family = "Maansson", , email = "ctm@clin.au.dk", role = c("aut", "cre"),
comment = c(ORCID = "0000-0002-3071-3437")),
person(given = "Emma Roger", family = "Andersen", , email = "201907412@post.au.dk", role = c("ctb", "rev")),
person(given = "Maiken Parm", family = "Ulhoi", , email = "maiken@oncology.au.dk", role = "dtc"),
person(given = "Peter", family = "Meldgaard", , email = "petemeld@rm.dk", role = "dtc"),
person(given = "Boe Sandahl", family = "Sorensen", , email = "b.sorensen@clin.au.dk", role = c("rev", "fnd")))
Description: Paired-end sequencing of cfDNA generated BAM files can be used as input to
discover EML4-ALK variants. This package was developed using position deduplicated BAM
files generated with the AVENIO Oncology Analysis Software. These files are made using
the AVENIO ctDNA surveillance kit and Illumina Nextseq 500 sequencing. This is a targeted
hybridization NGS approach and includes ALK-specific but not EML4-specific probes.
License: GPL-3
Encoding: UTF-8
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.2.1
Suggests:
knitr,
rmarkdown,
usethis,
devtools,
testthat,
BiocStyle,
sessioninfo
VignetteBuilder: knitr
Imports:
bamsignals,
GenomicRanges,
IRanges,
Rsamtools
Depends:
dplyr,
R (>= 4.2.0)
BugReports: https://github.com/CTrierMaansson/DNAfusion/issues
URL: https://github.com/CTrierMaansson/DNAfusion
vjcitn
CTrierMaansson
LiNk-NY
lshep
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 Bioconductor Package Naming Policy and acknowledge Bioconductor may retain use of package name.
[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.
[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 questions/help about the submission process, including questions about the output of the automatic reports generated by the SPB (Single Package Builder), please use the #package-submission channel of our Community Slack. Follow the link on the home page of the Bioconductor website to sign up.