search for: 60,70

I am trying to understand cut so I can divide a list of numbers into 10 group: 0-9.0 10-10.9 20-20.9 30-30.9, 40-40.9, 50-50.9 60-60.9 70-70.9 80-80.9 90-90.9 As I try to do this, I have been playing with the cut function. Surprising the following for applications of cut give me the exact same groups. This surprises me given that I have varied parameters include.lowest and right. Can someone help me understand what include....

...ou, John I John David Sorkin M.D., Ph.D. Professor of Medicine Chief, Biostatistics and Informatics University of Maryland School of Medicine Division of Gerontology and Geriatric Medicine Baltimore VA Medical Center 10 North Greene Street GRECC (BT/18/GR) Baltimore, MD 21201-1524 (Phone) 410-605-7119 (Fax) 410-605-7913 (Please call phone number above prior to faxing) >>> Jeff Newmiller <jdnewmil at dcn.davis.ca.us> 04/16/16 11:07 PM >>> Have you read FAQ 7.31 recently, John? Your whole premise is flawed. You should be thinking of ranges [0,10), [10,20), and so on...

...from my phone. Please excuse my brevity. On April 16, 2016 7:38:50 PM PDT, John Sorkin <jsorkin at grecc.umaryland.edu> wrote: >I am trying to understand cut so I can divide a list of numbers into 10 >group: > 0-9.0 >10-10.9 >20-20.9 >30-30.9, >40-40.9, >50-50.9 >60-60.9 >70-70.9 >80-80.9 >90-90.9 > >As I try to do this, I have been playing with the cut function. >Surprising the following for applications of cut give me the exact same >groups. This surprises me given that I have varied parameters >include.lowest and right. Can someone...

...eed(1) x <- c(rnorm(1e3, mean=10, sd=1), 50, 100) start <- 0 end <- 110 h <-10 c1 <- cut(x, br=seq(start, end, h), right=TRUE) levels(c1) # I get: # [1] "(0,10]" "(10,20]" "(20,30]" "(30,40]" # [5] "(40,50]" "(50,60]" "(60,70]" "(70,80]" # [9] "(80,90]" "(90,100]" "(100,110]" # I need (observe digits and space after the comma): # [1] "(000, 010]" "(010, 020]" "(020, 030]" "(030, 040]" # [5] "(040, 050...

...be done with table. Or perhaps factor and split. Or prop.table. cut? findInterval? Argh! Please correct me if what I am looking for is not called a "frequency table". Perhaps it's called grouped data. > zz$x9 [1] 65 70 85 65 65 65 62 55 82 59 55 66 74 55 65 56 80 73 45 64 75 58 60 56 60 [26] 65 53 63 72 80 90 95 55 70 79 62 57 65 60 47 61 53 80 75 72 87 52 72 80 85 [51] 75 70 84 60 72 70 76 70 79 72 69 80 62 74 54 58 58 69 81 84 I (think) I want it to look like: 40-49 2 50-59 15 60-69 20 70-79 19 80-89 12 90-99 2 Or the other way around with transpose. classe...

Hi, I'd like to add "alpha" in latex code to my image. Any suggestions? library(UsingR) BagA = c(rep(10,6),rep(20,5), rep(30,4),rep(40,3),rep(50,2),60,70) BagA BagB = c(10, 20,rep(30,2),rep(40,3),rep(50,4),rep(60,5),rep(70,6)) BagB par(mfrow = c(2, 1)) DOTplot(BagA) abline(v=60,lwd=2,lty=2,col="red") text(65,3, "alpha-->", col=2) abline(v=50, lwd=2, lty=2, col="blue") text(57,5, "p-value------->", co...

...from simulations. And, I have found it impossible to create a conditional plot that contains panels using an empty data frame. For example I want: library(lattice) e = data.frame("a", "b", "c", "d") xyplot(X.a. ~ X.b. | X.c. + X.d., data = e, xlim = c(c(50,60),c(60,70)), ylim = c(c(10,20),c(20,30)), drop.unused.levels=FALSE,layout = c(2,2)) to create a empty xyplot that would look like: 50 60 70 ---------------------------- 10 | | | | | | |...

