similar to: Problem when trying to install packages

Though Navigator may mess up any Rtools stuff because it handles the directory trees where packages and dependencies are located, does it not? If so, maybe just reinstall RStudio directly from its website to proceed. Just a guess obviously. Bert On Sat, Mar 16, 2024, 05:09 javad bayat <j.bayat194 at gmail.com> wrote: > Dear Rui; > Many thanks for your reply. I have installed Rtools

Dear all; I found a useful video on youtube that has explained how to install Rtools. I followed the instructions and the problem was solved. " Installing R version 4.0 + RTools 4.0 + RStudio For Data Science (#R #RTools #RStudio #DataScience) - YouTube <https://www.youtube.com/watch?v=h2IPWVXaUuU> " Sincerely On Sat, Mar 16, 2024 at 10:15?AM Bert Gunter <bgunter.4567 at

Hi i need use these 2 librarys? ( vctrs ) and ( ggplot2 ) , and the 2 librarys are installed in my Rstudio? RStudio Version 1.2.5033 ? 2009-2019 RStudio, Inc. "Orange Blossom" (330255dd, 2019-12-04) but i got all times thesse messages....please help-me...thanks lot of > library ( vctrs ) Error: package or namespace load failed for ?vctrs? in loadNamespace(i, c(lib.loc, .libPaths()),

Dear all, I have had some rather serious difficulties getting graphics and analysis packages to load in R on my new Ubuntu Install. The trouble seems to begin when attempting to install TMB. I have done a full purge of r-base r-base-dev and r-base-core and reinstalled the newest version of RStudio (not that this should matter). I'm not sure what to try next. many thanks! Brandon Z >

I think this is the fourth attempt to send this blessed message, so let's hope this gets through without any 'unprocessed' or 'ignored' in-lines on auto-reply. I wish to report to you some strange problems I'm experiencing with installing packages directly into my -R- 2.15.1 (there is an indirect solution, which I note below). First, here's some essential information:

>>>>> akshay kulkarni >>>>> on Wed, 31 May 2023 20:55:33 +0000 writes: > dear members, > I am using arfima() from forecast package to model a time > series. The following is the code: >> LYGH[[202]] > [1] 45.40 3.25 6.50 2.15 >> arfima(LYGH[[202]]) > Error in .fdcov(x, fdf$d, h, nar = nar, nma = nma,

dear members, I am using arfima() from forecast package to model a time series. The following is the code: > LYGH[[202]] [1] 45.40 3.25 6.50 2.15 > arfima(LYGH[[202]]) Error in .fdcov(x, fdf$d, h, nar = nar, nma = nma, hess = hess, fdf.work = fdf$w) : NA/NaN/Inf in foreign function call (arg 5) I tried viewing .fdcov() with the following code:

On 1/16/24 20:16, Dipterix Wang wrote: > Could you recommend any packages/functions that compute hash such that > the source references and sexpinfo_struct are ignored? Basically a > version of `serialize` that convert R objects to raw without storing > the ancillary source reference and sexpinfo. > I think most people would think of `digest` but that package uses >

Dear Martin, Sad that the bug is beyond your ken... Fortunately, the error happens only rarely...The length of LYGH was 719 and there were only two such errors..I will just replace them with NA and make do. By the by, what if I send LYGH as an attachment to your actual mail ( not the r-help mail)? Will it help? Can you then pinpoint the cause? Or should I raise a bug

dear members, I am using R to model stock prices but a slow "for" loop has stifled my research. I am using Rcpp to speed up my "for" loop. I am also using RcppEigen to implement block operations on xts objects..... how do I use RcppEigen? If I just load it by: > require(RcppEigen) it is not recognising the .block method in C++. If I include it inside

The problem: I would like to translate the Octave algorithm in griddata.m to R. Within the griddata algorithm calls are made to the Delaunay function. For the R translation I have found delaunayn within the "geometry" package and also the deldir package. Both do similar things but give slightly different results depending on the input. The question is, what is making the results for the

Many thanks Bert, now is ok, i did not know that "Namensraum" should mean a package Am So., 16. Apr. 2023 um 23:44 Uhr schrieb Bert Gunter < bgunter.4567 at gmail.com>: > So update the vctrs package to the latest version first before loading > R-tools (or the caret package, specifically)? > > -- Bert > > On Sun, Apr 16, 2023 at 1:57?PM G?bor Malomsoki >

Hi all, I wanted to share with you an experimental package that I?m currently working on: vctrs, <https://github.com/r-lib/vctrs>. The motivation for vctrs is to think deeply about the output ?type? of functions like `c()`, `ifelse()`, and `rbind()`, with an eye to implementing one strategy throughout the tidyverse (i.e. all the functions listed at

> > As Gabe mentioned (and you've explained about) the term "type" > > is really confusing here. As you know, the R internals are all > > about SEXPs, TYPEOF(), etc, and that's what the R level > > typeof(.) also returns. As you want to use something slightly > > different, it should be different naming, ideally something not > > existing yet

"The question is, what is making the results for the R packages different from each other?" There are literally thousands of R packages, contributed independently by thousands of people. There should be no expectation of consistency or for that matter, "correctness", among them. Caveat emptor. Only within the base R distribution, maintained and mostly written by the R Core

RHEL 6 installed R version 3.2.3 from EPEL installed Start R and use the following command, but got warnings! install.packages("rstan", dependencies = TRUE, repos = "http://cran.r-project.org/") ... g++ -m64 -shared -L/usr/lib64/R/lib -L/usr/local/lib64 -o RcppEigen.so RcppEigen.o RcppExports.o fastLm.o -L/usr/lib64/R/lib -lRlapack -L/usr/lib64/R/lib -lRblas -lgfortran -lm

> I think one could implement hashing on the fly without any > serialization, similarly to how identical works, but I am not aware of > any existing implementation We have one in vctrs but it's not exported: https://github.com/r-lib/vctrs/blob/main/src/hash.c The main use is vectorised hashing: ``` # Non-vectorised vctrs:::obj_hash(1:10) #> [1] 1e 77 ce 48 # Vectorised

>>>>> Hadley Wickham >>>>> on Wed, 8 Aug 2018 09:34:42 -0500 writes: >>>> Method dispatch for `vec_c()` is quite simple because >>>> associativity and commutativity mean that we can >>>> determine the output type only by considering a pair of >>>> inputs at a time. To this end, vctrs provides

On Thu, Aug 9, 2018 at 4:26 PM jan Vitek <vitekj at icloud.com> wrote: > > > I'm now confident that I > > can avoid using "type" by itself, and instead always use it in a > > compound phrase (like type system) to avoid confusion. That leaves the > > `.type` argument to many vctrs functions. I'm considering change it to > > .prototype,

> First off, you are using the word "type" throughout this email; You seem to > mean class (judging by your Date and factor examples, and the fact you > mention S3 dispatch) as opposed to type in the sense of what is returned by > R's typeof() function. I think it would be clearer if you called it class > throughout unless that isn't actually what you mean (in