search for: in_dir

...does a better a job of locating gcc. (Contributed by Andrew Redd) * `show_rd` passes `...` on to `Rd2txt` - this is useful if you're checking how build time `\Sexpr`s are generated. * A suite of `with` functions that allow you to temporarily alter the environment in which code is run: `in_dir`, `with_collate`, `with_locale`, `with_options`, `with_path`, ... (Fixes #89) * `release` ask more questions and randomises correct answers so you really need to read them (Fixes #79) * `source_gist` now accepts default url such as "https://gist.github.com/nnn" * New system path ma...

...does a better a job of locating gcc. (Contributed by Andrew Redd) * `show_rd` passes `...` on to `Rd2txt` - this is useful if you're checking how build time `\Sexpr`s are generated. * A suite of `with` functions that allow you to temporarily alter the environment in which code is run: `in_dir`, `with_collate`, `with_locale`, `with_options`, `with_path`, ... (Fixes #89) * `release` ask more questions and randomises correct answers so you really need to read them (Fixes #79) * `source_gist` now accepts default url such as "https://gist.github.com/nnn" * New system path ma...

Hi gang, I was a little surprised to see that patch go by recently which fixed an endian bug. I went to see how sparse checking looked and it was.. broken. I got it going again in my Fedora environment. Most of the patches are just cleanups, but there *were* three real bugs lurking in all that sparse warning spam. So I maintain that it''s worth our time to keep it going and fix

I'm using caret to assess classifier performance (and it's great!). However, I've found that my results differ between R2.* and R3.* - reported accuracies are reduced dramatically. I suspect that a code change to kernlab ksvm may be responsible (see version 5.16-24 here: http://cran.r-project.org/web/packages/caret/news.html). I get very different results between caret_5.15-61 +