Bugs-ers:
I have been overwhelmed by the amount of interest in my SAS macro (30 so
far). So instead of trying to respond to each person individually, I
have decided to post it on the mailling list. If anyone has a problem
with the macro or the attachment, please let me know.
A few remarks. Several people asked me about my comment relating to
batch BUGS. What I was trying to say was; I have only tested the macro
on WinBUGS generated CODA files and not with the original BUGS program,
but I don't anticipate any problems. Please let me know if you have
any.
The macro is called _DECODA. It makes use of two other macros, _COUNT
and _PRINTTO. Only _COUNT is necessary, but _PRINTTO is helpful since
the multiple invocations of the INFILE statement create a verbose .log
file which can be counter-productive.
Here's how you call the macro. If you have named the index file,
root.txt and each of the chains root#.txt where # is 1-10, then:
%_decoda(out=mydata, chains=2, file=root.txt);
If you are following the original BUGS naming convention, then it's a
little more work:
%_decoda(out=mydata, file=bugs.ind, file1=bugs1.out, file2=bugs2.out);
If you want to suppress the .log, in Windows:
%_decoda(log=NUL:, ...
or in Unix:
%_decoda(log=/dev/null, ...
Lastly, the DLM= options that I have specified on the INFILE statement
might not work with SAS for Macintosh (suppressing the .log also could
be a problem).
--
WWLD? (What Would Lombardi Do?)
Was "Name That Tune" Rigged?
Rodney Sparapani, Duke Clinical Research Institute
For addressing and schedule information
see http://www.duke.edu/~spara002
|