Bioconductor / Contributions

Contribute Packages to Bioconductor
131 stars 33 forks source link

RGraphSpace: A lightweight package for representing large igraph objects in a normalized coordinate system. #3235

Closed castromaa closed 5 months ago

castromaa commented 7 months ago

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 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.

bioc-issue-bot commented 7 months ago

Hi @castromaa

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: RGraphSpace
Type: Package
Title: A lightweight package for representing large igraph objects in a normalized coordinate system
Version: 0.99.0
Authors@R: 
    c(person("Vinicius", "Chagas", role = "ctb"),
      person("Victor", "Apolonio", role = "ctb"),
      person("Mauro", "Castro", role = c("aut", "cre"),
    email = "mauro.a.castro@gmail.com",
    comment = c(ORCID = "0000-0003-4942-8131")))
Depends: R(>= 4.2), methods, igraph, ggplot2
Imports: grDevices, scales, grid
Suggests: knitr, rmarkdown, RUnit, BiocGenerics, BiocStyle, PathwaySpace, RedeR
Description: RGraphSpace is an R package that integrates igraph and ggplot2 graphics within spatial maps. RGraphSpace implements new geometric objects using ggplot2 protypes, customized for representing large igraph objects in a normalized coordinate system. By scaling shapes and graph elements, RGraphSpace can provide a framework for layered visualizations.
License: Artistic-2.0
biocViews: GraphAndNetwork, Network, NetworkEnrichment, Spatial
VignetteBuilder: knitr
URL: https://github.com/sysbiolab/RGraphSpace
Collate:
    gspaceChecks.R
    gspaceValidation.R
    gspaceSupplements.R
    gspaceMisc.R
    gspacePlots.R
    gspaceClasses.R
    gspaceGenerics.R
    gspaceMethods.R
Encoding: UTF-8
RoxygenNote: 7.2.3
lshep commented 6 months ago

PathwaySpace is not a package on CRAN or Bioconductor; Any package that is listed as a dependency must be on CRAN or Bioconductor. Please remove this dependency or ask the maintainers to submit their package.

castromaa commented 6 months ago

Thank you. I had overlooked the removal of "PathwaySpace" from the 'suggests' section. It has now been excluded. It's worth noting that this package is not utilized in any aspect of RGraphSpace; rather, the dependency relationship is the other way around. So, as PathwaySpace relies on RGraphSpace, we are planning to submit PathwaySpace following the evaluation of RGraphSpace by Bioconductor. Any other suggestions, please let us know.

lshep commented 6 months ago

When I run R CMD check there is also an issue with the tests; I believe you have a typo and only have GraphSpace instead of RGraphSpace in both your defined test and the runTests.R file. The unit test also seems rather trivial -- we would hope that more extensive testing of package internals would be reflected in the unit tests.

However, I will move this into our git system for official build reports from our machines to begin the next phase. Please correct any ERROR, Warning, or Notes that will appear in the report once it is posted.

castromaa commented 6 months ago

Thank you, Lori. You are correct, it was a typo from an old nomenclature. We included the "R" in the RGraphSpace name to avoid a potential conflicting name with a web tool in a related field. I'll fix this typo in the github package, thanks.

Regarding the unit tests, there are extensive checks inside the GraphSpace class constructor. I would be happy to include any suggestions during the next phase.

bioc-issue-bot commented 6 months ago

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 commented 6 months ago

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: macOS 12.7.1 Monterey: RGraphSpace_0.99.1.tar.gz Linux (Ubuntu 22.04.2 LTS): RGraphSpace_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/RGraphSpace to trigger a new build. A quick tutorial for setting up remotes and pushing to upstream can be found here.

bioc-issue-bot commented 6 months ago

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

bioc-issue-bot commented 6 months ago

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: macOS 12.7.1 Monterey: RGraphSpace_0.99.2.tar.gz Linux (Ubuntu 22.04.2 LTS): RGraphSpace_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 git@git.bioconductor.org:packages/RGraphSpace to trigger a new build. A quick tutorial for setting up remotes and pushing to upstream can be found here.

bioc-issue-bot commented 6 months ago

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

bioc-issue-bot commented 6 months ago

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: macOS 12.7.1 Monterey: RGraphSpace_0.99.3.tar.gz Linux (Ubuntu 22.04.2 LTS): RGraphSpace_0.99.3.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/RGraphSpace to trigger a new build. A quick tutorial for setting up remotes and pushing to upstream can be found here.

