similar to: if(!CRAN()){...} / Repository policies

> On 25 Apr 2015, at 13:11 , Prof J C Nash (U30A) <nashjc at uottawa.ca> wrote: > > Hendrik pointed out it was the parentheses that gave the complaint. > Single quotes and no parentheses seem to satisfy R CMD check. Perhaps > that needs to be in the WRE. Well, it is in ?toTitleCase: ...However, unknown technical terms will be capitalized unless they are single

On 24.04.2015 22:44, Ben Bolker wrote: > Prof J C Nash (U30A <nashjc <at> uottawa.ca> writes: > >> >> I was preparing a fix for a minor glitch in my optimx package and R CMD >> check gave an error that the title was not in title case. > > [snip] to make Gmane happy ... > >> I have found >> >> A Replacement and Extension of the

I noted Duncan's comment that an answer had been provided, and went to the archives to find his earlier comment, which I am fairly sure I saw a day or two ago. However, neither May nor June archives show Duncan in the thread except for the msg below (edited for space). Possibly tech failures are causing misunderstandings. JN On 14-06-02 06:00 AM, r-devel-request at r-project.org wrote: >

I was preparing a fix for a minor glitch in my optimx package and R CMD check gave an error that the title was not in title case. It is A Replacement and Extension of the optim() Function R CMD check suggests the incorrect form A Replacement and Extension of the Optim() Function 'Writing R Extensions' suggests single quotes, i.e., A Replacement and Extension of the 'optim()'

How about allowing underscore? (I believe WRE is silent on this, and I have not tried submitting a package with underscore in the title.) As I pointed out in my OP, _optim()_ works. And we have the advantage that we can distinguish package from function. The purpose of consistent editing is surely to provide the affordances that save us from needing extra documentation, as per Donald Norman's

Hendrik pointed out it was the parentheses that gave the complaint. Single quotes and no parentheses seem to satisfy R CMD check. Perhaps that needs to be in the WRE. However, I have for some time used the parentheses to distinguish functions from packages. optim() is a function, optimx a package. Is this something CRAN should be thinking about? I would argue greater benefit to users than title

I need to make a graphic to show problems on different parts of chromosomes (think of a graphic showing the number of frayed threads as colors along different parts of a worn out rope). I want to draw bars going from left to right across a page and color different parts of the bars in different shades. Each graphic will need to have several bars of different lenghts corresponding to the

x1<-c(5.548,4.896,1.964,3.586,3.824,3.111,3.607,3.557,2.989,18.053,3.773,1.253,2.094,2.726,1.758,5.011,2.455,0.913,0.890,2.468,4.168,4.810,34.319,1.531,1.481,2.239,4.204,3.463,1.727) y<-c(2.590,3.770,1.270,1.445,3.290,0.930,1.600,1.250,3.450,1.096,1.745,1.060,0.890,2.755,1.515,4.770,2.220,0.590,0.530,1.910,4.010,1.745,1.965,2.555,0.770,0.720,1.730,2.860,0.760)

Ravi Varadhan and I have been looking at UCMINF to try to identify why it gives occasional (but not reproducible) errors, seemingly on Windows only. There is some suspicion that its use of DBLEPR for finessing the Fortran WRITE() statements may be to blame. While I can find DBLEPR in Venables and Ripley, it doesn't get much mention after about 2000 in the archives, though it is in the R FAQ

Ravi Varadhan and I have been looking at UCMINF to try to identify why it gives occasional (but not reproducible) errors, seemingly on Windows only. There is some suspicion that its use of DBLEPR for finessing the Fortran WRITE() statements may be to blame. While I can find DBLEPR in Venables and Ripley, it doesn't get much mention after about 2000 in the archives, though it is in the R FAQ

There are now several R geographic user groups, and a few have mailing lists on the R mailing list system. Thanks to Martin M, there's also a pointer to a page I'm maintaining to list/describe the groups. The page is at http://macnash.telfer.uottawa.ca/RUG.html Contact me if you have a listing. I'm prepared to wikify it if there is sufficient interest. John Nash

hello,friend, first hope everything goes well to you www.shoes159.com is our web. welcome to surf here pls tell me and choose nike shoes/jean/hoody/sweater/t-shirt/jacket/hat/ipod/hangbag/watch model and size u need. i think you will find something you interested,and if you need,pls tell me the order list,and i will confirm for you. and give u reasonable price include shipping fee,and the price

So I pulled the damned string and well, the sweater unraveled pretty hard. There is a WIP branch in the git repository; it doesn't fully build EFI yet, but I think at this point it's mostly just to slog through missing exports and so on. -hpa

On Wed, 26 Jun 2019 at 15:59, Robert Heller <heller at deepsoft.com> wrote: > OK, I recently ugraded to the current ESR release of Firefox for CentOS > 6. > And I am having problems with the user interface (basically it has become > hard > [for me] to use). > > What alternitives are there? (Chrome and Chromium are not possible with > CentOS, and Chrome and Chromium

ok, so let's take stock of things on the first of august... fletcher penney has updated multimarkdown to 3.1... plus he's working on finalizing his editor-app, which it seems he has christened as "multimarkdown composer". brett terpstra is rewriting-from-scratch his "marked" app. ("better sooner than later", he says.) from my experience, i decide to

Hi - I had a client recently move their asterisk system (asterisk 1.4.26, dahdi 2.2.0.1, aex800 w/vpm module) to a "new" location, a building that's nearly 150 years old. I was not personally able to go there, but the person who did the move said the building's demarc room was "scary"-- water leaks, jumbled and frayed wiring, and all sorts of other fun. The echo on

On Mon, Oct 22, 2012 at 02:05:17PM +0200, Sven Verdoolaege wrote: > On Sun, Oct 21, 2012 at 03:52:39PM -0700, Tobias Grosser wrote: > > On 10/21/2012 03:46 PM, Jack Howarth wrote: > > >Is there a schedule for releasing updated tarballs for isl and cloog? > > > > I am not aware of a concrete schedule, but I believe Sven (copied) > > was planning to release a new

predict.warn() -- a function to display factor levels in new data for linear model prediction that do not exist in the estimating data. Date: 2005-8-24 From: John C. Nash (with thanks to Uwe Ligges for suggestions) nashjc at uottawa.ca Motivation: In computing predictions from a linear model using factors, it is possible to introduce new factor levels. This was encountered on a practical

I've been creating some R tools that manipulate objective functions for optimization. In so doing, I create a character string with R code, and then want to have it in my workspace. Currently -- and this works fine -- I write the code out, then use source() to bring it in again. Example: cstr<-"jack<-function(x){\n cat(\"Silly x:\")\n print(x) \n }\n" write(cstr,

I spent more time than I should have debugging a script because I wanted x<-seq(0,100)*0.1 but typed x<-seq(O:100)*0.1 seq(0:100) yields 1 to 101, Clearly my own brain to fingers fumble, but possibly one others may want to avoid it. JN