[R] Why does nlme::getVarCov not Work for nlme Models?

Hi, I was just trying to summarize an nlme model using `broom.mixed::tidy()`, and it doesn't give random effects or residual variability for nlme models. As I looked deeper, this appears to be related to the fact that `nlme::getVarCorr()` doesn't support nlme models for no reason that I can dis

[R] Cross validation multivariate kernel regression

Hi, This question is general- I have a data set of n observations, consisting of a single response variable y and p regressor variables.( n ~50, p~3 or 4). I am planning to implement Nadaraya-Watson regression model, with bandwidths optimized via cross-validation. For cross-validation, I will need

Re: [R] Problem comparing two strings

A version of this came up not long ago in a slightly different context (bug 17369: parse() doesn't honor unicode in NFD normalization). The basic issue is that there are different unicode normalizations (look it up...). Briefly, accented characters exist in two forms, one as a single code poin

Re: [R] Problem comparing two strings

On 18/11/2019 10:11 a.m., Björn Fisseler wrote: Hello, I'm struggling comparing two strings, which come from different data sets. This strings are identical: "Alexander Jäger" But when I compare these strings: string1 == string2 the result is FALSE. Looking at the raw bytes used to encode the

Re: [R] Problem comparing two strings

Thank you! That solved my problem! Best         Björn Am 18.11.19 um 16:34 schrieb Ivan Krylov: > On Mon, 18 Nov 2019 16:11:44 +0100 > "Björn Fisseler" wrote: > >> It's obviously the umlaut "ä" in this example which is encoded with >> two respectively three bytes. The question is how to change

Re: [R] Problem comparing two strings

On Mon, 18 Nov 2019 16:11:44 +0100 "Björn Fisseler" wrote: > It's obviously the umlaut "ä" in this example which is encoded with > two respectively three bytes. The question is how to change this? Welcome to the wonderful world of Unicode-related problems! It is, indeed, possible to represent th

[R] Problem comparing two strings

Hello, I'm struggling comparing two strings, which come from different data sets. This strings are identical: "Alexander Jäger" But when I compare these strings: string1 == string2 the result is FALSE. Looking at the raw bytes used to encode the strings, the results are different: string1: 41

Re: [R] Problems with lambda argument

Dear friend Duncan, Thank you for your kind reply, I appreciate the fact that you always try to help. I got the error fixed, to fix the problem, instead of setting lambda="auto", I did lambda=BoxCox.lambda(tsobject), not sure if this is equivalent to setting lambda="auto", but I guess is a workaro

Re: [R] Problems with lambda argument

On 18/11/2019 8:44 a.m., Paul Bernal wrote: Dear friends, Hope you are doing great. When setting the lambda = "auto" in the auto.arima function, I get an error message saying non-numeric argument to binary operator. I have performed several tests changing parameters and going through the other

[R] lambad and biasadj parameters in auto.arima and forecast functions

Dear friends, Hope you are doing great. I noticed that both the auto.arima and the forecast function share parameters, like for example lambda and biasadj. If I set this parameters = TRUE in function auto.arima, do I also have to specify them and set them = TRUE in the forecast function? Best reg

[R] Problems with lambda argument

Dear friends, Hope you are doing great. When setting the lambda = "auto" in the auto.arima function, I get an error message saying non-numeric argument to binary operator. I have performed several tests changing parameters and going through the other lines of code and as soon as I set lambda = "a