bioc-issue-bot commented 6 months ago

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

bioc-issue-bot commented 6 months ago

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: macOS 12.7.1 Monterey: RGraphSpace_0.99.4.tar.gz Linux (Ubuntu 22.04.2 LTS): RGraphSpace_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 git@git.bioconductor.org:packages/RGraphSpace to trigger a new build. A quick tutorial for setting up remotes and pushing to upstream can be found here.

bioc-issue-bot commented 6 months ago

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

bioc-issue-bot commented 6 months ago

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: macOS 12.7.1 Monterey: RGraphSpace_0.99.5.tar.gz Linux (Ubuntu 22.04.2 LTS): RGraphSpace_0.99.5.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/RGraphSpace to trigger a new build. A quick tutorial for setting up remotes and pushing to upstream can be found here.

bioc-issue-bot commented 6 months ago

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

bioc-issue-bot commented 6 months ago

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: macOS 12.7.1 Monterey: RGraphSpace_0.99.6.tar.gz Linux (Ubuntu 22.04.2 LTS): RGraphSpace_0.99.6.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/RGraphSpace to trigger a new build. A quick tutorial for setting up remotes and pushing to upstream can be found here.

bioc-issue-bot commented 6 months ago

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

bioc-issue-bot commented 6 months ago

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: macOS 12.7.1 Monterey: RGraphSpace_0.99.7.tar.gz Linux (Ubuntu 22.04.2 LTS): RGraphSpace_0.99.7.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/RGraphSpace to trigger a new build. A quick tutorial for setting up remotes and pushing to upstream can be found here.

castromaa commented 6 months ago

I've fixed almost all build report issues, but the following ones persist:

* ERROR: Maintainer must add package name to Watched Tags on the support site.

I couldn't figure out how to add RGraphSpace to the 'Watched Tags' list. Please, advise.

* NOTE: Consider shorter lines; 11 lines (1%) are > 80 characters long.

This node seems to refer to 11 lines in the package's vignette file (RGraphSpace.Rmd). Not sure how to implement this suggestion, as the .Rmd is formatted to generate an html vignette. I could break lines, but doing so might disrupt the alignment of the vignette paragraphs. Please, advise.

* NOTE: Consider multiples of 4 spaces for line indents; 13 lines (1%) are not.

I used the "styler" package to setup 4 spaces for line indents across all .R files. However, 13 lines persist in other files. They seem to refer to the .Rd documentation files, which are generated by roxygen2.

* NOTE: Provide 'BugReports' field(s) in DESCRIPTION

"BugReports" field indicates a particular web page for submitting bug reports. Could we designate this suggestion as the package's page on Bioconductor once it becomes available?

vjcitn commented 6 months ago

I've fixed almost all build report issues, but the following ones persist:

Here's how you do this. First, make an account at support.bioconductor.org. Then visit your profile. You will see something like this

findtags

Look towards the bottom to see a "Tags" link. Click on that and you will find a field where you can enter tags. Use the name of your package as one of your tags.

The rest of these are "NOTE"s and you can address them at your discretion. Except that the BugReports field should include the URL of the Issues page for your source github repo.

* NOTE: Provide 'BugReports' field(s) in DESCRIPTION

"BugReports" field indicates a particular web page for submitting bug reports. Could we designate this suggestion as the package's page on Bioconductor once it becomes available?

bioc-issue-bot commented 6 months ago

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

bioc-issue-bot commented 6 months ago

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: macOS 12.7.1 Monterey: RGraphSpace_0.99.8.tar.gz Linux (Ubuntu 22.04.2 LTS): RGraphSpace_0.99.8.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/RGraphSpace to trigger a new build. A quick tutorial for setting up remotes and pushing to upstream can be found here.

castromaa commented 6 months ago

Thank you for your support; it was greatly helpful. RGraphSpace passed all checks this time.

bioc-issue-bot commented 5 months ago

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

LiNk-NY commented 5 months ago

Hi Mauro, @castromaa

Thank you for your submission. Unfortunately, the package does not leverage any existing Bioconductor software. Please consider a submission to CRAN.

Best regards, Marcel

castromaa commented 5 months ago

Hi Marcel,

