Skip to content
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

tidySpatialExperiment #3130

Closed
10 tasks done
william-hutchison opened this issue Sep 1, 2023 · 59 comments
Closed
10 tasks done

tidySpatialExperiment #3130

william-hutchison opened this issue Sep 1, 2023 · 59 comments
Assignees
Labels
3a. accepted will be ingested into Bioconductor daily builder for distribution

Comments

@william-hutchison
Copy link

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 Bioconductor Package Naming Policy and acknowledge
    Bioconductor may retain use of package name.

  • 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 Bioconductor code of conduct and
    agree to abide by it.

I am familiar with the essential aspects of Bioconductor software
management, including:

  • The 'devel' branch for new packages and features.
  • The stable 'release' branch, made available every six
    months, for bug fixes.
  • Bioconductor version control using Git
    (optionally via GitHub).

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.

@bioc-issue-bot
Copy link
Collaborator

Hi @william-hutchison

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:

Type: Package
Package: tidySpatialExperiment
Title: Brings SpatialExperiment to the tidyverse 
Version: 0.99.0
Authors@R: c(
    person("William", "Hutchison", email = "[email protected]", role = c("aut", "cre")),
    person("Stefano", "Mangiola", email = "[email protected]", role = "aut")
  )
Description: tidySpatialExperiment is an adapter that abstracts the SpatialExperiment container 
    in the form of a tibble and allows data manipulation, plotting and nesting using functions from
    the tidyverse ecosystem.
License: GPL-3
Depends:
    R (>= 4.3.0),
    SingleCellExperiment,
    SpatialExperiment,
    tidySingleCellExperiment,
Imports:
    ttservice,
    SummarizedExperiment,
    BiocGenerics,
    dplyr,
    tibble,
    tidyr,
    ggplot2,
    plotly,
    magrittr,
    rlang,
    purrr,
    lifecycle,
    methods,
    utils,
    S4Vectors,
    tidyselect,
    ellipsis,
    vctrs,
    pillar,
    stringr,
    cli,
    fansi,
    Matrix,
    pkgconfig
Suggests:
    BiocStyle,
    testthat,
    knitr,
    markdown,
    SingleCellSignalR,
    SingleR,
    scater,
    scran,
    tidyHeatmap,
    igraph,
    GGally,
    uwot,
    celldex,
    dittoSeq,
    EnsDb.Hsapiens.v86,
    cowplot, 
    microbenchmark
VignetteBuilder: 
    knitr
Biarch: true
biocViews: AssayDomain, Infrastructure, RNASeq, DifferentialExpression, GeneExpression, Normalization, Clustering, QualityControl, Sequencing
Encoding: UTF-8
LazyData: true
RoxygenNote: 7.2.3
Roxygen: list(markdown = TRUE)
URL: https://github.com/william-hutchison/tidySpatialExperiment
BugReports: https://github.com/william-hutchison/tidySpatialExperiment/issues

@bioc-issue-bot bioc-issue-bot added the 1. awaiting moderation submitted and waiting clearance to access resources label Sep 1, 2023
@vjcitn vjcitn added the pre-check passed pre-review performed and ready to be added to git label Sep 13, 2023
@vjcitn
Copy link
Collaborator

vjcitn commented Sep 13, 2023

you need DropletUtils in Suggests, or R_CHECK_SUGGESTS_ONLY will lead to error

@bioc-issue-bot
Copy link
Collaborator

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

@bioc-issue-bot bioc-issue-bot added pre-review on bioconductor git and access to on demand build but not assigned reviewer until build report clean and removed 1. awaiting moderation submitted and waiting clearance to access resources pre-check passed pre-review performed and ready to be added to git labels Sep 14, 2023
@bioc-issue-bot
Copy link
Collaborator

Dear Package contributor,

This is the automated single package builder at bioconductor.org.

Your package has been built on the Bioconductor Build System.

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 Bioconductor Build
System:
macOS 12.6.5 Monterey: tidySpatialExperiment_0.99.0.tar.gz
Linux (Ubuntu 22.04.2 LTS): tidySpatialExperiment_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
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@lshep lshep added the 2. review in progress assign a reviewer and a more thorough review of package code and documentation taking place label Sep 14, 2023
@bioc-issue-bot
Copy link
Collaborator

A reviewer has been assigned to your package for an indepth review.
Please respond accordingly to any further comments from the reviewer.

@bioc-issue-bot bioc-issue-bot removed the pre-review on bioconductor git and access to on demand build but not assigned reviewer until build report clean label Sep 14, 2023
@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: 23f040541eae9be46730e92f8dee4e84f01b34d5

@bioc-issue-bot
Copy link
Collaborator

Dear Package contributor,

This is the automated single package builder at bioconductor.org.

Your package has been built on the Bioconductor Build System.

On one or more platforms, the build results were: "WARNINGS".
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 Bioconductor Build
System:
macOS 12.6.5 Monterey: tidySpatialExperiment_0.99.1.tar.gz
Linux (Ubuntu 22.04.2 LTS): tidySpatialExperiment_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
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: 5733e3b28587ac9662c4aee13ce6c6734fb2e125

