search for: nashjc

> 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 c...

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...

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

...t; Bill Dunlap > TIBCO Software > wdunlap tibco.com <http://tibco.com> > > On Mon, Jul 30, 2018 at 11:35 AM, J C Nash <profjcnash at gmail.com <mailto:profjcnash at gmail.com>> wrote: > > In looking at rootfinding for the histoRicalg project (see gitlab.com/nashjc/histoRicalg > <http://gitlab.com/nashjc/histoRicalg>), > I thought I would check how uniroot() solves some problems. The following short example > > ff <- function(x){ exp(0.5*x) - 2 } > ff(2) > ff(1) > uniroot(ff, 0, 10) > uniroot(ff, c...

In looking at rootfinding for the histoRicalg project (see gitlab.com/nashjc/histoRicalg), I thought I would check how uniroot() solves some problems. The following short example ff <- function(x){ exp(0.5*x) - 2 } ff(2) ff(1) uniroot(ff, 0, 10) uniroot(ff, c(0, 10), trace=1) uniroot(ff, c(0, 10), trace=TRUE) shows that the trace parameter, as described in the Rd file...

...us to the project. As a first task, I am hoping to establish a "Working Group on Algorithms Used in R" to identify and prioritize issues and to develop procedures for linking older and younger workers to enable the transfer of knowledge. Expressions of interest are welcome, either to me (nashjc _at_ uottawa.ca) or to the mailing list (https://lists.r-consortium.org/g/rconsortium-project-histoRicalg). A preliminary web-site is at https://gitlab.com/nashjc/histoRicalg. While active membership of the Working Group is desirable, given the nature of this project, I anticipate that most member...

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

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()'

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,

...ings, or Turn Signals are the Facial Expressions of Automobiles. Changing the name of a function in a case-sensitive computing language may not be a bug, but it is asking for trouble. JN On 15-04-25 07:57 AM, peter dalgaard wrote: > >> 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, unk...

...e tools (the three codes at the top are based on papers all of which now qualify for >50 years old) seems inconsistent with other messages. For information: I'm coordinating a project to build understanding of what older algorithms are in R as the histoRicalg project. See https://gitlab.com/nashjc/histoRicalg. We welcome participation. Best, JN On 2019-03-04 7:59 a.m., Jim Hester wrote: > Conversely, what is the process to remove a package from core R? It seems > to me some (many?) of the packages included are there more out of > historical accident rather than any technical need...

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

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 level in forecasting retail sales where certain events had not occurred during the estimation period but did occur during the val...

...n 'testing' binaries for amd64 and i386 that are continuously updated as new packages appear on CRAN. With that 'apt-get install r-cran-foo' becomes a reality for almost every value of foo out of the set of CRAN packages. | | On Thu, Sep 10, 2009 at 1:50 PM, Prof. John C Nash <nashjc at uottawa.ca> wrote: | > Subject: Non-GPL packages for R | > | > Packages that are not licensed in a way that permits re-distribution on | > CRAN are frequently a source of comment and concern on R-help and other | > lists. A good example of this problem is the Rdonlp2 package th...

...ons 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 case. JN On 15-04-24 06:17 PM, Uwe Ligges wrote: > > > 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...

It may be worth noting that both Avraham and I are members of the histoRicalg project (https://gitlab.com/nashjc/histoRicalg) that has some modest funding from R-Consortium. The type of concern this nlminb thread raises is why the project was proposed. That is, older codes that may predate IEEE arithmetic and modern programming language processors often were built with a different understanding of how algorit...

...materials and I'll try to arrange for presentation. As an example, I'll show a 2-line script that draws multi-page graphs (e.g., stock market trades by the minute for last month over 10 by 2 sheets of paper). Please share this with others who may be interested. Cheers, John Nash <nashjc at uottawa.ca> ==================================================================================== La version fran?aise suit le texte anglais. ------------------------------------------------------------------------------------ This email may contain privileged and/or confidential in...{{dro...

...es if this is posted twice. The r-help mailing system gave an error (reported to moderator) on first try, but it may have gone through. ---------------------------- Original Message ---------------------------- Subject: Re: R-help Digest, Vol 95, Issue 17 From: "Prof. John C Nash" <nashjc at uottawa.ca> Date: Mon, 17 January, 2011 1:04 pm To: r-help at r-project.org Cc: ligges at statistik.tu-dortmund.de jinruixu at umich.edu -------------------------------------------------------------------------- For those issues with optimization methods (optim, optimx,...

I'm inclined to agree with the view that the "precision" of a generator should be highlighted better in the manual pages. When I do ?runif I don't see a mention, but ?.Random.seed DOES give the info, as Duncan points out, and it is suggested to look there. A 1-liner with each random number generator "CAUTION: random number generators use different mechanisms and