Displaying 20 results from an estimated 100 matches similar to: "Warnings generated by log2()/log10() are really large/takes a long time to display"
2006 May 05
4
str() with attr(*, "names") is extremely slow for long vectors
Hi,
I noticed some time ago that, for instance, named vectors that are
really makes str() really slow when displaying the names attribute. I
don't know exactly when this started, but it wasn't the case say 1-2
years ago. Example (on a WinXP 1.8GHz):
> s <- 1:1000; names(s) <- s
> system.time(str(s))
Named int [1:1000] 1 2 3 4 5 6 7 8 9 10 ...
- attr(*, "names")=
2005 Jul 15
2
R v2.1.0 patched (>2005-05-09) for Windows?
I'm trying to troubleshoot a case where R crashes on Windows. It does
not occur at all with my R v2.1.0 patched (2005-05-09), but happens on R
v2.1.1 (patched or non-patched) in many different cases. The R
v2.2.0dev (2005-07-15) also got this problem (although it won't crash on
the below example). I previously reported this
2007 May 14
1
Native implementation of rowMedians()
Hi,
I've got a version of rowMedians(x, na.rm=FALSE) for matrices that
handles missing values implemented in C. It has been optimized for
memory and speed. To avoid coercing integers to doubles, and hence
allocate an additional 200% memory, there is one C function for
integers and one for doubles.
The rowMedians() implementation is currently sitting in my non-CRAN
package R.native
2005 Dec 14
1
About help on 'mahalanobis'
Hi,
help on 'mahalanobis' (in the stats package in Rv2.2.0) now says:
"Description:
Returns the Mahalanobis distance of all rows in 'x' and the vector
mu='center' with respect to Sigma='cov'. This is (for vector 'x')
defined as
D^2 = (x - mu)' Sigma^{-1} (x - mu)"
It does return D^2 as written. However,
2002 Feb 20
2
How to get the penalized log likelihood from smooth.spline()?
I use smooth.spline(x, y) in package modreg and I would like to get
value of penalized log likelihood and preferable also its two parts. To
make clear what I am asking for (and make sure that I am asking for the
right thing) I clarify my problem trying to use the same notation as in
help(smooth.spline):
I want to find the natural cubic spline f(x) such that
L(f) = \sum_{k=1}{n} w[k](y[k] -
2007 Aug 29
1
R CMD check recursive copy of tests/
>From NEWS of R v2.6.0 devel:
o R CMD check now does a recursive copy on the 'tests' directory.
However, R CMD check does not run *.R scripts in such subdirectories
(as I thought/hoped for), only those directly under tests/, This may
or may not be intentional. If true, maybe the above should be
clarified as:
o R CMD check now does a recursive copy on the 'tests' directory
2009 Nov 11
2
typo in docs for unlink()
The VALUE section in the help for 'unlink' says:
| 0| for success, |1| for failure. Not deleting a non-existent file is
not a failure, nor is being unable to delete a directory if |recursive =
FALSE|. However, missing values in |x| result are regarded as failures.
The last phrase doesn't make sense to me. Should it be either "missing
values in x are regarded as
2010 Mar 28
2
Setting up TortoiseSVN and PuTTY on Windows for r-forge.r-project.org (Was: Re: Using SVN + SSH on windows)
Here are some notes/observations I've done on my setup that works for
me. Hopefully it will be added to some r-forge documentation/wiki.
I use:
Windows Vista Business SP2 32bit
TortoiseSVN 1.6.7 (Build 18415 - 32 Bit , 2010/01/22 17:55:06)
PuTTY v0.60 (with Pageant v0.60)
I have a deprecated r-forge project ('r-oo') that I will use through
out. My r-forge username is
2014 Dec 06
1
R CMD check --as-cran and (a)spell checking
Does anyone know if it is possible to add a dictionary file of known
words that becomes part of the *built* package to tell 'R CMD check
--as-cran' not to report these words as misspelled. I want this
dictionary to come with the *.tar.gz such that it will be available
regardless where the package is checked. For instance, currently I
get:
* using log directory
2001 Mar 22
1
Call by reference: Was: Object orientation?
To reply to Yves Gauvreau question (Jan 24, 2001) about how to set values
within function, it is possible to do without without using the "<<-"
assignment operator or other nasty tricks. I had the same problem and I did
a nasty workaround two weeks ago implementing the functionality of reference
variables, but today I "ran into" the [R] help page for ".Alias".
2001 Mar 07
1
Minor bug in maketitle.pl (with bug correction) (PR#864)
Full_Name: Henrik Bengtsson
Version: rw1022
OS: Windows Me
Submission from: (NULL) (216.175.126.55)
When ${R_HOME}/share/perl/maketitle.pl tries to generate a TITLE that is longer
than $lc-3 (=13) characters long, it repeats the package name on line two.
Example: Now it generates an output like:
com.braju.graphics
com.braju.graphics Bla bla bla...
But, I believe it should
2001 May 08
1
ASCII map?
Is there a way to convert between and integer and a character and vice
versa? For instance
i <- 65;
ch <- intToChar(i); # "A"
i <- charToInt(ch); # 65
or even better
i <- c(65, 66);
ch <- intToChar(i); # c("A", "B")
i <- charToInt(ch); # c(65, 66)
I have tried to do a ASCII map myself, and I figured out that the ASCII
2001 Jun 30
1
Rd tag \link not working without \code (PR#1006)
Full_Name: Henrik Bengtsson
Version: 1.3.0
OS: Windows Me
Submission from: (NULL) (216.175.124.18)
Even though I know the Rd format might be replaced soon, I am report this just
in case:
The package optional argument for \link is *only* used when \link is in a \code
environment. Example:
1) This link works: \code{\link[base]{cat}}
2) But not this one: \link[base]{cat}
It looks like the
2001 Jul 06
1
Title of bundled packages in the library index (PR#1017)
Full_Name: Henrik Bengtsson
Version: 1.3.0
OS: Windows Me
Submission from: (NULL) (216.175.122.171)
I realized that the title of packages in the library index when they are in a
bundle is the title of the bundle and not the package.
It looks like the TITLE file, which apparently is used for generating the
library index, takes the value of the bundle's title and not the package's
title.
2011 Aug 30
0
[LLVMdev] exp2 and log2 intrinsic expansion
I'm having a problem when generating the following LLVM intrinsics:
@llvm.exp2.f32
@llvm.log2.f32
On linux, these are available on as part of standard math libraries, the
code geenrator expands them into library calls, and the linker happily finds
them. However, on Windows and OSX, where no implementation exists, instead
of throwing a runtime error, we get a call to a function with a null
2003 Oct 29
1
I have a problem with the log2 function
Dear R users,
according the help(log), the function
log2(x) should give the natural logarithm of x.
I expect in case of x=2 to to get 0.6931, however, R gives me 1 as a result.
Similar, logb(2,2) gives 1 again.
I'm wondering if I have missed something ?
Yours
Frank
--
Frank Mattes, MD e-mail: f.mattes at ucl.ac.uk
Department of Virology fax 0044(0)207 8302854
Royal Free Hospital
2010 Mar 10
1
log2(quote(1:10)) evaluates the quoted 1:10, log() does not
This is very minor, but shouldn't log2(quote(1:10))
throw an error,the same as log() and other math functions
do? It looks like log2 and log10 evaluate a call object
instead of throwing a non-numeric-argument error. They
do object to non-call language objects, like expressions.
> log2(quote(1:10))
[1] 0.000000 1.000000 1.584963 2.000000 2.321928 2.584963
[7] 2.807355 3.000000
2007 Nov 20
1
xy.coords and log10
Is there a way to teach xy.coords, when given log="xy", or just "x"
or "y" separately, to do a decimal log10 instead of the natural log?
Cheers,
Alexy
2011 Aug 28
2
-log10 of 0
Dear R users:
Sorry for this simple question:
I am writing a function where I would need to pickup p values and make
-log10 of it.
The p values are from an anova output and sometime it can yield me 0.
-log10 (0)
[1] Inf
I can not replace Inf with 0, which not case here.
This is restricting me to go further in the function and out me the error.
You help is highly appreciated.
Thanks;
--
2007 Aug 07
1
lm( ) for log10-transformed data
Dear help-list,
I would like to perform a linear regression on the log10 of the two
vectors ov.mag.min and res.600nm. The slope and intercept of the
regression I use to plot a wider range of ov.mag.min in a double log plot.
For a linear regression on only tow points, wouldn't I expect the
results for two.points.min to match pretty exactly res.600nm? It does
not seem to be the case here.