Closed zhangjunpeng411 closed 6 years ago
Hi @zhangjunpeng411
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: miRSM
Type: Package
Title: Inferring miRNA sponge modules by integrating expression data and miRNA-target binding information
Version: 0.99.0
Author: Junpeng Zhang
Maintainer: Junpeng Zhang <zhangjunpeng_411@yahoo.com>
Description: The package aims to identify miRNA sponge modules by integrating expression data and miRNA-target binding information.
It provides several functions to study miRNA sponge modules, including popular methods for inferring gene modules
(candidate miRNA sponge modules), and a function to identify miRNA sponge modules, as well as a function to conduct
functional analysis of miRNA sponge modules.
Depends: R (>= 3.4.3)
License: GPL-3
URL: <https://github.com/zhangjunpeng411/miRSM>
Encoding: UTF-8
LazyData: true
biocViews: GeneExpression, BiomedicalInformatics,
Clustering, GeneSetEnrichment, Microarray,
Software, GeneRegulation
RoxygenNote: 6.0.1
Imports: WGCNA,
flashClust,
dynamicTreeCut,
GFA,
igraph,
linkcomm,
MCL,
NMF,
biclust,
runibic,
iBBiG,
fabia,
BicARE,
isa2,
s4vd,
BiBitR,
rqubic,
Biobase,
varhandle,
PMA,
stats,
miRsponge,
Rcpp
Suggests:BiocStyle,
knitr,
rmarkdown,
testthat,
org.Hs.eg.db
VignetteBuilder: knitr
A reviewer has been assigned to your package. Learn what to expect during the review process.
IMPORTANT: Please read the instructions for setting up a push hook on your repository, or further changes to your repository will NOT trigger a new build.
please update the user-facing interface (argument and return values) to use a SummarizedExperiment and other standard objects instead of ad-hoc data representations.
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.
@mtmorgan Thanks for you advice.
Junpeng
Received a valid push; starting a build. Commits are:
bc3415c Add files via upload
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.
Received a valid push; starting a build. Commits are:
c852afc Add files via upload
Received a valid push; starting a build. Commits are:
60a7aef Add files via upload
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.
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.
Received a valid push; starting a build. Commits are:
64fc314 Add files via upload
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.
Received a valid push; starting a build. Commits are:
ada0e06 Add files via upload
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: "ABNORMAL". 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.
Received a valid push; starting a build. Commits are:
f8c7010 Add files via upload
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: "ABNORMAL". 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.
Received a valid push; starting a build. Commits are:
d08d58c Add files via upload
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". 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.
Received a valid push; starting a build. Commits are:
cf7222b Add files via upload
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: "ABNORMAL". 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.
Received a valid push; starting a build. Commits are:
767353d Add files via upload
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: "ABNORMAL". 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.
Received a valid push; starting a build. Commits are:
e4e81cd Add files via upload
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: "ABNORMAL". 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.
Received a valid push; starting a build. Commits are:
aef9494 Update
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: "ABNORMAL". 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.
Received a valid push; starting a build. Commits are:
046eaa5 Update
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: "ABNORMAL". 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.
Hi @lshep ,
How can I resolve the ABNORMAL status of the repository? I don't see anything particularly wrong in the build report, only the operating system is not showed in the OS/Arch field. In addition, only one operating system is runned.
Thanks and Regards, Junpeng
This was likely an issue on our end. I am rerunning the package now to generate the complete build report.
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". 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.
Received a valid push; starting a build. Commits are:
d2c038d Update
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.
Received a valid push; starting a build. Commits are:
698cbee Update
Dear Package contributor,
This is the automated single package builder at bioconductor.org.
Your package has been built on Linux, Mac, and Windows.
Congratulations! The package built without errors or warnings on all platforms.
Please see the build report for more details.
Please let me know when you are finished updating user-facing interface (argument and return values) as @mtmorgan suggested. When you are finished with this update I will give a more formal review of the package.
Hi @Ishep,
I have updated all functions by using a SummarizedExperiment object for arguments. Now, you can review it. Thanks for your hard work.
Regards, Junpeng
Sorry for the delayed response. Please see the following comments:
General:
README
Description:
NEWS:
CHANGES IN VERSION 0.99.8-0.99.14
-------------------------
Update miRSM.Rmd
CHANGES IN VERSION 0.99.4-0.99.7
-------------------------
Update runnable examples
would become
CHANGES IN VERSION 0.99.8-0.99.14
-------------------------
o Update miRSM.Rmd
CHANGES IN VERSION 0.99.4-0.99.7
-------------------------
o Update runnable examples
Vignette:
[ ] you only need to load the data once instead of repeatedly
data(ceRExp)
data(mRExp)
[ ] So running your examples module_GFA is an empty list - is this intended?
[ ] All output are lists of character vectors? It seems as list of Genes - please look into formatting output to a GSEAbase::GeneSet or GeneSetCollection object
[ ] Are the lengths of the lists going to be consistent? What do the different elements of the list mean? Some better explanation of the output would be helpful as well as maybe labelling the list elements.
[ ] It seems like there is extra whitespace in the coding sections of Identification of miRNA sponge modules and Functional analysis of miRNA sponge modules causing it to display weirdly
[ ] Your last code section is eval=FALSE why?
[ ] So these modules are meant to be run separatly depending on which is appropriate or desired?
inst/script:
Man files:
R Code: Internal ProNet functions -
[ ] So I see that ProNet is temporarily removed from CRAN which is why I assume you are inlcuding these functions here? Have you reached out to the ProNet package maintainer to see if they plan on maintaining the package and having it back on CRAN?
[ ] It seems like this section of code outputs the resutls of each function. Maybe create a helper function for it instead so that if there are every updates it only needs to be updated in one instance
ceR_Num <- lapply(seq_along(Modulegenes), function(i) length(which(Modulegenes[[i]] %in%
colnames(ceRExp))))
mR_Num <- lapply(seq_along(Modulegenes), function(i) length(which(Modulegenes[[i]] %in%
colnames(mRExp))))
index <- which(ceR_Num >= num.ModuleceRs & mR_Num >= num.ModulemRs)
CandidateModulegenes <- lapply(index, function(i) Modulegenes[[i]])
return(CandidateModulegenes)
Please address the above issues and push changes. When you are ready please comment back here and I will re-review. Thank you for you submission - I look forward to working with you to get your package accepted
Cheers,
Hi @lshep ,
Thanks for your comments.
Regards, Junpeng
Received a valid push; starting a build. Commits are:
f3f35bf Update
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". 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.
Received a valid push; starting a build. Commits are:
181d267 Update
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". 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.
Received a valid push; starting a build. Commits are:
1cd5101 Update
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". 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.
Received a valid push; starting a build. Commits are:
824e970 Update
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". 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.
Received a valid push; starting a build. Commits are:
ffb6615 Update
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". 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.
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 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.
I am familiar with the essential aspects of Bioconductor software management, including:
For help with submitting your package, please subscribe and post questions to the bioc-devel mailing list.