search for: afcourse

...I really do not know where to look in for my problem. I am moving from SAS and I have difficulties in translating SAS to R world. I hope I will get some hints or pointers so I can study from there on. I would like to do something like this. In SAS I can write a macro as example bellow, which is afcourse a silly one but shows what I don't know how to do in R. %macro test(data, colname, colvalue); data &data; ... &colname="&colvalue"; other_&colname="other_&colvalue"; run; %mend; And if I run it with this call: %test(Greg...

...et me know if such a question should be sent to R-help. I did a contribution to function hwe.hardy in package 'gap' during the weekend. That functions performs Hardy-Weinberg equilibrium test using MCMC. The return of the function does not have classical components for htest class so I was afcourse not successfull in using it. However, I managed to copy and modify some part of print.htest to accomplish the same task. Now my question is what to do in such cases? Just copy parts of print.htest and modify for each test or anything else. Are such cases rare? If yes, then mentioned approach is...

Hello! I was just wondering if Sweave can work with \input or \include LaTeX commands. So, is it aware of such a possible hierarchy in documents. I would test that, but I don't have such a report available at the moment. I thought of that when I was writting shell script for Sweave from command line and I have solved that part there. -- Lep pozdrav / With regards, Gregor GORJANC

...E=en_US.utf8; LC_MONETARY=en_US.utf8;LC_MESSAGES=en_US.utf8;LC_PAPER=C;LC_NAME=C;LC_ADDRESS=C; LC_TELEPHONE=C;LC_MEASUREMENT=C;LC_IDENTIFICATION=C" # and new internationalization functions say that everything should be OK R> l10n_info() $MBCS [1] TRUE $"UTF-8" [1] TRUE # and It afcourse works fine if I set R> Sys.setlocale("LC_CTYPE", "C") # If I echo LC variables in terminal I have $ echo $LC $LC_ALL $LC_MEASUREMENT $LC_PAPER $LC_TIME $ echo $LC_PAPER a4 $ echo $LC_TIME en_US $ echo $LC_MEASUREMENT metric $ echo $LC_ALL en_US.utf8 $ e...

...E=en_US.utf8; LC_MONETARY=en_US.utf8;LC_MESSAGES=en_US.utf8;LC_PAPER=C;LC_NAME=C;LC_ADDRESS=C; LC_TELEPHONE=C;LC_MEASUREMENT=C;LC_IDENTIFICATION=C" # and new internationalization functions say that everything should be OK R> l10n_info() $MBCS [1] TRUE $"UTF-8" [1] TRUE # and It afcourse works fine if I set R> Sys.setlocale("LC_CTYPE", "C") # If I echo LC variables in terminal I have $ echo $LC $LC_ALL $LC_MEASUREMENT $LC_PAPER $LC_TIME $ echo $LC_PAPER a4 $ echo $LC_TIME en_US $ echo $LC_MEASUREMENT metric $ echo $LC_ALL en_US.utf8 $ e...

Hello! This really isn't so important, but it comes often in my mind, when I write documentation for functions. Writing R Extensions manual says that one should describe each element of the argument list (which is afcourse OK) in a form: \item{arg_i}{Description of arg_i.} When I started with R it really helped me that some "man pages" used \item{arg_i}{Mode. Description of arg_i.} e.g. \item{argument1}{Logical. Bla bla bla.} \item{argument2}{Integer. Bla bla bla.} \item{argument2}{Character. Bla bla...