@bioc-issue-bot
Copy link
Collaborator

Dear Package contributor,

This is the automated single package builder at bioconductor.org.

Your package has been built on the Bioconductor Build System.

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 Bioconductor Build
System:
Linux (Ubuntu 22.04.2 LTS): tidySpatialExperiment_0.99.2.tar.gz
macOS 12.6.5 Monterey: tidySpatialExperiment_0.99.2.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
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@william-hutchison
Copy link
Author

william-hutchison commented Sep 19, 2023

Hello, thank you for your feedback. I have addressed all warnings and errors produced during the automated test process. Let me know if you have any further suggestions

@hpages
Copy link
Contributor

hpages commented Sep 28, 2023

Thanks @william-hutchison. Please consider addressing the following NOTEs:

R CMD check NOTEs:

  1.  * checking dependencies in R code ... NOTE
     Packages in Depends field not imported from:
       ‘SpatialExperiment’ ‘tidySingleCellExperiment’
       These packages need to be imported from (in the NAMESPACE file)
       for when this namespace is loaded but not attached.
    
  2.  Consider adding
       importFrom("methods", "callNextMethod", "getMethod", "is")
     to your NAMESPACE file (and ensure that your DESCRIPTION Imports field
     contains 'methods').
    

    Note that for the above note we actually recommend to import the full methods namespace with import(methods) instead of the suggested selective import.

    Fixing the imports should get rid of most "no visible binding for global variable" and "no visible global function definition" messages. Any remaining one will need to be assessed to determine whether it's a false positive or not.

  3.  * checking Rd files ... NOTE
     prepare_Rd: group_by.Rd:70-72: Dropping empty section \seealso
    

BiocCheck() NOTEs:

  1.  * Checking for recommended biocViews...
         * NOTE: Consider adding these automatically suggested biocViews:
           Spatial, Transcriptomics, SingleCell, ImmunoOncology, DataImport
    

    Maybe not all the terms above are relevant but maybe some of them are?

  2.  * Checking vignette directory...
         * NOTE: 'sessionInfo' not found in vignette(s)
    
  3.  * Checking coding practice...
         * NOTE: Avoid using '=' for assignment and use '<-' instead
    

Let me know if you have any questions.

Thanks,
H.

@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: abe6e276e93b10ff68f94cf64f1030c4b74cad4c

@bioc-issue-bot
Copy link
Collaborator

Dear Package contributor,

This is the automated single package builder at bioconductor.org.

Your package has been built on the Bioconductor Build System.

On one or more platforms, the build results were: "ERROR, skipped".
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 Bioconductor Build
System:
ERROR before build products produced.

Links above active for 21 days.

Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@bioc-issue-bot bioc-issue-bot added ERROR and removed OK labels Sep 29, 2023
@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: 05b0a894b63e5033aa35b6776c39845a1db8c0df

@bioc-issue-bot
Copy link
Collaborator

Dear Package contributor,

This is the automated single package builder at bioconductor.org.

Your package has been built on the Bioconductor Build System.

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 Bioconductor Build
System:
Linux (Ubuntu 22.04.2 LTS): tidySpatialExperiment_0.99.4.tar.gz
macOS 12.6.5 Monterey: tidySpatialExperiment_0.99.4.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
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@william-hutchison
Copy link
Author

william-hutchison commented Jan 5, 2024

Hi @hpages, thank you for your feedback.

I had removed the plot_ly() generic from tidySummarizedExperiment in our development version but did not push these changes to Bioconductor. Sorry about that, I will address this now.

Kind regards,
William

@william-hutchison
Copy link
Author

Hi @hpages. The updated tidySummarizedExperiment has been pushed the devel branch of Bioconductor. Thanks again.

@hpages
Copy link
Contributor

hpages commented Jan 17, 2024

Great, thanks!

Last thing on the list: since in the end the plot_ly() generic is defined in the ttservice package, do you really need to list tidySummarizedExperiment in Depends? What is tidySummarizedExperiment used for in tidySpatialExperiment?

If you do need to depend on tidySummarizedExperiment, then make sure to import the package in your NAMESPACE like you did for tidySingleCellExperiment. This issue is actually reported by R CMD check:

* checking dependencies in R code ... NOTE
Package in Depends field not imported from: ‘tidySummarizedExperiment’
  These packages need to be imported from (in the NAMESPACE file)
  for when this namespace is loaded but not attached.

If you don't need to depend on tidySummarizedExperiment then remove it from Depends.

Maybe the same applies to tidySingleCellExperiment? Do you really need to depend on it?

Thanks again,
H.

@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: f04ba04b09eaf91519ec6dd3b3d2ff88022e67f7

@bioc-issue-bot
Copy link
Collaborator

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: "skipped, 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:
ERROR before build products produced.