Thank you for taking the time to evaluate RGraphSpace. While CRAN is a good suggestion, could I ask you to reconsider Bioconductor? This package is intended to enhance the user experience with RedeR, a package we maintain on Bioconductor. RedeR is an interactive software for visualizing and manipulating nested networks. Currently, it lacks a user-friendly interface to R graphics, requiring users to perform all tasks in a Java interface. RGraphSpace will parse graph objects for RedeR using igraph syntax rules, enabling users to plot the same network in RedeR and ggplot2. As igraph is a very popular tool in network fields, we created RGraphSpace separated from RedeR, so other users (that may not know RedeR) could benefit from using RGraphSpace + igraph + ggplot2. It's worth noting that igraph itself lacks a straightforward interface for ggplot2. Therefore, we believe that this infrastructure could greatly benefit users interested in manipulating and visualizing networks. Please let us know any suggestions on how we could enhance RGraphSpace to align with Bioconductor's standards.

Sincerely,

Mauro

vjcitn commented 5 months ago

Thanks for this submission. I feel that this particular package needs more work to demonstrate its relevance to Bioconductor and genomic data science. The vignette is very abstract and deals only with a toy example. I was led to have a look at RedeR which is also very interesting but includes code like

gt3  <- subg(g=hs.inter, dat=ER.limma[ER.limma$degenes.t3!=0,], refcol=1)

which is valid, it works, but the user acceptability of this is somewhat questionable. If I understand it correctly, RGraphSpace would help end-users doing genomic data science to take advantage of RedeR's capabilities. I would ask that you build up the vignette to really sell the value of RedeR+RGraphSpace to those doing genomic data science. I would also propose that in doing this you take advantage of some Bioconductor resources for representing genomic data and networks. like ndexr for networks, and SummarizedExperiment or GSEABase for genomic data or gene sets as one might have for the "ER.limma" references above. I hope you can follow some of these suggestions as it will be beneficial to your users and to Bioconductor!

castromaa commented 5 months ago

Great, thank you Vince. I agree, the vignette is still abstract and contains only a toy example, primarily because we're unable to fully disclose a case study from a companion paper that is currently under revision. But I will expand the vignette to incorporate your suggestions, which I truly appreciate.

Can I ask another related advise? RGraphSpace is intended to be a lightweight interface for ggplot2, but not only for RedeR. The primary tool that motivated the implementation of RGraphSpace is called PathwaySpace, which we were planing to submit to Bioconductor after RGraphSpace. PathwaySpace is where we plan to showcase the usability of these new tools, particularly for the diffusion of gene signals in pathways, but this will require a normalized graph coordinate system provided by RGraphSpace.

As a brief overview, there are five main tools involved in the dependency design as we envision it: 1 - igraph: a popular tool, providing state-of-the-art graph methods, but lack good plotting capabilities. 2 - ggplot2: offers state-of-the-art plotting capabilities, but is not readily compatible with igraph data objects. 3 - RedeR: provide an interactive interface for igraph networks. 4 - RGraphSpace: will provide methods to plot igraph and RedeR networks in ggplot2. 5 - PathwaySpace: will provide methods for diffusion of gene signals, using all the others to visualize gene signals onto pathways and graphs.

Therefore, giving this dependency design, would it make sense to submit PathwaySpace now so that the current reviewer could assess all these tools side by side?

vjcitn commented 5 months ago

Thanks for the followup. It sounds like your software has a substantial generic component for network science, which would likely get good exposure through CRAN, and a possibly significant application space in genomic data science, which would be appropriate and useful for Bioconductor. My suggestion at this point would be to consider those packages that enhance ggplot2 and igraph as CRAN packages, and the packages that deal with gene signaling networks as Bioconductor packages, which specifically take advantage of existing tooling for networks and gene sets in Bioconductor.

Why propose CRAN for the more generic components? Because our reviewing energies and our capacity to support growing numbers of packages are finite and are approaching limits. We are trying to make changes to increase capacity and that effort of renovation is impacting our review and processing bandwidth. So when the review process comes up with "has no bioconductor interop" it is natural to check whether contributors are aware of the CRAN option, which may have real benefits in terms of exposure to non-genomics users.

vjcitn commented 5 months ago

Of note is that Bioconductor packages may formally Depend upon CRAN packages.

castromaa commented 5 months ago

Thanks for sharing these concerns. It all makes sense to me, and we can definitely proceed with releasing RGraphSpace as a CRAN package. I will move in this direction.

As for submitting PathwaySpace to Bioconductor, we may need to wait a while until RGraphSpace is available on CRAN. I'll close this issue, many thanks.