Closed mrbakhsh closed 2 years ago
Hi @mrbakhsh
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: deepCE
Type: Package
Title: Inference of Interactome and Underying Protein Complexes from Co-fractionation MS Data via Deep Learning
Version: 0.99.0
Authors@R: c(
person("Matineh", "Rahmatbakhsh", ,"matinerb.94@gmail.com",c("aut","trl","cre")),
person("Mohan", "Babu", ,"mohan.babu@uregina.ca", c("led")),
person("Alla", "Gagarinova", ,"alla.gagarinova@usask.ca", c("led")))
Description: Co-fractionation mass spectrometry (CF-MS) has emerged as a powerful approach
for cell-wide identification of protein complexes that performs nearly all
biological processes and cellular activities. While computational tools based
on traditional machine learning is widely applied to analyze protein complexes,
it remains unclear if it is the most suitable choice for analyzing CF/MS
dataset. Here, we introduce deepCE, a R/Bioconductor package that employs deep
learning approaches for automated scoring of co-fractionation mass spectrometry
(CF-MS) and sophisticated clustering procedure for network inference of
underlying complexes.
Depends:
R (>= 4.1),
keras
Imports:
dplyr,
tidyr,
igraph,
ggplot2,
pROC,
PRROC,
RcppAlgos,
purrr,
tibble,
stringr,
data.table,
magrittr,
DiffCorr,
MSnbase,
stats,
grDevices,
utils
License: MIT + file LICENSE
Encoding: UTF-8
URL: https://github.com/mrbakhsh/deepCE
BugReports: https://github.com/mrbakhsh/deepCE/issues
VignetteBuilder: knitr
Suggests:
ptw,
infotheo,
reshape2,
fmsb,
knitr,
rmarkdown,
BiocStyle,
gprofiler2,
fgsea,
lsa,
WGCNA,
plyr,
proxy,
fdrtool,
BiocGenerics,
RUnit
SystemRequirement: tensorflow
biocViews:
Proteomics,
SystemsBiology,
NetworkInference,
Network,
Clustering,
MassSpectrometry
RoxygenNote: 7.1.2
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". 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/deepCE
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: 8cc4e652831f2ec6e2066b994ba078417b771919
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: "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. 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/deepCE
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: af69812eeb0ccb0bcf62b9120a9e16947e007471
Received a valid push on git.bioconductor.org; starting a build for commit id: 26d194e1cf3434354f5f2962c068d636f8ce9873
we are experiencing some issues with the newly added windows builder that is prevent the new build report from being posted. We are working on a remedy. We appreciate your patience and understanding.
Hi @lshep, thank you for letting me know. No worries
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: "WARNINGS, 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. 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/deepCE
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: fe98b11068cfe774c885f92f12eeed4d18fd6687
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". 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/deepCE
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: 3958dc936d7ba528800fae4f4a31f2a8d6bd58b2
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". 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/deepCE
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: b34d838b12f831578e63aa2991906d46ea5b3d0a
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". 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/deepCE
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: b34d838b12f831578e63aa2991906d46ea5b3d0a
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". 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/deepCE
to trigger a new build.
A quick tutorial for setting up remotes and pushing to upstream can be found here.
Hi @mrbakhsh
You seem to have closed the issue. Is there a reason?
Even though you have errors on the build machine, you can still fix them and make sure they pass. Once it is error-free, I can review the package.
Hi @nturaga,
Thank you for the message. Actually, we are in the process of writing the manuscript for the package and we thought that it is a bit early to make it public. I will try to submit it later this year again. Thank you
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.