Displaying 20 results from an estimated 9000 matches similar to: "Histogram for factors"
2000 May 08
3
eigen broken on AIX with R-devel? (PR#537)
Hi, I get the wrong eigen values on an AIX machine with R-devel of 5/3/00.
Here are the results:
R> m <- matrix (c(6.8, 2.4, 2.4, 8.2), nrow=2)
R> m
[,1] [,2]
[1,] 6.8 2.4
[2,] 2.4 8.2
R> eigen(m)
$values
[1] 19.281403 6.337993
$vectors
[,1] [,2]
[1,] 0.1918866 0.9967987
[2,] 0.9967987 -0.1918866
And for comparison, here is what I get on a Sun (with
2001 Sep 07
2
Why does substr<- truncate and not replace...
... when the replacement string is shorter than the portion of the
string to be replaced?
The documentation to substr (in R 1.3.1) gives me:
If the portion to be replaced is longer than the replacement
string, then only the portion the length of the string is
replaced.
And so I try:
R> x <- "abcdef"
R> substr(x,2,3) <- "xy" #ok
R> x
[1]
2001 Sep 07
2
Why does substr<- truncate and not replace...
... when the replacement string is shorter than the portion of the
string to be replaced?
The documentation to substr (in R 1.3.1) gives me:
If the portion to be replaced is longer than the replacement
string, then only the portion the length of the string is
replaced.
And so I try:
R> x <- "abcdef"
R> substr(x,2,3) <- "xy" #ok
R> x
[1]
2001 Sep 07
2
adding logical vector to data frame
Hello. I'm afraid that I'm missing something very obvious this
afternoon...
When I add a column to a data.frame (by assigning to a "new" column
name a logical vector), I thought that I had (at least) 3 options to
do so:
R> j <- data.frame (x=1:2)
R> j$y <- c(TRUE,FALSE) #assignment 1
R> str(j)
`data.frame': 2 obs. of 2 variables:
$ x: int 1 2
$ y: logi
2000 Mar 18
3
AIX fails on startup with R-1.0.0
Hi,
this is not a bug report since this may not be a problem with R per se.
The current release of R (1.1.0) will compile cleanly on an AIX box
(I have 4.3.2) but it will fail upon startup with an Illegal
Instruction. I've located the problem to be in do_strsplit when R
calls regcomp.
This function is defined in regex.c. However, the text from regex.o
doesn't find its way into the
2001 Jan 30
1
Disappearing x axis in plot.factor (PR#830)
Hi.
While there is an x-axis set up for:
> plot.factor(factor(1:3))
this axis is not present for
> plot.factor(factor(1:3), col="red")
which actually should just be the same as the first plot and call
barplot(table(.)), shouldn't it? Where did the ticks and labels go?
Note that
> barplot (table(factor(1:3)), col="red")
has the x-axis.
Something funky is going
1999 Jun 09
1
R on AIX (>4.2)
Hi,
I'm determined to get R compiling & running on a machine running AIX
4.2. I've seen previous emails in the archive about this topic. The
main obstacle is getting dynamic loading to work, but it works for Tcl
and hence is feasable.
Questions:
- is anybody _currently_ working with R on AIX?
- why have previous fixes to the sources not been introduced into
the released
1999 Jun 09
1
R on AIX (>4.2)
Hi,
I'm determined to get R compiling & running on a machine running AIX
4.2. I've seen previous emails in the archive about this topic. The
main obstacle is getting dynamic loading to work, but it works for Tcl
and hence is feasable.
Questions:
- is anybody _currently_ working with R on AIX?
- why have previous fixes to the sources not been introduced into
the released
2001 Jan 30
1
screen can't go back to log="y" plot (PR#831)
[I have abbreviated the subject as jitterbug has been having probems
with long subjects.]
The issue here is that one cannot mix log/non-log axes in the calls to
screen(), as the appropriate par() parameter is read-only, but the
meaning of yaxp depends on it. But beyond that you can't set
x/yaxp for log axes.
You should be able to do this: you can in the S original.
A simpler version:
plot
2001 Feb 03
1
tk non-widget commands (esp. update and winfo)
Hi,
I've been playing with the tcltk package. It's very nice to have
access to buttons, menus etc. now. Thank you!
Alas, I also have questions: In Tcl everything is a string [*]. This
is not the case in R, of course. So why are return values of tk
commands still strings? (Is there any other reason than speed or
"package is work in progress"?)
Example:
> tt <-
2001 Feb 06
2
X11 warnings about "wrong" font sizes (PR#840)
Hi. This is cosmetic in nature, yet annoying as the warning points
to the wrong source: On a screen running on an X server with 100 DPI,
I always got warnings about X11 using the wrong font size:
> x11()
Warning message:
X11 used font size 17 when 12 was requested
Then I looked at the code and X11 is _not_ to be blamed for this:
R resets the requested font size for 100 DPI screens! There
2001 Feb 14
2
help with tcltk
Hallo!
Can anyone explain to me how to add a vert. scrollbar to a listbox using tcltk please?
Thanks
--
Frank Gerrit Zoellner
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject
2000 Mar 07
4
Error compiling R on RS6000 (PR#475)
Full_Name: Paul Gutwin
Version: R-1.0.0
OS: AIX 4.2.1
Submission from: (NULL) (198.133.22.67)
R-1.0.0 fails to compile. I'm using the config.cache file from a successful
compliation of R-0.65.0 (prob #290, fixed thanks to Thomas Vogels @ CMU).
Compiling R-1.0.0 fails with the following error messages:
make
Target "R" is up to date.
gcc -I. -I../include -I../../src/include
2000 Apr 07
1
x11 colortype problems ('gray' is broken?) (PR#512)
Hi,
I occasionally run out of color in my X11 terminal. At this
point, R will issue this error message:
Error: X11 cannot allocate additional graphics colors.
Consider using colortype="pseudo.cube" or "gray".
An immediate x11(colortype="pseudo.cube") doesn't work as the
colortype seems to be shared among the different x11 plotting windows.
So I have
2000 Apr 07
1
how to send a bug report within ESS
Hi,
I just tried to send a bug report within an ESS session in emacs.
bug.report() simply returned quietly, giving no indication what it
did or didn't whatsoever. (I hope you don't see empty emails
because of this in R-bugs.)
What's the preferred way to send a bug.report? Shouldn't it work
with method="ess"? Also, I keep forgetting this, what's the
1999 Jun 10
1
running R on AIX (>= 4.2)
(Was: r-help -- dynload for R on AIX)
Thanks for all the responses. Let's see:
- I found the dynload.c posted by Arne (April 99, I believe). If
the difference to the current version of dynload.c is too big,
then the current dynload.c is a better starting point. Otherwise
#ifdef's won't be feasible.
- One problem appears to be the list of exported symbols.
2000 Jun 16
2
Missing -lm for tcltk (R 1.1.0, AIX 4.3) (PR#573)
> From: tov@phoenix.ece.cmu.edu
> Date: Fri, 16 Jun 2000 16:32:36 +0200 (MET DST)
> To: r-devel@stat.math.ethz.ch
> Subject: [Rd] Missing -lm for tcltk (R 1.1.0, AIX 4.3) (PR#573)
> CC: R-bugs@biostat.ku.dk
> X-Loop: R-bugs@biostat.ku.dk
>
> Hi,
>
> ok, AIX 4.3 insists on being different. I can't compile --with-tcltk
> out of the box. I have to add
1999 Jun 10
2
dynload for R on AIX (>= 4.2)
On Thu, 10 Jun 1999, Friedrich Leisch wrote:
> Yes, if I understood AIX workings correct you have to have a text file
> of to-be-exported symbols at the time of linking a shared library,
> i.e. the linker is called like (this is pasted from a mail by Arne)
>
> $(F77) -o module.so -bM:SRE -bE:module.exp -bnoentry $(OBJECTS) $(LIBDIR) $(LIBS)
>
> where module.exp is a text
2001 Jul 29
4
style question: returning multiple arguments - structure orlist
I see Thomas has already nailed this one, so it becomes a non-issue.
Nevertheless I feel moved to say I think the idea would have been a step in
the wrong direction in the first place. It comes from a desire to make R
behave "a bit more like matlab" and that is ultimately unhelpful.
Having tried to teach generations of students how to use the system (S-PLUS,
but it could equally well
2001 Feb 13
1
X11 device doesn't handle destroy events correcly (PR#848)
Hi, there are two problems in devX11.c. The one is an undocumented
nuisance and the other isn't a bug until you try to embed an X11
device in another window (think tktoplevel() in tcltk package...).
Let's take a look at locator() first: Assuming you call locator() with
a current X11 device, this call is handled in X11_Locator
(src/unix/X11/devX11.c). When you have one window open and