similar to: execution time of .packages

Dear R-users, Can some one help me out. I tried installing some packages in R_2.5.1 but I get an error message as shown below. This is unusual since I have been installing and updatings packages in the same version of R. > chooseCRANmirror() > update.packages(ask='graphics') Error in .readRDS(pfile) : unknown input format or > utils:::menuInstallPkgs() Error in .readRDS(pfile) :

I met today a computer crash and our maintenance officer had to reinstall some components of the OS (MS Windows XP Pro) as well as the Internet browser (among other things). Now, I cannot install packages from a distant repository: > utils:::menuInstallPkgs() Error in .readRDS(pfile) : unknown input format > traceback() 5: .readRDS(pfile) 4: .packages(all.available = TRUE) 3:

DeaR Forum, I am trying to install the library ggplot2.? Currently I am using following R version R version 3.4.1 (2017-06-30) -- "Single Candle"Copyright (C) 2017 The R Foundation for Statistical ComputingPlatform: x86_64-w64-mingw32/x64 (64-bit) However, when I try to install ggplot2 and few other packages, I am getting following error. > library(ggplot2)Error: package or namespace

Following patch for pfile.rb and pfile/source.rb allows the user to set a replace => false parameter on a file sourced by puppet, but not replaced if checksums do not match. This is for cases in which it is desired to distribute initial "bootstrap" files and ensure future existence, yet allow them to be modified on the node. RTS --- pfile.rb~ Wed Aug 2 04:47:05 2006 +++ pfile.rb

I am having one frustrating time trying to decipher why ov_read is failing in my MFC/C++ application, and I see in Google results that others have had difficulty as well. These google discussions generally involve libraries, dll's and linking options, as though there are perhaps some basic incompatibilities between ogg vorbis and win32 and/or MFC/C++. Very confusing. If I pass fopen a

Greetings, I've just downloaded the Ogg/Vorbis Win32 SDK 'OggVorbis-win32sdk-1.0.1.zip' and made a test app to open an ogg file. But as soon as I call ov_open() the program crashes because of an access violation to address 0x00000010... This happens on both Release and Debug builds. The test app is simple: #include "vorbis/codec.h" #include "vorbis/vorbisfile.h"

Point of clarification: Packages other than those that are part of the "standard" r distro must first be "installed" from a package repository -- typically CRAN -- via the install.packages()* function before they can be accessed via the library() or require() function. Have you done this? See ?installed.packages if you are unsure. Also, R must know what libraries to look in

Eddie, I have been reviewing vorbis list postings, because I have been spinning my wheels for a week, trying to make a simple insertion of ogg vorbis decoding (vorbisfile) in the audio class of my MFC/C++ program. I just read your thread from April 2004. Question: Do you have anything you could send me, since I assume you succeeded in getting results? And/or could you take a look at what I

OK, I've been developing a small class that I can use in virtually any application to load and decode OGG files. Everything works fine until it reaches the line with the call to ov_open, then the application freezes and has to be killed. This is a single-threaded Win32 app. Below is both the structure that gets passed around, and my entire OGG class. Maybe one of you can figure this out.

I am using/trying to use R 2.2.0. I have created a package of ``supplementary'' time series functions for use by my students in a time series course. The package involves only raw R code; no dynamic loading to complicate matters. I need to install this package in a location on a local area network where the students can access it under Windoze. In the past I learned that I could do

Hi all, Take this simple script, which I'm trying to use to understand when modification in-place occurs, and when a new object is created: message("Global") x <- 1:3 .Internal(inspect(x)) x[2] <- 1L .Internal(inspect(x)) message("In function") (function() { x <- 1:3 .Internal(inspect(x)) x[2] <- 1L .Internal(inspect(x)) })() If I run it from the

Hi, I would like to know if it's ok to use .Internal(inspect(x)) in order to detect vector copying. Take for example the following silly code: f <- function() { x = seq(10) print(.Internal(inspect(x))) for(i in seq(10)) { x[i] <- x[i] + 1 print(.Internal(inspect(x))) } } The output of f() was: @bd7acf0 13 INTSXP g0c4 [NAM(1)] (len=10, tl=0) 1,2,3,4,5,... [1] 1 2

I have a vaiable named NAM having value : 1,2,3,4,5,6,7,8,9. I want to make an indicator variable that will take value 1 if NAM=7 or NAM=8 or NAM=9. How can I do that? I usually do: Var001<- ifelse(NAM==7,1,0) for the simplest case. [[alternative HTML version deleted]]

Hi All? I was looking at a posting from June-17. I managed to solve it. However, when I changed the example in the posting, my solution will work only once at a time which was mentioned by Jim Lemon on his response to the original posting. This means that my solution will have to be repeated as many times as the maximum number of spaces on each gap; something that may not work well for large

Hi all, I have problems in a dataframe variables types. Look: from a loop function: for(...){ ... dados.fin <- rbind(dados.fin, c(L=j, A=j^2, Nsp=nsps, N=length(amosfin$SP), AmT="am",NAm=nam, AMST=amst)) dados.fin <- rbind(dados.fin, c(L=j, A=j^2,

Hello, I?m experimenting with ALTREP and was wondering if there is a preferred way to create an ALTREP wrapper vector without using .Internal(wrap_meta(?)), which R CMD check doesn?t like since it uses an .Internal() function. I was trying to create a factor that used an ALTREP integer, but attempting to set the class and levels attributes always ended up duplicating and materializing the

Hi, I expected NAMED to be 1 in all these three cases. It is for one of them, but not the other two? > R --vanilla R version 2.14.0 (2011-10-31) Platform: i386-pc-mingw32/i386 (32-bit) > x = 1L > .Internal(inspect(x)) # why NAM(2)? expected NAM(1) @2514aa0 13 INTSXP g0c1 [NAM(2)] (len=1, tl=0) 1 > y = 1:10 > .Internal(inspect(y)) # NAM(1) as expected but why different to x?

Hi there, When I run the following code, I could get correct objects (with correct values): for(i in 1:6) { #-- Create objects 'r.1', 'r.2', ... 'r.6' -- nam <- paste("r",i, sep=".") assign(nam, 1:i) # save(nam, file = paste(nam, "RData", sep = ".")) } I hope to save the object 'r.1',

Hello, I have a maybe trivial question, but I simply don't understand well enought how to work with text/strings: I have a rather compelx data structure, a big list with several sub-lists/dataframes and for certain calculations (which I do in loops), I only need a certain group of sub-lists/dataframes, which I want to specify with a name vector and paste together the object name and pass it

Hi! Like to write quite a lot (ca 100) of objects from my envirovment with save. The names of the objects are in a list nam. nam<-dir() nam<-grep("E",nam,value=T) length(nam) 20 for(x in nam) { #reads the objects and assigns the names. assign(x,simFromEmboss(Simmatrix(),x)) nnam<-paste(x,".rda",sep="") print(nnam) save(x,file=nnam) } I knew that