search for: xport

Colleagues During the transition to R3.0.0 (OS X), one of the packages that I used -- SASxport -- did not work until I used the "type=source" option in install.packages. This led to an adventure: 1. I downloaded the package source: SASxport_1.2.4.tar.gz 2. in the SASxport/R folder, I found all the functions that are part of the package. I became interested in whether I cou...

...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 error and warning messages: > read.xport("test.xpt") Error in read.xport("test.xpt") : The specified file does not start with a SAS xport file header! In addition: Warning message: In readBin(file, what = character(0), n = 1, size...

...t; > 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 error and warning messages: > >> read.xport("test.xpt") > Error in read.xport("test.xpt") : > The specified file does not start with a SAS xport file header! > In addition: Warning message: > In readBin(...

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...

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") Alfalfa<-read.xport("test.xpt") I have set the directory correctly as far as I am aware, b...

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 l...

...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 code for producing SAS transport files for testing: libname x SASV5XPT "test.xpt"; libname y SASV5XPT "test2.xpt"; PROC FORMAT; VALUE race 1=green 2=blue 3=purple; RUN; PROC FORMAT CNTLOUT=format;RUN; data test; LENGTH race 3 age 4; age=30; label age="Age at B...

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 recreation of sensitive data. It was generated in SAS as an export file containing 51 empty datasets, but it has a structure of the non-empty data...

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 discussion of the bug can be found from the foll...

...not had SAS on my machines in about 12 years so it would be nice to be able to read binary transport files instead of having to run the slower sas.get function in the Hmisc library. sas.get has to launch SAS to do its work. The foreign package implements a quick way to read such files in its read.xport function. This function has some significant problems which I have reported to the developers some time ago but fixes do not seem to be forthcoming nor have acknowledgements of the bug report. The developers have done great work in writing the foreign package (and many other awesome contributions...

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: http://finzi.psych.upenn.edu/R/Rhelp02a/ar...

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** **COMPRESSED** **COMPRESSED********LIB CONTROL WIN_PRO<BC>^BWIN^@8 SAS8.2...

Hi, I'm experiencing a strange issue while attempting to import some XPORT formatted datasets created using SAS 9.3. I 'm using R 2.2.1 with a recently downloaded version of the "foreign" package, although I don't have the version for that handy. I have been able to load some of the XPORT datasets, however when I increase to the entire dataset, I get t...

> 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 me to read the xpt file into R: > > library(SASxport) > data(Alfalfa) > lookup.xport("test.xpt") > Alfalfa<-read.xport("test.xpt") > > I have set th...

Hi, SAS transport files created with the xport engine in SAS can be read using read.xport. However, the xport engine only works with SAS version 6, and consequently long variable names are not allowed... Can anyone tell me how to get SAS data (ver 8) into R (easily)? Thanks in advance S?ren H?jsgaard sorenh at agrsci.dk http://www.jbs.ag...

...ame: 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 multiple failures: Windows 98 Version 4.10.1998 RGUI failure in no-valid page module KERNEL32.DLL of 0177:bff7b983. Regiters: EAX=00000020 CS=0177 EIP=bff7b983 EFLGS=00010202 EBX=0270f150 SS=017f ESP=0270f108 EBP=02...

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'; leng...

Let''s move this to the Shorewall Development list.... On Tuesday 10 February 2004 03:14 pm, xavier wrote: > here is a patch to allow this : > |ACCEPT<10/sec:20>:debug fw lan:$ntp_servers udp 123 - - - - ntp > > a problem with the patch is that now the logprefix is mandatory. > i''m trying to debug it, but i can''t find the flaw. Also, with

...ur <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 SAS XPORT Stephen> file, when it should be loading the SAS XPORT file in Stephen> binary format? Is this a problem? I have no idea what you mean by binary/text SAS XPORT formats. R implements the XPORT format as described in http://ftp.sas.com/...

...39;; filename transp 'D:\CES Analysis\Data\fadata.xpt'; /* create a transport file - R cannot read file created by proc cport */ proc cport data=ces2.fadata file=transp; run; I then tried to read it in R using: > library(foreign) > library(Hmisc) > fadata2 <- sasxport.get("D:\\CES Analysis\\Data\\fadata.xpt") Error in lookup.xport(file) : file not in SAS transfer format Next I tried using the libname statement and the xport engine to create a transport file. The problem with this method is that variable names cannot be more than 8 characters as th...