Displaying 10 results from an estimated 10 matches for "historicalg".
Did you mean:
historical
2018 Jun 05
0
histoRicalg -- project to document older methods used by R and transfer knowledge
After some thought, I decided r-devel was probably the best of the R lists
for this item. Do feel free to share, as the purpose is to improve documentation
and identify potential issues.
John Nash
The R Consortium has awarded some modest funding for "histoRicalg",
a project to document and transfer knowledge of some older algorithms
used by R and by other computational systems. These older codes
are mainly in Fortran, but some are in C, with the original implementations
possibly in other programming languages. My efforts
were prompted by finding some...
2018 Jul 30
2
trace in uniroot() ?
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 paramet...
2019 Mar 04
2
Package inclusion in R core implementation
...for current version, so
hanging on to antique 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 a...
2018 Aug 13
1
trace in uniroot() ?
...ally figure that out.
>
>
> 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...
2019 Feb 08
0
nlminb with constraints failing on some platforms
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 dif...
2019 Mar 04
0
Package inclusion in R core implementation
...ng on to antique 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 th...
2018 Aug 13
0
trace in uniroot() ?
...lled (e.g. in
a line search
or in derivative estimation), but some plotting or other postprocessing can
ususally figure that out.
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Mon, Jul 30, 2018 at 11:35 AM, J C Nash <profjcnash at gmail.com> wrote:
> 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...
2019 Mar 04
1
Package inclusion in R core implementation
...on to antique 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 pa...
2019 Feb 06
2
nlminb with constraints failing on some platforms
> On 6 Feb 2019, at 10:58, Martin Maechler <maechler at stat.math.ethz.ch> wrote:
>
.....
> ---------------------------------------------------------------------------
>
> I summarize what has been reported till:
>
> Failure in these cases
> ========
> 1. Kasper K ("Scientific Linux", self compiled R, using Intel's MKL
> for BLAS/LAPACK)
2019 Feb 28
3
Package inclusion in R core implementation
Hi,
It sometimes happens that some packages get included to R like for example
the parallel package.
I was wondering if there is a process to decide whether or not to include a
package in the core implementation of R?
For example, why not include the Rcpp package, which became for a lot of
user the main tool to extend R?
What is our view on the (not so well known) dotCall64 package which is an