similar to: problems with read.ssd in foreign

Displaying 20 results from an estimated 2000 matches similar to: "problems with read.ssd in foreign"

2009 Oct 20
2
Problems importing Unix SAS .ssd04 file to R (Win)
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 <-
2007 Apr 23
0
Correction to PR #9631 (PR#9632)
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
2011 Mar 06
1
read.ssd() from foreign package
Hi, I am encountering a confusing problem when I tried to use read.ssd to read SAS datasets. For one SAS dataset "a.sas7bdat", it did not work; while for another SAS dataset "b.sas7bdat" it worked: > tmp<-read.ssd("C:\\SASdata", "a",sascmd="C:/Program >Files/SAS/SASFoundation/9.2/sas.exe") SAS failed. SAS program at
2002 Dec 25
0
Part II Re: read.ssd {foreign} (Reading a permanent SAS d ataset into an R data frame)
Scot, Thanks for the info. I will try your code out to verify the result, but before I do that, will your code (SAS and R) work with variable names that are longer than 8 characters long without truncating the variable name in R? Also, I wonder about using your method or the PROC EXPORT method with larger data sets. The data sets I will be working with for the most part will not be that large,
2008 Dec 03
2
reading version 9 SAS datasets in R
Hi, I am trying to read a SAS version 9.1.3 SAS dataset into R (to preserve the SAS labels), but am unable to do so (I have read in a CSV version). I first created a transport file using the SAS code: libname ces2 'D:\CES Analysis\Data'; filename transp 'D:\CES Analysis\Data\fadata.xpt'; /* create a transport file - R cannot read file created by proc cport */ proc
2007 Apr 23
0
foreign::read.ssd and long names (PR#9631)
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
2005 Sep 26
1
reading SAS data files
I am attempting to read in a SAS 9.1 data file. After starting R I change to the directory containing the sas data file and use the "dir" command to confirm that it is there. Then I run the following R-code: library(foreign) sashome <- "/Program Files/SAS/SAS 9.1" test<-read.ssd(file.path(sashome), "pcb", sascmd = file.path(sashome,
2002 Dec 25
0
Part II Re: read.ssd {foreign} (Reading a permanent SAS d ataset into an R data frame)
Scot, Thanks for the additional information. On further reflection... whether one uses SAS PROC EXPORT or uses a SAS LIBNAME yourfile XPORT 'yourpathname'; statement, an intermediate file is created in either case. As far as experience tells me now, PROC EXPORT is a far superior choice, because variable names do not get truncated and you only have to deal with reading in a simple text
2004 Mar 26
1
lookup.xport in foreign ignoring some datasets (PR#6701)
The Details. In the following version. > version _ platform i386-pc-linux-gnu arch i386 os linux-gnu system i386, linux-gnu status major 1 minor 8.1 year 2003 month 11 day 21 language R > lookup.xport ignores some datasets in sas export file. File "emptySasData3.xpt" (available at http://biostat.mc.vanderbilt.edu/tmp/emptySasData3.xpt) is a
2002 Dec 20
1
read.xport and lookup.xport in foreign (PR#2385)
Under platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status major 1 minor 6.1 year 2002 month 11 day 01 language R and using foreign 0.5-8 I am encountering errors when using read.xport. Here's
2002 Dec 20
2
Part II Re: read.ssd {foreign} (Reading a permanent SAS d ataset into an R data frame)
try: library(foreign) read.ssd("J:\\QM\\Reports\\Sarthur\\SAS_Application\\SAS_Data_Sets","use") instead, hth, Merry Christmas, Bernhard -----Original Message----- From: Stephen Arthur [mailto:sarthur67 at yahoo.com] Sent: 20 December 2002 16:55 To: ripley at stats.ox.ac.uk; rossini at blindglobe.net Cc: r-help at stat.math.ethz.ch; stvjc at channing.harvard.edu Subject:
2002 Dec 21
2
Part II Re: read.ssd {foreign} (Reading a permanent SAS d ataset into an R data frame)
>>>>> "Stephen" == Stephen Arthur <sarthur67 at yahoo.com> writes: Stephen> The SAS data set I PROC CPORTed is [9] the result is [10]. Stephen> I PROC CIMPORTed [10] back to its orginal state [9], and it Stephen> worked. Stephen> So the SAS people think that the error is not with the SAS Stephen> XPORT file, but with R trying to load a text
2003 Jan 18
1
SAS transport files and the foreign package
Even though the FDA has no policies at all that limit our choices of statistical software, there is one defacto standard in place: reliance of the SAS transport file format for data submission (even though this format is deficient for this purpose, e.g., it does not even document value labels or units of measurement in a self-contained way). Because of the widespread use of SAS transport files in
2002 Apr 26
1
Problem with read.xport() from foreign package
I have found that data imported from SAS using read.xport() in package foreign (installed recently) does not match the original data, when the data consists of character strings that are only one character long. Here is an example. ---- SAS commands to create the data ---- options nocenter; data foo; a='a'; b='bb'; length c d $2; c='c'; d='
2010 Aug 02
1
read SAS dataset using read.ssd()
Hi, I am using read.ssd() from foreign package to read some SAS datasets. I have 2 types of SAS datasets, one with "sas7bdat" extension, the other with "ssd01" extension. I have no problem with the first dataset type, but got the following error message with the 2nd dataset type (with "ssd01" extension): test<-read.ssd("C:/Documents and
2001 May 31
1
R and SAS
Hi I'm trying to read SAS-data on VAX/VMS to Windows R using foreign pakage read.xport and experience some problems. Following lines are used in SAS to create XPORT file LIBNAME a ''xxx; LIBNAME b XPORT ''; PROC COPY IN=a OUT=b; RUN; and I succeed in getting file that looks like correct xport file.However when typing in R following
2010 Mar 25
1
Read SAS data
Hi! I need to import in R some SAS dataset (sas7bdat). I found two functions to do it: "read.ssd" from the package "foreign" and "sas.get" from "Hmisc". df = read.ssd(libname = path2data, sectionnames = "sasSmallDataset", tmpXport = path2data, tmpProgLoc = path2data, sascmd = path2sas) sas.get(libraryName = path2data, member =
2011 Jan 05
1
Reading large SAS dataset in R
Hi all, I have a large (approx. 1 GB) SAS dataset (test.sas7bdat) located in the server (“R:/” directory). I have SAS 9.1 installed in my PC and I can read the SAS dataset in SAS, under a windows environment, after assigning libname in "R:\" directory. Now I am trying to read the SAS dataset in R (R 2.12.0) using the read.ssd function of the “foreign” package, but I get an error
2024 Jun 06
1
Bug report for package foreign anf functon write.foreign
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
2013 Feb 27
0
question about read.ssd function
Hi there, I am trying to read SAS dataset into R and have observed some weird behaviors. Here is my setting. I copied retail.sas7bdat from sashelp and placed it in my test directory C:\Temp. In R, I submitted the following command >read.ssd("C:/Temp", "retail", sascmd="C:/Program Files/SAS/SASFoundation/9.2/sas.exe") The data has been read correctly. But when