Dear R-devel,
Is there anything that we can do to make output of those call more
consistent? So the first one will return `c(1L, 2L)` rather than
`1:2`. Note that it is not related to compact integer sequence
introduced by altrep, it is reproducible on R 3.1.0 as well.
substitute(v+x,
Thank you Lionel for comprehensive explanation. I think that rotating
AST in base R is not a good way to go, it would probably complicate
the code heavily.
Best,
Jan Gorecki
On Tue, Mar 17, 2020 at 4:49 PM Lionel Henry wrote:
>
> Hi Jan,
>
> In the lisp code you provide the operators are parsed
Hi Bioc team,
I am the maintainer of the package /waddR/.
We have had built issues on the active branch recently, due a dependency
being unavailable. After pushing a patch, the issues were resolved on
the devel branch.
Is it possible to merge these critical changes (version 1.1.4) to the
Please see the top portion of this page
http://bioconductor.org/developers/how-to/troubleshoot-build-report/. Updates
are not instantaneous; it can take 24-48 hours to appear, and will only appear
on the landing page if the build and check completed without Error.
Get Outlook for
Hi BioC-devel,
I am the author of the Bioconductor package APAlyzer (
https://bioconductor.org/packages/release/bioc/html/APAlyzer.html). We are
trying to push our updated package (version 1.1.1) to Bioconductor.
However, the git tutorial seems doesn't work in my case, here's what I've
done:
$
Good day,
I am not sure how to fix my package properly, even with the good example. A
link to the specific part of my function is
https://github.com/DarioS/ClassifyR/blob/e35899caceb401691990136387a517f4c3b57d5e/R/runTests.R#L567
and the example in the help page of runTestsEasyHard function
Hi BioC-devel,
I spent some time yesterday getting my Windows laptop ready to debug a
Windows OS-only issue in regionReport (bioc-release 3.10), but
ultimately I couldn't reproduce it. Since the error seems to be some
type of cache, I bumped the version number but it still failed today
and it
Thanks very much for the response. Can you recommend a way to do password
recovery? I no longer have access to the registered email address, and I'm
afraid that I registered long enough ago that I don't have the password
that I used.
On Tue, Mar 17, 2020 at 2:05 PM Turaga, Nitesh <
You'll have to activate your account first,
https://git.bioconductor.org/BiocCredentials/account_activation/
> On Mar 17, 2020, at 5:11 PM, ni41435_ca wrote:
>
> The SIM package is registered to mboetze...@hotmail.com.
>
> You can change the email on BiocCredentials app yourself.
>
>
The SIM package is registered to mboetze...@hotmail.com.
You can change the email on BiocCredentials app yourself.
Best,
Nitesh
> On Mar 17, 2020, at 11:52 AM, r.mene...@nki.nl wrote:
>
> l.s.
>
>
> I cannot seem to be able to activate my account on the bioconductor git. I
> get a message
Interesting. 'Kruskal Wallis' gets 5.68M google hits, 'Kruskall
Wallis' gets 432K ...
Within CRAN packages, sos::findFn("kruskal") gets 408 hits,
=sos::findFn("kruskall") gets 15 hits. (Some of those may be like the
use of 'euclidian' in stats::dist() to intentionally match misspellings
Hi,
There are a couple of things you'd have to do,
1. In the BiocCredentials app, you'd have to change your email address
registered. And update your SSH keys if needed, add your personal Github ID as
well.
2. In the DESCRIPTION file of the package, you'd have to change your email
address to
Further to my earlier email,
I understand that my package has been archived since my last version on CRAN
(1.1.0) had among its dependencies a package that has been archived.
Now my question:
How can I bring my package (actually the new version 1.1.1 that I’m trying to
check) back to life
Hello,
After checking my package with win builder, I got 1 note that I seem to not
fully understand:
CRAN repository db overrides:
X-CRAN-Comment: Archived on 2020-03-17 as depends on archived package
'spatialEco'.
Do you have any suggestion?
There is not reference to that package in my
The question is a bit abstract for me to understand and it might be better to
point to actual code in a git repository or similar...
Inside a package, something like
fun = function(x, y, ...) {
c(x, y, length(as.list(...)))
}
user_visible <- function(x, ...) {
y = 1
Good day,
Thanks for the examples which demonstrate the issue. Do you have other
recommendations if, inside the loop, another function in the package is being
called and the variable being passed is the ellipsis? There are only a couple
of variables which might be provided by the user
Using --with-pcre1 to configure the latest R 4.0 (revision 77988) on an
Ubuntu 14.04.5 LTS system gives me the following error:
...
checking if lzma version >= 5.0.3... yes
checking for pcre2-config... no
checking for pcre_fullinfo in -lpcre... yes
checking pcre.h usability... yes
checking
However, notice that if it is the guy from the Kruskal-Wallis test (William K.,
1919--2005), the "Kruskall" is in fact misspelt. It might be someone else, of
course...
-pd
> On 17 Mar 2020, at 18:24 , Duncan Murdoch wrote:
>
> I believe it is also acceptable to explain in your submission
Dirk,
> Octave had this already in the 1990s, see documentation for 'popen2' here:
thanks. unix that had since the 1970s... :)
cheers, Greg
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Hi,
I recently received error messages for 2 packages. As a worst-case-scenario,
it is acceptable if the sRAP package had to be removed. However, I need to
resolve the issue for the COHCAP package.
This is odd because I don’t think I have updated either package in the last
year or so. In
I'd like to change the email address associated with my
Bioconductor account, and also update the ownership of my packages to my
personal Github account (I originally registered both of these with my
employer, and I have since left the company). Could you please direct me to
documentation that
I believe it is also acceptable to explain in your submission message
that the misspelled words are all proper names. As far as I know,
misspellings are not enough of a problem to cause an automatic
rejection, so a human being will be making a judgment about the note.
Duncan Murdoch
On
Simon,
> FWIW if you're on unix, you can use named pipes (fifos) for that:
i've always wondered what named pipes actually were. thanks!
cheers, Greg
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Gabor, thanks. yes, managing the two-way communication is always a bit
error-prone, as it depends on the input/output characteristics of the
two ends -- they either match, or deadlock. it's too bad if polling is
always *required* -- i'd think sometimes a programmer would be happy
blocking,
l.s.
I cannot seem to be able to activate my account on the bioconductor git. I get
a message saying my email address (the same one on the package help file) is
not associated with a maintainer of a Bioconductor package. The email address
is write simply is
r.xavierdemene...@vumc.nl
as
You can single quote them to avoid them being spell checked, e.g. ...
using methods of 'Kruskall' and 'Brainerd'. This is a common and
accepted practice.
This is hinted at in "Writing R Extensions" (e.g. help.start());
The mandatory ‘Description’ field should give a comprehensive
description of
Hello,
I'm glad that it worked.
Two things:
1. Please, click reply all to keep this threaded.
2. The question should have belonged to r-h...@r-project.org, not to
r-devel@r-project.org.
Rui Barradas
Às 07:10 de 17/03/20, Moshe Olshansky escreveu:
It works, thank you!
On Tuesday, 17 March
Hello,
I am checking a package of mine, and I got only 1 note regarding possibly
misspelled words in the DESCRIPTION.
The issue I am facing is that those 6 words are not actually misspelled, being
either first or last names of individuals (actually, statistician; e.g.,
Kruskall, Brainerd).
Hi r-package-devel,
CRAN asked me to correct some errors so I'm currently in the process of
updating/ resubmitting my package and ran into an error connected to one of my
dependencies.
The thing is that the problem only occurs during the r-devel checks because of
a newer package version of
Windows uses separate processes that do not share memory (SnowParam()), whereas
linux / mac by default use forked processes that share the original memory
(MulticoreParam()). So
> y = 1
> param = MulticoreParam()
> res = bplapply(1:2, function(x) y, BPPARAM=param)
works because the function
Hi Jan,
In the lisp code you provide the operators are parsed as simple
symbols in a pairlist. In the R snippet, they are parsed as
left-associative binary operators of equal precedence. If you unquote
a call in the right-hand side, you're artificially bypassing the
left-associativity of these
Good day,
I have a loop in a function of my R package which by default uses bpparam() to
set the framework used for parallelisation. On Windows, I see the error
Error: BiocParallel errors
element index: 1, 2, 3, 4, 5, 6, ...
first error: object 'selParams' not found
This error does not
Crime?
(Macavity, Macavity, ..., and when you reach the scene of crime
Macavity's not there...)
I suspect your data objects are like Macavity, they're not there.
I found this in the R Internals 1.17.
Lazy-load databases are loaded into the exports for a package, but not
into the namespace
Hello,
The problem seems to be that A is a matrix. The following solves the error.
# create A and b as in your code then run
A <- as.data.frame(A)
df1 <- cbind(A, b)
reg <- lm(b ~ ., df1)
# etc
Hope this helps,
Rui Barradas
Às 04:36 de 17/03/20, Moshe Olshansky via R-devel escreveu:
34 matches
Mail list logo
