similar to: R source issue "sarge" or "stable"

You've omitted a comma. races2000 is a data frame, which for purposes of extracting rows behaves like a 2-dimenional object. The following works fine: hills2000 <- races2000[races2000$type == 'hill', ] Additionally, you might like to ponder > type <- races2000[names(races2000)=="type"] > type[1:4] Error in "[.data.frame"(type, 1:4) :

(See DAAG book, p. 173, ex. 3) I'm a new user of R, and I'm following the DAAG text. I want to create a subset of the races2000 data frame, but get errors because of a mismatch of values in some columns: > library(DAAG) > attach(races2000) > hills2000 <- races2000[races2000$type == 'hill'] Error in as.matrix.data.frame(x) : dim<- : dims [product 770] do not

R version: 2.0.0 OS: Fedora Core 1 When I'm using Fedora Core 1, Rplots.ps (and subsequent Rplots.pdf created after using ps2pdf Rplots.ps) which are created from the command line execution of R are too large to fit on a US Letter sized page when printed. The same code will produce a US letter sized page when I'm on my Debian Sid box. Both boxes are connected to the same shared

I've recently installed Ubuntu 5.10 on a desktop and need R installed, however, even after uncommenting the repos associated with universe, backports and multiverse, the packages available for Ubuntu are somewhat out of date: clint at simba:~$ apt-cache policy r-base r-base-core r-base: Installed: (none) Candidate: 2.1.1-1 Version table: 2.1.1-1 0 500

I've recently installed Ubuntu 5.10 on a desktop and need R installed, however, even after uncommenting the repos associated with universe, backports and multiverse, the packages available for Ubuntu are somewhat out of date: clint at simba:~$ apt-cache policy r-base r-base-core r-base: Installed: (none) Candidate: 2.1.1-1 Version table: 2.1.1-1 0 500

I've installed Ubuntu 5.10 Breezy on my Mac. When using MacOSX, I used to work with R 2.2.1, but now, with Ubuntu, I can't download it with synaptic. I can only download R 2.1.1-1, and I really need 2.2.1. I've tried to edit the sources.list file, typing deb http://cran.R-projet.org/bin/linux/debian stable/ R/r, using a different mirror,... but when I run synaptic, it says: W:

When I combine separate vectors into one list, there are new names created. I'd like to change them to something more meaningful. Here are two examples using data(zelazo) from library(ISwR): > library(ISwR) > data(zelazo) > attach(zelazo) > zelazo $active [1] 9.00 9.50 9.75 10.00 13.00 9.50 $passive [1] 11.00 10.00 10.00 11.75 10.50 15.00 $none [1] 11.50 12.00 9.00

A data set I obtained has the hours running from 01 through 24 rather than the conventional 00 through 23. My favorite, strptime, balks at hour 24. I thought it would be easy to correct but it must be too late on Friday for my brain and caffeine isn't helping. TIA for a hint, Clint -- Clint Bowman INTERNET: clint at ecy.wa.gov Air Quality Modeler INTERNET: clint at math.utah.edu

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 if you see >f it is doing something to the file. At least a delta-xfer. If it was just a metadata change it would show cf. If you see an >fc without a t then that is an example where rsync found a file that didn't match even though the timestamps did. That isn't supposed to happen very often. On 10/28/2015 01:19 PM, Clint Olsen

I just joined this mail-list, so I apologize if this has been discussed before, but: Has anyone suggested adding a "todo list notation" to Markdown? Specifically, I'd like to see an open paren, brace or bracket, at the start of a line, followed by a space, a "/", or a "X", followed by a matching closing paren, brace, or bracket, followed by a space and more text

I have a large data structure that looks like: > strsplit(st,",")[14395] [1] "KGEG" [2] "SA => KGEG" [3] "72785" [4] "47.62139" [5] "-117.52778" [6] "723" [7] "WA" [8] "US" [9] "2" [10] "SPOKANE SPOKANE INTERNATIONAL AIRPORT" [11] "1" I'd like to be able to

I have shapefiles for the state climatic divisions for the United States and read.shape brings them in wonderfully. Now I wish to run through a list of several thousand observation sites to find out in which division each is located. I figure that I can compute the winding number for each site and be done. However a search doesn't find any references and I can't find a winding number

The US water year extends from 01 October yyyy-1 through 30 September yyyy and is referenced by the year starting on the included 01 January yyyy. I'd like to be able to find the annual means for the water year. To do so I've taken the input date-time, which is in the usual format "1991-10-07 10:35:00" changed it by: w$d<-as.POSIXct(w$date.time) Now I can add an

I have a 2 by 226200 table, conveniently read in by read.table(), which exhibits some strange behavior when plotted by plot(V1,V2). The general pattern for the range of windspeeds, [0<V1<50] is as expected -- the wind gust falls in the interval [V1<V2<65] except for certain values of V2. For V2 == c(15,26,37,48,59), the V2 values are positioned at one-tenth of the V1 (i.e., as if I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If it seeing the files as new then I agree that stat won't help. It might have explained some other itemize output. Since it is seeing the files as new then they must not be where it is looking. Meaning that your link-dest parameter must not be appropriate for your target. On 01/10/2015 08:49 PM, Clint Olsen wrote: > On Sat Jan 10 2015 at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What does --itemize-changes say about that file? Try using the stat command on the various copies of it to see what is different about them. On 01/09/2015 09:42 PM, Clint Olsen wrote: > Hi: > > I've been using rsync for a couple years now. Unfortunately, I've > made some changes on both ends, so it's unclear what could be

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --checksum generally takes a lot longer than --size-only. A delta transfer generally goes quicker than a checksum. However, if you want to make a list of what is corrupt a checksumming utility that is less stupid than rsync can be useful. I say that because rsync's - --checksum is entirely unintelligent. It will checksum every single file on

found by Christian T. Steigies <cts@debian.org> usr/klibc/arch/m68k/crt0.o: In function `_start': usr/klibc/arch/m68k/crt0.S:(.text+0xe): undefined reference to `___libc_init' too many '_'. never seen jbsr, converted that to jsr. Signed-off-by: maximilian attems <maks@sternwelten.at> diff --git a/usr/klibc/arch/m68k/crt0.S b/usr/klibc/arch/m68k/crt0.S index

found by Christian T. Steigies <cts@debian.org> usr/include/arch/m68k/klibc/archstat.h:12: error: syntax error before '__dev64' better use __stdev64 defined in klibc/stathelp.h Signed-off-by: maximilian attems <maks@sternwelten.at> diff --git a/usr/include/arch/m68k/klibc/archstat.h b/usr/include/arch/m68k/klibc/archstat.h index 89c0341..dce25f9 100644 ---

On Sat Jan 10 2015 at 5:21:33 AM Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > What does --itemize-changes say about that file? Try using the stat > command on the various copies of it to see what is different about them. > In my original message, I stated I used --itemize-changes, and I reported the following: >