similar to: writeForeignSAS and potential extensions

... and is there also such a nice tool (like spss.get) for exporting data frames to SPSS? write.table does not keep the data frame labels - neither did the other exporting tools that I found. Thanks! Michael [[alternative HTML version deleted]]

My question is about the write.foreign() command in the foreign package. I use a command like the following to try and output data and a code file to read my data into SAS. write.foreign(data.frame.object, datafile="filepath", codefile="filepath", package="SAS", dataname="myData") With my data set, it gives the following error: Error in

Dear all, First of all, I thank you for the creation of the package. I write this message concerning the write.foreign() function from the foreign package and a bug that I discovered. When we want to save our dataset as a .sas file, the limit of variable names character is 8 by default. In SAS this limit is 32 character and an argument in the function, validvarname, can theorically switch the

Hi, is there a way to retrieve the line number of where en error occurred when sourcing a file in a tryCatch statement? Is it stored somewhere accessible? It is not found in the error object. Consider the following code/output and note the difference in the traceback between source (has line number) and sys.source (has no line number). Thank you, Renaud ######## # code ######## codefile <-

dear: when I read a Excel file(exp-11),The R project give me a error ,Just like this: ??'datafile' > write.foreign("exp-11.xls") ???list(df = df, datafile = datafile, codefile = codefile) : ??'datafile' > write.foreign("exp-11.xls") ???list(df = df, datafile = datafile, codefile = codefile) : ??'datafile' >

Hi Ricky / AJ Progress of sorts. I got passed the last problem by looking at the makefiles but run in to the next one, see below. It has created files in /contrib/R-2.4.0. there is an " R " under /contrib/R-2.4.0/bin/R. Running it gives :- /contrib/R-2.4.0/bin/R R version 2.4.0 (2006-10-03) Copyright (C) 2006 The R Foundation for Statistical Computing ISBN 3-900051-07-0 R is

I am trying to create a class union of class unions to facilitate method dispatch. When I execute code in the global environment, everything acts as expected, however when I put the same code in the context of a package, selectMethod can no longer find the correct method. This first block below puts the code in the context of a package: fn <- "codefile.R" writeLines( c(

Hello, I'm trying to import a SAS file made using SAS on Unix. Currently I'm using SAS on Windows and I'm trying to import that .ssd04 file to R. The file name of the file is testfile.ssd04 and it is located in 'M:\sasuser'. I'm using Windows XP and R 2.91. Basically what I'm doing is ############ r code ############## > library(foreign) > sashome <-

Dear R users, I have just upgraded R v1.5.0 to v1.6.1 for Windows but have trouble loading my library of R only functions (no C calls). After examining the "library" script this difference was found: (v1.5.0) which.lib.loc <- dirname(pkgpath) descfile <- system.file("DESCRIPTION", package = package, lib.loc = which.lib.loc) if

I'm trying to build an RPM of R 2.3.1 on a very old RedHat system (specifically, a ROCKS 3.3.0 cluster which is built on RH enterprise 3 (I think??)) I downloaded R-2.3.1.tgz from CRAN; downloaded the R.spec file cran.r-project.org/http://cran.r-project.org/bin/linux/redhat/SRPMS/ ; and ran rpmbuild -ba R.specs. Everything goes along fine until ... make[5]: Entering directory

Thanks, I'll look into it. On Tue, Feb 18, 2020 at 8:32 AM Ezra Tucker <ezztucker at gmail.com> wrote: > > Hi Robert, > > This looks like a bug to me (tested in R 3.6.2 on Windows), f(new("a")) > should return "hi!". I'll add that this DOES work properly in 3.6.1 > which leads me to suspect this could be due to the subtle change in the > way

dear all, i'm trying to reproduce an spss-anova in R. It is an 2x3x3 repeated measures desingn with repeated contrasts. In R i've coded a contrast matrix for all factors and made a split in the aov summary - but I can't get the repeated interaction contrasts. The output from SPSS looks like this: TaskSw * CongNow * CongBefore: SS df Mean Square F Sig. 1 vs. 2 1 vs. 2 1 vs. 2

Did not seem to reach Saikat DebRoy, this might be the forum. Bendix -----Original Message----- From: BXC (Bendix Carstensen) Sent: 24. november 2008 15:00 To: 'saikat at stat.wisc.edu'; 'stvjc at channing.harvard.edu' Subject: read.ssd It's always annoyed me that that read.ssd crashed on datasets with long variable names, but the other day a collegue of mine pointed out to

Okay - that makes sense and thanks for looking into this! As an aside, from R-devel's perspective would you say methods are stabilizing again or do you foresee a lot of changes coming in the 4.* series? On Tue, Feb 25, 2020 at 3:39 PM Michael Lawrence via R-devel < r-devel at r-project.org> wrote: > This seems to work as expected (returning "hi!") in R-devel, but there

Good day My name is Jos? Oscar, I'm from Mexico and I have some questions about foreign in your write.foreig( ) function. We know that this function generates the inputs to be able to run them or execute them in another program like SPSS, SAS or Stata. In these cases, when creating an example file, a matrix and using the function to execute the .sps file directly from SPSS, I don't care or

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) When I filed this a few minutes ago, I left off the rewritten read.ssd(). I've included it at the end this time. read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member

here appears to be a bug in the foreign library. The following code used to work, but now generates an error when 'package="SAS"' is specified: ds <- read.csv("http://www.math.smith.edu/sasr/datasets/help.csv") # running foreign package version 0.8-30 library(foreign) # this works fine write.foreign(ds, "foo", "bar", package="Stata") #

While installing my small package, I met a tricky problem. For clarity, let me explain it with the following simplified example. In ~/pkg/R/aclass.R, setClass("aclass", contains="bclass", representation(i="numeric")) In ~/pkg/R/bclass.R, setClass("bclass", representation(j="numeric")) After building a "pkg" package, the file

I tried to use write.foreign() to export to SAS this morning and got an error. When I looked at the code for writeForeignSAS() I saw this line: dfn < -df which I think should be dfn <- df So, I tried to run update.packages() to see if there was an updated version and got the following result. > update.packages(c("foreign")) Warning message: In list.files(lib) :

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member names (the sectionnames argument to read.ssd) longer than 8 characters. The second is that PROC COPY also fails if any