Links above active for 21 days.

Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@bioc-issue-bot bioc-issue-bot added ERROR and removed OK labels Jan 17, 2024
@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: b6fd6bf220ecea2b49a6646e72bea3f380f226c1

@bioc-issue-bot
Copy link
Collaborator

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: "skipped, 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:
ERROR before build products produced.

Links above active for 21 days.

Remember: if you submitted your package after July 7th, 2020,
when making changes to your repository push to
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: 7d76d7947d5fb1bbb04d6d84a099a2a399c94d49

@bioc-issue-bot
Copy link
Collaborator

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: "skipped, 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 22.04.2 LTS): tidySpatialExperiment_0.99.15.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
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: 68c204b4f8382d2e6d9caabdf5d276cd69272674

@bioc-issue-bot
Copy link
Collaborator

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: "skipped, 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 22.04.2 LTS): tidySpatialExperiment_0.99.17.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
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@william-hutchison
Copy link
Author

Hi @hpages, thank you for your suggestions.

I have moved tidySummarizedExperiment to Suggests. I believe tidySingleCellExperiment should remain in Depends to attach functions which are not exported by tidySpatialExperiment and are instead called directly from tidySingleCellExperiment e.g count().

Unfortunately I am now encountering an error with the macOS build:

ERROR: dependency SpatialExperiment is not available for package tidySpatialExperiment

All works well on Ubuntu and I am not sure what could be causing this, as SpatialExperiment has always been listed in Depends. I will continue to investigate, but let me know if you have any ideas. Maybe it could be a problem with the build process?

Thanks again

@hpages
Copy link
Contributor

hpages commented Jan 19, 2024

Maybe it was just bad timing. We updated R to the latest R-devel on all our devel build machines a couple of days ago. It could be that the SPB got triggered before all the BioC packages got reinstalled on merida1. Can you please trigger a new build by bumping the version again? Thanks

@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: 96365815bb3f5b9b0b7a4874693d8f82a3bca1fe

@bioc-issue-bot
Copy link
Collaborator

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: "WARNINGS".
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:
macOS 12.7.1 Monterey: tidySpatialExperiment_0.99.18.tar.gz
Linux (Ubuntu 22.04.2 LTS): tidySpatialExperiment_0.99.18.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
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@hpages
Copy link
Contributor

hpages commented Jan 20, 2024

Thanks. Let's ignore the warning on merida1. R CMD check took a little bit more than 10 min there (11 minutes 43.62 seconds), not a big deal.

3 minor things left and the package will be good to go:

  1. This R CMD build note:
* checking for empty or unneeded directories
Omitted LazyData from DESCRIPTION

(just remove the LazyData: false line)

  1. This R CMD check note:
* checking Rd line widths ... NOTE
Rd file 'rectangle.Rd':
  \examples lines wider than 100 characters:
         mutate(in_rectangle = rectangle(array_col, array_row, center = c(50, 50), height = 20, width = 10))
  1. This R CMD BiocCheck note:
* Checking coding practice...
    * NOTE: Avoid using '=' for assignment and use '<-' instead

Almost there.

Thanks again.

@bioc-issue-bot
Copy link
Collaborator

Received a valid push on git.bioconductor.org; starting a build for commit id: 17747da50095e662e483dbafc5dbf2e5711dfc1f

@bioc-issue-bot
Copy link
Collaborator

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: "WARNINGS".
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:
macOS 12.7.1 Monterey: tidySpatialExperiment_0.99.19.tar.gz
Linux (Ubuntu 22.04.2 LTS): tidySpatialExperiment_0.99.19.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
[email protected]:packages/tidySpatialExperiment to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.

@william-hutchison
Copy link
Author

Hi @hpages, I have addressed the three notes you raised. Thank you for helping me improve tidySpatialExperiment.

@hpages
Copy link
Contributor

hpages commented Jan 22, 2024

Great, thanks!

@hpages hpages added 3a. accepted will be ingested into Bioconductor daily builder for distribution and removed 2. review in progress assign a reviewer and a more thorough review of package code and documentation taking place WARNINGS labels Jan 22, 2024
@bioc-issue-bot
Copy link
Collaborator

Your package has been accepted. It will be added to the
Bioconductor nightly builds.

Thank you for contributing to Bioconductor!

Reviewers for Bioconductor packages are volunteers from the Bioconductor
community. If you are interested in becoming a Bioconductor package
reviewer, please see Reviewers Expectations.

@lshep
Copy link
Contributor

lshep commented Jan 26, 2024

The default branch of your GitHub repository has been added to Bioconductor's
git repository as branch devel.

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/william-hutchison.keys is not empty), then no further steps are required. Otherwise, do the following:

  1. Add an SSH key to your github account
  2. Submit your SSH key to Bioconductor

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 BiocManager::install("tidySpatialExperiment"). The package 'landing page' will be created at

https://bioconductor.org/packages/tidySpatialExperiment

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.

@lshep lshep closed this as completed Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3a. accepted will be ingested into Bioconductor daily builder for distribution
Projects
None yet
Development

No branches or pull requests

6 participants