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
YAPSA #71
Comments
Hi @huebschm Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
|
Your package has been approved for building. Your package is IMPORTANT: Please read the instructions for setting |
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". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160725155701.html |
We only start builds when the
to
If you did not intend to start a build, you don't need to |
Received a valid push; starting a build. Commits are: d3d422e Now with version bump |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160726143645.html |
Received a valid push; starting a build. Commits are: 8d750bc second revision Bioconductor: remove YAPSA.html |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160727093349.html |
Received a valid push; starting a build. Commits are: 5fc893d subscribed to Bioc-devel mailing list |
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, skipped, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160727102405.html |
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, skipped, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160727111256.html |
@hpages moscato1 CHECK output:
Looking at the output of the build of other packages, e.g. Is there anything that can be done to overcome this? |
Hi Daniel, YASPA has been transferred to me and I'll be doing the review. I wanted to make sure you saw Martin's response to your questions here https://stat.ethz.ch/pipermail/bioc-devel/2016-July/009570.html Valerie |
Dear Valeria,
This worked out, so comparing to the report under |
I don't understand what you mean by 'this worked out'. You have 2 choices:
Valerie |
Dear Valerie, |
Hi, |
Hi, the maintainer of limSolve didn't reply. Therefore we were looking for an alternative. It seems like limSolve uses the package lsei, and for the functions we need lsei might be sufficient. What I don't know yet is if lsei builds on windows, but we will try that out. |
Received a valid push; starting a build. Commits are: 36f97f9 replace limSolve dependency by lsei |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160812161544.html |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160812181144.html |
Received a valid push; starting a build. Commits are: 0ccccff changed test in LCD_SMC from matrix to data frame |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160812212020.html |
Received a valid push; starting a build. Commits are: 9c6253b reformatted test_LCD |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160813060738.html |
Received a valid push; starting a build. Commits are: efc6651 further adaptions on test LCD_SMC |
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". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160813074353.html |
Dear Valerie, |
Yes, that's good, thanks. I'm looking at it now and should have comments for you by tomorrow. |
Great job with the vignette and code organization. Comments and suggestions below. (1) number of exported functions and have over 100 man pages: In general, the number of exported objects should be >= the number of man pages. Everything that is exported needs a man page but if a function is not exported it does not need a man page. Is it essential the user have access to all these functions? If some (many?) are for internal use only it would be a much cleaner design to not export (and not document) these functions. Please explain. (2) support VRAnges Several functions take as input a data.frame of chromosome name, position, alt, ref etc. which is a natural representation for VRanges. As you probably know, VRanges is a commonly used class for variants and supporting this would make it easy for users with data already in VRanges to use your functions. For functions that operate on this type of data.frame please add support for VRanges. For example, in trellis_rainfall_plot.Rd the 'in_rainfall_dat' argument can be either a data.frame or VRanges. I'm sure I've missed a few but it looks like these functions support this type of data.frame and should also support VRanges: (3) Please format your code to max 80 characters wide. (4) non-evaluated man pages Please explain why these are wrapped in \dontrun: ~/proj/git/software/YAPSA/man >grep dont * (5) vignette
Let me know if you have questions. Valerie |
We only start builds when the
to
If you did not intend to start a build, you don't need to |
Dear Valerie, |
Received a valid push; starting a build. Commits are: 197fe57 last changes for code review |
Dear Valerie, (1) number of exported functions:
(2) support VRAnges
(3) Please format your code to max 80 characters wide.
(4) non-evaluated man pages
(5) vignette
Thank you very much for your comments and suggestions, best Daniel. |
Dear Valerie, Received a valid push; starting a build. Commits are: 197fe57 last changes for code review was sent out. Could this be related to the fact that by increasing the version number I reached 0.99.10 by now, i.e. two digits after the last separator? Also by mistake I had closed the issue and reopened it right again. Thank you for your help, best Daniel. |
Thanks for making the changes and documenting what you did. I'm not sure why the SPB didn't complete - I'll check with Lori. The 'z' portion of the 'x.y.z' version can go as high as you want; there is no restriction on that. More than likely it was related to the closing of the issue. Once we get a clean build/check I'll approve the package. Valerie |
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". Please see the following build report for more details: http://bioconductor.org/spb_reports/YAPSA_buildreport_20160822104316.html |
Dear Valerie, |
Yes, looks good. You'll get an email from Martin within the next week with svn credentials and next steps. Thanks again for putting in the extra work to improve the package. |
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]'
the package source and all review commentary are visible to the
general public.
instructions. My package is consistent with the Bioconductor
Package Guidelines.
to the analysis and comprehension of high throughput genomic data.
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:
months, for bug fixes.
(optionally via GitHub).
For help with submitting your package, please subscribe and post questions
to the bioc-devel mailing list.
The text was updated successfully, but these errors were encountered: