Hi,
I have submitted my package scMerge to Bioconductor’s GitHub Issue page. The
only warning that I am receiving now tells me the R CMD check took more than 5
minutes. I am not sure how can I shorten this time as a number of the checks
are taking much longer time than my local computers. Even
Got it, thanks for the tip! I've pushed a fix that should resolve this but I
have another question.
The only way I could get check.Renviron to load was to either
1. explicitly load the file in R with readRenviron("~/check.Renviron")
2. manually set the R ENV variable with
Preferably the public API would be camel case for consistency with
other Bioconductor APIs (at least the core ones). It's not a huge deal
though.
On Tue, Feb 26, 2019 at 8:12 AM Turaga, Nitesh
wrote:
>
> As long as it’s consistent, you can use another style. Consistency helps
> reviewers read
The ERROR your package is experiencing has to do with conditional length
greater than 1. We did send you an email indicating this entitled
"Bioconductor Package ERROR" that had the following information:
In a continued effort to better code, there have been efforts to identify
problematic
lintr can be configured to use camelCase.
On Tue, Feb 26, 2019 at 11:12 AM Turaga, Nitesh <
nitesh.tur...@roswellpark.org> wrote:
> As long as it’s consistent, you can use another style. Consistency helps
> reviewers read the code easily.
>
> Most people generally use “camelCase" or “snake_case"
As long as it’s consistent, you can use another style. Consistency helps
reviewers read the code easily.
Most people generally use “camelCase" or “snake_case" for variable names and
function names. But keep in mind that class names need to be “CamelCase" as
that is the R style of doing
Hi All,
I maintain the GenVisR package which is currently failing on the devel
branch. I can see it has something to do with the test cases however the
error message is not clear, I don't get a line number for which test
case has failed or any other indication to that effect. Normally this
Hi all,
I'm developing a package that to submit to Bioconductor and I've noticed
that the style guide suggests camelCasealternatingWords which I find hard
to read and is different from other style guides and automated
style-checking I've seen (lintr, Hadley Wickam).
Is this an optional
Hi Vinh,
See in line replies,
On Feb 22, 2019, at 2:30 PM, Vinh Tran
mailto:t...@bio.uni-frankfurt.de>> wrote:
Dear all,
I am planning to submit a package into Bioconductor. But BiocCheck() gave a
warning about the size of the git pack file:
$warning
[1] "The following files are over 5MB
Yes the maintainer that is going to actively maintain the package (or
coordinate maintenance) should be listed in the Description and that maintainer
email MUST be registered at the mailing list and support site.
Lori Shepherd
Bioconductor Core Team
Roswell Park Cancer Institute
Department
Hi -
I am have been working with Dr. Valentine Dinu on the PoTRA package since last
year. I have the current version on the GitHub: Bioconductor-PoTRA.
His lab members work on developing and testing different versions of PoTRA so
those versions are kept on his lab page. Which is why I created
11 matches
Mail list logo
