ssue by producing an error "data
is essentially constant"
- which is the same error message found in t-test under similar conditions.
P.S. First time writing to this list. Read all the guides of posting, but sorry
in advance if I still missed any rules.
---
Karolis Koncevičius
Inde
en Infinities are on
both sides.
Regards,
Karolis Koncevičius.
On 2019-12-07 23:18, Karolis Koncevičius wrote:
Thank you for a fast response. Nice to see this mailing list being so
alive.
Regarding Inf issue: I agree with your assessment that Inf should not
be removed. The code gave me an impres
n Thu, 12 Dec 2019 17:20:47 +0100 writes:
Karolis Koncevičius
on Mon, 9 Dec 2019 23:43:36 +0200 writes:
>> So I tried adding Infinity support for all cases. And it
>> is (as could be expected) more complicated than I
>> thought.
> "Of course !"
is reached that the behavioiur has to be modified.
Kind regards,
Karolis Koncevičius.
---
Index: wilcox.test.R
===
--- wilcox.test.R (revision 77540)
+++ wilcox.test.R (working copy)
@@ -42,7 +42,7 @@
,3,2)-c(3,2,1))
[1] 1
unique(c(0.4,0.3,0.2)-c(0.3,0.2,0.1))
[1] 0.100033307 0.099977796 0.15551
On 2019-12-07 1:55 p.m., Karolis Koncevičius wrote:
Hello,
Writing to share some things I've found about wilcox.test() that seem a
a bit inconsistent.
1. Inf
and guidelines about issues 3 and 4 as well.
On 2019-12-07 21:59, Martin Maechler wrote:
Karolis Koncevičius
on Sat, 7 Dec 2019 20:55:36 +0200 writes:
> Hello,
> Writing to share some things I've found about wilcox.test() that seem a
> a bit inconsistent.
> 1. Inf values are
Hello,
I recently stumbled on an unusual behaviour of any() and all() and have
been adviced from StackOverflow to share it here [1].
df1 <- data.frame(A=TRUE, B=FALSE)
df2 <- data.frame(A=1, B=0)
> any(df1)
Error in FUN(X[[i]], ...):
only defined on a data frame with
Hello,
I also want to report 2 missed cases of stringsAsFactors=TRUE in base:
1. grid.expand() still uses hard stringsAsFactors=TRUE in its arguments.
2. as.data.frame.table() also keeps factors after conversion from table.
Duncan Murdoch
on Sun, 12 Apr 2020 08:57:14 -0400 writes:
>
Hello,
Today I was investigating ks.test() with two numerical arguments (x and y) and
was left a bit confused about the policy behind handling ties.
I might be missing something, so sorry in advance, but here is what confuses me:
The documentation states: "The presence of ties always generates
p to pass for
‘@‘ by adding ‘\\@‘ to regexp.
Please note that this now is not dependant on using or not using roxygen2
KK.
> On Apr 29, 2023, at 12:53 AM, Karolis Koncevičius
> wrote:
>
> Thank you for such a quick reply, Gabriel,
>
> I am not too familiar with the package tools, so cann
in
tools:::.S3_method_markup_regexp
> On Apr 28, 2023, at 10:34 PM, Karolis Koncevičius
> wrote:
>
> I was building a package that uses the new generic @ and kept having errors
> with “roxygen2” documentation. “roxygen2” generated NAMESPACE added
> `@.newclass` as a newly
I was building a package that uses the new generic @ and kept having errors
with “roxygen2” documentation. “roxygen2” generated NAMESPACE added
`@.newclass` as a newly exported function, not as a S3method.
At first I thought this must be a bug in roxygen2 and they lag behind the new
I don't know and/or am not privy to.
>
> Best,
> ~G
>
> On Fri, Apr 28, 2023 at 1:49 PM Karolis Koncevičius
> mailto:karolis.koncevic...@gmail.com>> wrote:
>> This issue might go deeper - I was not successful in passing R CMD checks
>> for the usage files
Hello Kurt,
With r84341 it now works on my side.
Warm regards,
Karolis K.
> On Apr 29, 2023, at 1:24 PM, Kurt Hornik wrote:
>
>>>>>> Karolis Koncevičius writes:
>
> Can you pls try again with r84341 or later?
>
> Best
> -k
>
>> A more concre
But this might require a more detailed investigation. For example I just
noticed that even with the patch `@` is still not listed in .S3_methods_table().
KK.
> On Apr 29, 2023, at 4:44 PM, Karolis Koncevičius
> wrote:
>
> Hello Kurt,
>
> With r84341 it now works on
Ah, you are correct, my bad and apologies. I forgot that table is only for
available methods, not for available generics.
KK.
> On Apr 30, 2023, at 4:49 PM, Kurt Hornik wrote:
>
>>>>>> Karolis Koncevičius writes:
>
>> But this might require a more deta
Hello,
I have stumbled upon a few cases where the behaviour of naming and subsetting
in matrices seems unintuitive.
All those look related so wanted to put everything in one message.
1. Why row/col selection by names with NAs is not allowed?
x <- setNames(1:10, letters[1:10])
X <-
Thank you for such a quick reply, here are some points that I think might have
been missed:
> I would state the question the other way : why are NAs integer indices
> allowed?
> In my experience, they are sometimes useful but they often delay the
> detection of bugs. However, due to backward
18 matches
Mail list logo