...ever value I use from 0.0005 to 20. I can't obtain a way to make all the labels appear correctly. Between the short help page of plot and the long help page of par, I can't manage. Need some help. Thanks. > table(clage) clage (0,10] (10,15] (15,19] (19,25] (25,35] (35,45] (45,60] (60,70] 1207 1134 947 1477 2154 2095 2732 1353 (70,100] 898 > plot(clage) > plot(clage,cex.lab=0.5) > plot(clage,cex.lab=1.5) > plot(clage,cex.lab=0.05) > plot(clage,cex.lab=20.05) > plot(clage,cex.axis=20.05) > plot(clage,cex.a...

...from simulations. And, I have found it impossible to create a conditional plot that contains panels using an empty data frame. For example I want: library(lattice) e = data.frame("a", "b", "c", "d") xyplot(X.a. ~ X.b. | X.c. + X.d., data = e, xlim = c(c(50,60),c(60,70)), ylim = c(c(10,20),c(20,30)), drop.unused.levels=FALSE,layout = c(2,2)) to create a empty xyplot that would look like: 50 60 70 ---------------------------- 10 | | | | | | |...

ear folks ? I have a question, though it is more of a logic- or a good practices-question than a programming question per se. I am working with data from the American Community Survey summary file. It is mainly categorical count data. Currently I am working with about 40 tables covering about 35 variables, mainly in two-way tables, with some 3-way and a handful of four-way tables. I am going to

Hi, this is probably quite simple but I can't seem to do it correctly. I have a data frame of counts of infections in different ages; something like: count=c(1, 1, 1, 2, 2, 2, 3, 3, 3, 3, 4, 4, 4, 4, 4, 7, 8, 8, 9, 9, 10, 11, 15, 17, 17, 17, 17, 19, 19, 19, 19, 20, 20, 20, 21, 21, 21, 22, 22, 22, 22, 23, 23, 23, 23, 23, 24, 24, 25, 27, 31, 33 ) age=c(3, 8, 9, 7, 56, 58, 10, 13, 53, 55, 11,

...- ../../fish/guestfish sparse $@ 1M + truncate -s 1M $@ blank-disk-1M.qcow2: qemu-img create -f qcow2 -o preallocation=metadata $@ 1M diff --git a/tests/guests/Makefile.am b/tests/guests/Makefile.am index 6ada4ec..796d428 100644 --- a/tests/guests/Makefile.am +++ b/tests/guests/Makefile.am @@ -60,70 +60,37 @@ disk_images = \ # time and we need the tools we have built in order to make it. check_DATA = $(disk_images) guests-all-good.xml -CLEANFILES = $(check_DATA) \ - guests-all-good.xml \ - stamp-fedora-md.img \ - *.tmp.* +$(disk_images) guests-all-good.xml: stamp-guests -# Make severa...

I should probably start by saying this patch series isn't ready for review yet. This patch series adds a test harness to libguestfs. It allows us to run the tests outside the ordinary 'make check' path in the build tree. In particular, you can use this to run tests when libguestfs has been installed. 'make check' and the other 'make check-*' rules still work. The

Since v3: - A large number of fixes, especially for running the tests on installed libguestfs. - Fixed EXTRA_DIST rules throughout. - Extra patch 17/17 which is a tidy-up of the generated XML listing guests. Rich.

This is a more complete patch to add the test harness. The only parts missing now are the language bindings (except OCaml). The language bindings need a bit more thought. At the moment most language binding tests are done through some sort of shell script like perl/run-perl-tests which either runs each test itself or uses some language-specific machinary to run each test. The problem with that

Since v2: - Add perl tests. - Reworked and fixed the tests for virt-builder. - Some further minor bug fixes.