similar to: Problem with read.xport() from foreign package

Displaying 20 results from an estimated 2000 matches similar to: "Problem with read.xport() from foreign package"

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
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
2001 May 05
1
read.xport bug of foreign pkg (PR#933)
Full_Name: Jorge A. Tomasevic Version: 1.2.2 OS: Win98 Submission from: (NULL) (146.83.23.177) As i'm not an "R-expert-user", i will describe what i do: i) open Rgui.exe ii) ivoke foreign library : >library(foreign) iii) i try to read an .xpt file (from Systat 9): >datos <- read.xport('ipoisson.xpt') iv) then the program crashes. Norton CrashGuard alerts the
2008 Feb 25
1
Read.xport function in package foreign
Hi All, Sorry that I didn't provide enough information. I've been trying to import SAS xport files that contain multiple files using package foreign's read.xport. I first attempted this back in 2005 and had problems. Some of files that were present in the SAS xport file weren't being created in R. I submitted my problem to the community:
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
2018 Apr 13
5
Reading xpt files into R
Hello R folk I have an xpt file which I have been trying to open into R in R studio On the net I found guidance which says that I need packages Hmisc and SASxport which I have successfully loaded. I had also found some code which says that this would allow me to read the xpt file into R: library(SASxport) data(Alfalfa) lookup.xport("test.xpt")
2018 Apr 14
1
Fwd: Re: Reading xpt files into R
> On Apr 14, 2018, at 12:18 PM, WRAY NICHOLAS via R-help <r-help at r-project.org> wrote: > > > -------- Original Message ---------- > From: WRAY NICHOLAS <nicholas.wray at ntlworld.com> > To: peter dalgaard <pdalgd at gmail.com> > Date: 14 April 2018 at 20:18 > Subject: Re: [R] Reading xpt files into R > > > Well yesterday I'd downloaded
2018 Apr 14
0
Fwd: Re: Reading xpt files into R
-------- Original Message ---------- From: WRAY NICHOLAS <nicholas.wray at ntlworld.com> To: peter dalgaard <pdalgd at gmail.com> Date: 14 April 2018 at 20:18 Subject: Re: [R] Reading xpt files into R Well yesterday I'd downloaded the "foreign" package and tried to open the xpt file using that: library(foreign) read.xport("test.xpt") I got the following
2018 Apr 13
0
Reading xpt files into R
> On Apr 13, 2018, at 10:01 AM, WRAY NICHOLAS via R-help <r-help at r-project.org> wrote: > > Hello R folk > > I have an xpt file which I have been trying to open into R in R studio > > On the net I found guidance which says that I need packages Hmisc and SASxport which I have successfully loaded. > > I had also found some code which says that this would allow
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
2010 Dec 06
3
How to this SAS transport file in R?
Dear All, I try to read the SAS transport file in R, but it shows error. Please help! I am using R 2.11.1 library(foreign) download.file("http://isites.harvard.edu/fs/docs/icb.topic35387.files/demo_c.xpt","C:/Desktop/demo_c.xpt") sasxport <- read.xport("C:/Desktop/demo_c.xpt") Error in lookup.xport(file) : file not in SAS transfer format -- View this
2005 Apr 07
1
Importing SAS transport data
I have encountered a problem reading SAS transport files on both a Mac (OS X) and Linux (RedHat 9), both using R2.0.1. After loading "foreign", the command: read.xport("V1622101_050304.xpt") yields: Error in lookup.xport(file) : File not in SAS transfer format In Linux, I can "cat" the file. The first few lines are: **COMPRESSED** **COMPRESSED** **COMPRESSED**
2006 Sep 26
0
read.xport: Writing and reading dataframe to disk directly
Hi All, is there a way of directly writing to disk file, the dataframe or list of dataframes that result from read.xport function. This function converts SAS export files to R dataframes. I would like to convert a SAS transport file to R, but the resulting R dataframes do not fit in the memory of my computer. Is there way to write the output of this fucntion to disk, perhaps using some pipe or
2005 Jul 14
3
read.xport
I am trying to import data from a SAS XPORT file that contains 24 SAS files. When I use the "read.xport" procedure only about 16 data frames (components) are created. Any suggestions? ************************************************************************* Gary A. Nelson, Ph.D Massachusetts Division of Marine Fisheries 30 Emerson Avenue Gloucester, MA 01930 Phone: (978)
2002 Mar 28
0
Enhancement request: lookup.xport() in library foreign
I installed the foreign library yesterday, and have successfully used the read.xport() function to get data from SAS. This is very helpful. SAS "date" and "datetime" variables become numeric variables, which is, of course, what they really are in SAS. Naturally, it is desirable to convert them to date/time objects in R. Looking at the documentation for the SAS transport
2008 Oct 09
1
Error when reading a SAS transport file
Dear All, I get the following error when using either SASxport or Hmisc to read an .xpt file: > w <- read.xport("D:/consult/Trophos/dnp/base/TRO_ds_20081006.xpt") Erreur dans factor(x, f$value, f$label) : invalid labels; length 15 should be 1 or 14 > z<- sasxport.get("D:/consult/Trophos/dnp/base/TRO_ds_20081006.xpt") Erreur dans factor(x, f$value, f$label) :
2007 Aug 15
2
Loading JMP Files
Hi, I know how to use SPSS and JMP, and have quite a few JMP files I would like to use in R. I converted them to .xpt files, downloaded the 'foreign' library then tried this command: >read.xport("D:\\Databases\nameoffile.xpt") to which I get: >Error in lookup.xport(file) : unable to open file I have read FAQ lists and Google searched and cannot figure out what I'm
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 Nov 10
3
read SAS file
Looked at a lot of documentation and listserv postings and still can’t solve this problem. I need to get a SAS dataset into R. I’ve converted it to an .xpt file and when I try to read it I get: > read.xport("cft2008R") Error: could not find function "read.xport" > Not sure what I’m doing wrong. I’m running SAS 9.1.3 on an UNIX box. I ftp’d the file over to my
2004 Nov 23
3
Problem with read.xport() from foreigh package (PR#7389)
Full_Name: Ruskin Chow Version: R 2.0.1 OS: Windows 2000 Submission from: (NULL) (203.169.154.66) Data imported from SAS using read.xport() in package foreign are converted to <NA> when the SAS data field consists of character strings that are only one character long. This is apparently a previously reported bug and perhaps fixed in some platform other than Windows (rw2001).Some