Open shazanfar opened 2 months ago
Hi @shazanfar
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: SpatialFeatures
Title: Entropy-based subcellular and supercellular features for molecule-resolved spatial omics datasets
Version: 0.99.0
Authors@R: c(
person("Shila", "Ghazanfar", email = "shazanfar@gmail.com",
role = c("aut", "cre", "ctb"),comment = c(ORCID = "0000-0001-7861-6997")),
person("Guan", "Gui", role = "ctb")
)
Description: This package uses molecule-level information to extract new
cell-level features as an alternative to simply calculating gene counts. By
using four categories, sub-sector, super-sector, super-sector and
super-concentric segmentations of cells, SpatialFeatures then uses entropy
as a metric to arrive at a cell-by-gene level feature. Overall, this means
that we can extract more nuanced information from molecule-resolved spatial
gene expression for further downstream analysis with SingleCellExperiment.
License: GPL-2
Encoding: UTF-8
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.3.2
Depends: R (>= 4.4.0),
MoleculeExperiment,
SingleCellExperiment,
dplyr,
purrr,
parallel
Imports:
terra,
rlang
Suggests:
knitr,
ggplot2,
BiocStyle
VignetteBuilder: knitr
biocViews: Spatial, GeneExpression
URL: https://sydneybiox.github.io/SpatialFeatures/
BugReports: https://github.com/sydneybiox/SpatialFeatures/issues
Your package has been added to git.bioconductor.org to continue the pre-review process. A build report will be posted shortly. Please fix any ERROR and WARNING in the build report before a reviewer is assigned or provide a justification on why you feel the ERROR or WARNING should be granted an exception.
IMPORTANT: Please read this documentation for setting up remotes to push to git.bioconductor.org. All changes should be pushed to git.bioconductor.org moving forward. It is required to push a version bump to git.bioconductor.org to trigger a new build report.
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 the Bioconductor Single Package Builder.
On one or more platforms, the build results were: "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.
The following are build products from R CMD build on the Single Package Builder: Linux (Ubuntu 24.04.1 LTS): SpatialFeatures_0.99.0.tar.gz
Links above 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/SpatialFeatures
to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Received a valid push on git.bioconductor.org; starting a build for commit id: ca193f7b5d125718d31ff84faf65652111e6c9d9
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on the Bioconductor Single Package Builder.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
The following are build products from R CMD build on the Single Package Builder: Linux (Ubuntu 24.04.1 LTS): SpatialFeatures_0.99.1.tar.gz
Links above 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/SpatialFeatures
to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
A reviewer has been assigned to your package for an indepth review. Please respond accordingly to any further comments from the reviewer.
BiocManager::install()
.example_me
.?SpatialFeatures
).BiocStyle::Biocpkg(".")
(or similar for packages hosted on CRAN or GitHub).spatialFeatures()
lists the segmentations its using, but these are not explained (and are not obvious to interpret, to me at least...); consider briefly explaining these in both in R doc and the vignette.sapply()
and use vapply()
instead.me
with 0 checks on class/validity of that input; please add something of that sort as to avoid weird failure downstream.data.frame
s etc.).featureTypes
is passed to match.arg()
with a set of valid options provided in the function definition, but EntropyMatrix
is missing this.The vignette ends (just before 'Finish') with #> DataFrame with 178 rows and 0 columns
-- intended?
Hi @HelenaLC and @vjcitn thanks for your comments, it's taking me a while to get through these points as the student leading this project has graduated and has limited time. My apologies and will get back to you very soon, Best wishes, Shila
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.