similar to: Bug list summary (automatic post)

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

I like to have a continuously running R process, which can receive a dataframe from a client (over TCP/IP), does some processing, and sends some data back. What is the prefered way to do this? Using the socket interface? Using omega's CORBA stuff? Does anyone has example code for doing so? Thanks for any help Regards -- Dr. Jens Oehlschl?gel-Akiyoshi Analyse MD FACTORY GmbH Gr?nstr. 15

Sorry, I was commenting on the previous windows version (version file says 0.5a) (the first one which ran under RW.1.0.0) I have Win NT 4.0 Service pack 5 and R is > version _ platform Windows arch x86 os Win32 system x86, Win32 status major 1 minor 0.0 year 2000 month February day 29 language R > -----Original Message----- > From: Prof Brian

Hi Martin, Great that you follow this. My original intention was to be able to translate colornames to hsv because this would allow using colornames to cut out a certain part of the colorwheel for colorcoding (HSV component H, see my code below) I think internally we might have colors represented as Colornames, ColorIntegers, ColorHexcodes, ColorRGBs, ColorHSVs (ColorCMYs?) however the R-user

I couldn't find this in online help or the archives: Is there any R function or object giving the mapping of the colornames as given by colors() into the hsv() model? Regards -- Dr. Jens Oehlschl?gel-Akiyoshi MD FACTORY GmbH Bayerstrasse 21 80335 M?nchen Tel.: 089 545 28-27 Fax.: 089 545 28-10 http://www.mdfactory.de

I couldn't find this in online help or the archives: Is there any R function or object giving the mapping of the colornames as given by colors() into the hsv() model? Regards -- Dr. Jens Oehlschl?gel-Akiyoshi MD FACTORY GmbH Bayerstrasse 21 80335 M?nchen Tel.: 089 545 28-27 Fax.: 089 545 28-10 http://www.mdfactory.de

I observed the following difference: > ddd <- data.frame(a=1:3, b=1:3) # assignment of 'X' silently ignored > ddd[1,1] <- 'X' > is.factor(ddd[[1]]) [1] FALSE > ddd a b 1 1 1 2 2 2 3 3 3 # assignment of 'X' not ignored > ddd[[1]][1] <- 'X' > is.factor(ddd[[1]]) [1] TRUE > ddd a b 1 X 1 2 2 2 3 3 3 Regards > version

I have a question concerning memory. I understood that R takes a fixed amount of memory at startup (which I can influence with --vsize --nsize) and that gc() shows the memory still free of the total memory reserved for R. However, if I create a long vector of character data, gc() only seem to reflect the space needed for a vector of pointers to char, the space used for the character data itself

I observe dificulties with using data.frame(I(matrix)) > mat <- matrix(letters, 2, 2) > dimnames(mat) <- list(c(1:2), c("x","y")) > mat x y 1 "a" "c" 2 "b" "d" > dd <- data.frame(I(mat)) > ddd I.mat..x I.mat..y 1 a a 2 b b 3 c c doesn't look too bad, but, has

Here is a possible BUG with as.data.frame() and/or [.data.frame which broke Michael Lapsleys RODBC-Code. Can anyone confirm it is a bug or a 'feature' of the prototype? tablename <- "abc" a <- as.data.frame(cbind("abc", 1:3)) b <- as.data.frame(cbind(tablename, 1:3)) # ok > a V1 V2 1 abc 1 2 abc 2 3 abc 3 # missing column name > b tablename 1

Dear all, In RW0901 I could > dates("01/01/2000") [1] 01/01/100 where only the printing was wrong, but the double numeric representation of the chron object was calculated correctly but now in RW0990 > dates("01/01/2000") Error in fun(yy, ...) : must be 2-digit (numeric) year specification and also the followig doesn't help > dates("01/01/2000",

--Multipart_Wed_Feb__4_12:25:40_1998-1 Content-Type: text/plain; charset=US-ASCII Jim, I am relating your message to R-devel. This should be discussed in a broader audience; I am not an expert on GLM's, I know you are and others on this group also... R-develers, please CC to Jim Lindsey (on this topic), since he hasn't been part of the R-devel list for a while.. BTW: I will be gone

-- Happy holidays! -- Dear R Development Core Team, I want to thank you *very much* for the new "Writing R Extensions" manual published with RW0.901 and hope this is the right place to report some possible typos. page 17, example given in the middle of the page, I think it should read REAL(version) = 3.0; ^^^^^^^ page 23, second example, I think the parameter definition

R-devel Digest Monday, September 24 2001 Volume 01 : Number 314 In this issue: [Rd] R 1.3.1 fails 'make check' on arm in the Bessel example (PR#1097) [Rd] Bug list summary (automatic post) [Rd] (PR#1089) Can be closed See the end of the digest for information about r-devel-digest ---------------------------------------------------------------------- Date: Fri, 21