similar to: Linux refresh x11 window problem

Hi, One thing that has always puzzled me using R, via Emacs/ESS on Debian, is how the graphics windows get (or don't get) redrawn. At the moment I've got four different X11() windows open, arranged to all fit on the screen at the same time. However, I have no idea how to get them all redrawn consistently. What I mean is, if I now switch focus from my main Emacs window to one of the

I've fixed the original report and Tom's first. Someone had incorrrectly arranged for most of the initialization to be done only once per session. I did ask before 1.3.0 what the intention was .... For pseudocolor devices at least this was biting since the palette was not re-initialized. I don't see point two on my system, and Martin's point about interruption was first shown

I have on occasion had the problem of missing title bars on X11 graphics windows when using R, and would like to know what others have found in terms of the occurance, source, or solution of this problem. In searching for information on this I found only the brief thread from last November which I have copied below. Anyone who has experienced this knows it brings a very unwelcome interruption to

Full_Name: Keith Frost Version: 2.1.0 OS: Debian Sarge Submission from: (NULL) (66.162.141.10) This has actually been a problem for some time in R under Linux. (I noticed it under previous builds for Redhat 9 as well.) The graphics device windows produced by the x11() function do not always get redrawn when they should, sometimes leaving the device blank when there should be a graph on it.

Hello, This is an issue that is at the interface of R, X, and my window manager (either icewm or openbox, both latest versions). I am running R 2.10.1 on Ubuntu 9.10. My goal: When an X11 device is started in R (e.g., by simply calling plot), I would like for the resulting window to be in the "always on top" state, and for focus not to switch to it. Configuring this behavior is

R^2 for a model is usually defined as 1-RSS/TSS where TSS is the SS about the mean and RSS is the residual SS from the model. Consider the model in R z <- runif(20) y <- z+rnorm(20) my.model <- lm(y~offset(z)) summary(my.model)$r.squared Here the RSS is equivalent to the TSS and gives 0 when it should (IMHO and a few others perhaps) be 1 - RSS/TSS(corrected for the mean only) RSS =

I apologize if this is too obscure to reproduce, or some idiosyncratic aspects of my system. If I create a plot, e.g., > plot(1:10) I get a graphics device as expected. I then click on the 'zoom' box on my X11 window, so the window expands to occupy the entire screen. The plot is redrawn at the scale of the large window, but is clipped to the 'unzoomed' size. I only

Hi, When I place a legend on a plot it looks exactly as I intended on the screen. However, almost always, when I export this to postscript file, the legend's text protrudes through the legend's frame (the latter being placed correctly). See the appended example code. I can send the EPS file as well for those that are interested (<4 kb; <200 lines). I found nothing in the FAQS,

I'm noticing some differences between making an explicit call to windows() to generate a graphics device and going with whatever R gives you when you just start plotting, which raises the question of just what the nature of the default device is. I've had a hard time researching this so far, so I'm asking the list. Here are two code snippets: ############################### ##

It really is unclear what is claimed to be a bug here. But see https://stat.ethz.ch/pipermail/r-devel/2007-May/045592.html for why the bug is not in R: your old and new data do not match. Your fit is to a category. [The problem with the web interface to R-bugs was reported last week: it is being worked on.] On Mon, 30 Apr 2007, r.darnell at uq.edu.au wrote: > This is a multi-part

Hello, The harddisk of my etch/bristuffed asterisk1.2 box finally died. I moved the cheap (1397:2bd0) HFC-S card to a squeeze host (i686) and built dahdi modules 2.3.0.1 using m-a. After zaptel->dahdi and asterisk 1.2->1.6 config adaptations, everything seems ok, except for the BRI side, unable to bring layers 1/2 up. Asterisk reports: chan_dahdi.c:12393 dahdi_pri_error: 1 Unable to

> From: Ross Darnell > > Liaw, Andy wrote: > >>From: Liaw, Andy > >> > >> > >>>From: Ross Darnell > >>> > >>>A good point but what is the value of storing a large set of > >>>predicted > >>>values when the values of the explanatory variables are lost > >>>(predicted >

I create lots of postscript files which I view with ghostview. The beginning of the files all begin something like %!PS-Adobe-3.0 %%DocumentNeededResources: font Helvetica %%+ font Helvetica-Bold %%+ font Helvetica-Oblique %%+ font Helvetica-BoldOblique %%+ font Symbol %%DocumentMedia: a4 595 841 0 () () %%Title: R Graphics Output %%Creator: R Software The consequence is that in ghostview,

Using R (version 0.63.3) for MS windows, I try the following command > shell(paste("cd ",getenv("RHOME"),sep="")) which replies with an error message Too many parameters - FILES\RW0633 which appears to suggest that the space if the path name is causing difficulties to the cd command. getenv returns > getenv("RHOME") RHOME

I would like to create a page of two graphs (2 rows by 1 col) and then draw vertical lines (segments?) on both graphs from the minimum values to the corresponding maximum value. So I have tried # > y <- rnorm(3000) > par(mfrow=c(2,1)) > plot(y,type="l") > plot(cumsum(y),type="l") > segments(1000,min(cumsum(y)),1000,max(cumsum(y))) > par(mfg=c(1,1)) >

I would appreciate help translating the following lme model to an lmer function. lme(lognrms ~ Group*Rotation*muscle*side*support*arms, random=~1|Subject/Stratum2/rep, data=Data) Many thanks Ross Darnell r.darnell at uq.edu.au

I am relatively new to R, so this may be a much simpler question than it seems to me. I am trying to create a function that includes two summations, and can't figure out how. I am attaching the equation as a pdf file. This function will then be optimized over a chosen range of values, but right now I just need help with the function. Thank you. Zack Darnell Duke University -- Zack

http://bugs.freedesktop.org/show_bug.cgi?id=13993 Summary: Display corruption when using iceWM Product: xorg Version: 7.3 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Nux! wrote: >> From: "m roth" <m.roth at 5-cent.us> >> Sent: Tuesday, 7 November, 2017 15:37:13 > >> So, on my old Netbook, now happily running C6.9, I'm looking for >> opinions for a lightweight window manager. Gnome surely ain't it.... >> Years back, I used to like IceWM, but not sure it's been kept up. >> >> So, opinions?

Has anyone else encountered a loop and failure to shutdown on CentOS4? This has occurred twice in the past month, but unfortunately I failed to write down the looping messages. The only relevant problems I found via Google reference raid controllers, and I have POI (plain ol' IDE). Doh! Obviously I wuill need to record the errors. My environment is run-level 5 with GDM, but I use IceWm