search for: r_batch_options

Hi, Out of laziness I just used "R CMD batch" instead of "R CMD BATCH". I didn't get an error so didn't think about the consequences... One consequence is (at least on Mac OS X 10.11 but probably in more generality) that R_BATCH_OPTIONS are ignored, which was kind of fatal in my case... I am thus wondering whether it makes sense to either a) have R_BATCH_OPTIONS also be respected for "R CMD batch" or b) simply not allow "R CMD batch" as a valid command (so requiring to use "R CMD BATCH"). Both approac...

...1:39, Marius Hofert wrote: > | Out of laziness I just used "R CMD batch" instead of "R CMD BATCH". I > | didn't get an error so didn't think about the consequences... One > | consequence is (at least on Mac OS X 10.11 but probably in more > | generality) that R_BATCH_OPTIONS are ignored, which was kind of fatal > | in my case... I am thus wondering whether it makes sense to either a) > | have R_BATCH_OPTIONS also be respected for "R CMD batch" or b) simply > | not allow "R CMD batch" as a valid command (so requiring to use "R CMD >...

...1:39, Marius Hofert wrote: > | Out of laziness I just used "R CMD batch" instead of "R CMD BATCH". I > | didn't get an error so didn't think about the consequences... One > | consequence is (at least on Mac OS X 10.11 but probably in more > | generality) that R_BATCH_OPTIONS are ignored, which was kind of fatal > | in my case... I am thus wondering whether it makes sense to either a) > | have R_BATCH_OPTIONS also be respected for "R CMD batch" or b) simply > | not allow "R CMD batch" as a valid command (so requiring to use "R CMD >...

...ors like this whenever I try to run R in batch mode: /usr/lib64/R/bin/BATCH: line 52: 7875 Broken pipe ( echo "invisible(options(echo = TRUE))"; cat ${in}; echo ''; echo "proc.time ()" ) 7876 Segmentation fault | ${R_HOME}/bin/R ${opts} $ {R_BATCH_OPTIONS} >${out} 2>&1 I have had the same problem on the linux and osX versions of R. Is this a known bug? Thanks, Aaron Tenney

...ert wrote: >> | Out of laziness I just used "R CMD batch" instead of "R CMD BATCH". I >> | didn't get an error so didn't think about the consequences... One >> | consequence is (at least on Mac OS X 10.11 but probably in more >> | generality) that R_BATCH_OPTIONS are ignored, which was kind of fatal >> | in my case... I am thus wondering whether it makes sense to either a) >> | have R_BATCH_OPTIONS also be respected for "R CMD batch" or b) simply >> | not allow "R CMD batch" as a valid command (so requiring to use &quot...

Is this the right place to report segfaults? spc$ R CMD BATCH driver.q rOut.txt spc$ tail -16 rOut.txt /Library/Frameworks/R.framework/Resources/bin/BATCH: line 60: 5461 Segmentation fault ${R_HOME}/bin/R -f ${in} ${opts} ${R_BATCH_OPTIONS} > ${out} 2>&1 *** caught segfault *** address 0x3f095116, cause 'memory not mapped' Traceback: 1: .Call("La_dgesv", a, b, tol, PACKAGE = "base") 2: solve.default(iV0) 3: solve(iV0) 4: standardGeneric("solve") 5: solve(iV0) 6: w0.fullCond(cur...

...gt;> | Out of laziness I just used "R CMD batch" instead of "R CMD BATCH". I >>> | didn't get an error so didn't think about the consequences... One >>> | consequence is (at least on Mac OS X 10.11 but probably in more >>> | generality) that R_BATCH_OPTIONS are ignored, which was kind of fatal >>> | in my case... I am thus wondering whether it makes sense to either a) >>> | have R_BATCH_OPTIONS also be respected for "R CMD batch" or b) simply >>> | not allow "R CMD batch" as a valid command (so requiring...

Hello I recently submitted an update of a package, and received error reports from CRAN maintainers concerning the pkg/tests section: > Next time you update, can you please ensure that the .Rout.save files > are generated in English (with LANGUAGE=en set). R 2.12.x will ensure > that the tests are run in English, and it saves a lot of unnecessary > chatter if the reference