Displaying 3 results from an estimated 3 matches for "do_match".
Did you mean:
no_match
2001 Nov 20
2
is match slow?
I'm doing
m <- match(matriz, origen, 0)
where matriz is a 270x900 matrix and
origen a 11675 elements vector, and is taking
a very long time.
Is match a function
implemented in C? If not, would a C
code be faster?
Thanks
Agus
Dr. Agustin Lobo
Instituto de Ciencias de la Tierra (CSIC)
Lluis Sole Sabaris s/n
08028 Barcelona SPAIN
tel 34 93409 5410
fax 34 93411 0012
alobo at ija.csic.es
2000 Nov 20
2
precision, incorrect(?) tapply() NA's
Hi,
Summary:
I ran into some unexpected behavior in approx() and tapply()
that introduced NA's in "clean" data due to (?) numerical accuracy/round off.
The culprit seems to be in match() that coerces it's arguments to character,
loosing precision in the process.
[R development version 1.2.0, 08 Nov 2000, on Linux]
Example:
> r
> [1] 0.6931472 0.6931472 0.6931472
2000 Nov 20
2
precision, incorrect(?) tapply() NA's
Hi,
Summary:
I ran into some unexpected behavior in approx() and tapply()
that introduced NA's in "clean" data due to (?) numerical accuracy/round off.
The culprit seems to be in match() that coerces it's arguments to character,
loosing precision in the process.
[R development version 1.2.0, 08 Nov 2000, on Linux]
Example:
> r
> [1] 0.6931472 0.6931472 0.6931472