-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUGZILLA #6701] lookup.xport in foreign ignoring some datasets #2068
Comments
From: Peter Dalgaard <p.dalgaard@<::CENSORED -- SEE ORIGINAL ON BUGZILLA::>>
SAS version 5 XPORT libraries? Why? Does it work any different with libname x xport "H:\what\ever"; ?
-- METADATA
|
NOTES: METADATA
|
Audit (from Jitterbug): METADATA
|
I just asked a SAS user and was told that the SAS export engine 5 is still used even though SAS itself is on version 9.6. So this is not about what SAS version is supported. However I don't know how to test if this issue is reproducible. The link to download the file doesn't work any more. Could this be closed? METADATA
|
Created attachment 2528 [details] This is a SAS export file with three data sets one of which is empty. METADATA
INCLUDED PATCH
|
I tested lookup.xport on the sample file and it worked fine. I would say this issue can be closed as no longer reproducible -- although I'm not sure if there was something more specific about the number 37. That said, I believe that both SAS and R have had substantial changes since this report. METADATA
|
From: Svetlana Eden <svetlana.eden@<::CENSORED -- SEE ORIGINAL ON BUGZILLA::>>
The Details.
In the following 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 that revealed the problem
(and can not be shared).
It means that lookup.xport ignores non-empty datasets also.
The file "emptySasData3.xpt" has 51 empty datasets.
lookup.xport reads only 37 first datasets.
(In non-empty data lookup.xport ignored
datasets in the middle (not in the end) )
[1] "AE" "BII" "BIO" "BLI" "BP" "C" "D" "DEA" "DEM"
"DHT"
[11] "DIS" "DP" "E" "EC" "EL" "G" "HS" "HU" "IN"
"IP"
[21] "L" "LT" "MC" "MO" "NO" "PAS" "PAT" "PATH" "PO"
"PR"
[31] "PS" "PV" "Q" "RA" "RE" "SA" "SL"
The following datasets were not read by lookup.xport
UR, URN, VIS, VIT, VO.
The example of the
SAS code used to builds the empty data
from the non-empty data in "export.xpt".
options nofmterr;
proc options;run;
libname x sasv5xpt "H:\projects\export.xpt";
libname y sasv5xpt "H:\projects\emptySasData3.xpt";
data ae; set x.ae(obs = 0); run;
...
data vit; set x.vital(obs = 0); run;
data vo; set x.volume(obs = 0); run;
proc copy in = work out = y; run;
I think I did not miss anything,
thank you,
Svetlana
--
Svetlana Eden Biostatistician II School of Medicine
Department of Biostatistics Vanderbilt University
METADATA
The text was updated successfully, but these errors were encountered: