similar to: SAS XPORT Transport Format

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

> 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

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

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

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

> 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

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")

Saikat DebRoy and I have been working on an R package that, among other things, will read SAS data libraries in the XPORT format. Even though a SAS data set is of a fairly simple structure, it is a challenge to write code to read the libraries "properly". In fact, I am beginning to think that file format is not well-defined. Here is the situation: - a SAS data set is a table.

I see in the archives significant discussion about SAS, CDISC formats etc. for FDA, but no direct suggestion of adding a write.xport method to the foreign package. Are there significant barriers to doing so? [[alternative HTML version deleted]]

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

Hi All, In 2005, I noted that when I used read.xport function in the foreign package to import a SAS transport file (.xpt) with multiple files imbedded in it, data frames from some of the files were not created. Since then, I discovered that the information from the missing files is being read into one dataframe, but the data appear corrupted. This has been noted before by Dr. Harrell (in

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

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

I like R more than SAS. My job is doing research on clinical trial. But I was told that FDA only accepts the result from SAS. Is that true? TOO BAD. [[alternate HTML version deleted]]

Hi all, I am setting up a new AD server with Samba 4.1.11 from the FreeBSD ports. I struggle with the internal DNS. I add a new CNAME record but it does not show up properly. I gave the AD domain a new DNS domain (domain.fda) and the server the name samba4.domain.fda. I am using the internal DNS, and a forwarder to a bind server in the same network. After the AD provision I have this here

Hi, All: What might cause "R CMD check" to report, "could not find function" for a function that has long been in the 'fda' package? Both Jim Ramsay in Ottawa, Canada, and I in San Jose, CA, get this same error. I replicated it with a fresh, anonymous checkout from R-Forge (svn checkout svn://svn.r-forge.r-project.org/svnroot/fda). With this, I did

Hello: What do you recommend I do to get past cryptic error messages from "R CMD check", complaining "No such file or directory"? The package is under SVN control, and I reverted to a version that passed "R CMD check", without eliminating the error. The "00install.out" file is short and bitter: cat: ./R/Copy: No such file or directory cat:

I hope that Marc doesn't mind, but I felt that part of his recent post was important enough to deserve it's own subject line rather then being lost in a 60-msg-long thread... On Sun, Jan 11, 2009 at 10:08 AM, Marc Schwartz <marc_schwartz at comcast.net> wrote: ... I strongly believe that the comments regarding R and the FDA are overly negative and pessimistic. The hurdles to

Yesterday I just noticed the new document on R and regulatory aspects for biomedical research posted at http://www.r-project.org/doc/R-FDA.pdf Coming from an institution that performs a large number of clinical trials for FDA and being an advocate of R myself, I have found that the following issues usually come up when discussing the use of R for FDA trials: 1. Most FDA submissions come down to

Hi all there Can some one clarify me on this issue, features wise which is better R or SAS, leaving the commerical aspect associated with it. I suppose there are few people who have worked on both R and SAS and wish they would be able to help me in deciding on this. THank you for the help --------------------------------- [[alternative HTML version deleted]]