search for: 1970

Dear all, I have noticed a little change in the behaviour of as.factor from R-2.2.1 to R-2.3.0, and can't find it in the NEWS. In R-2.3.0: > times <- 1:5 > class(times) <- "Date" > as.factor(times) [1] 1 2 3 4 5 Levels: 1 2 3 4 5 In R-2.2.1: > as.factor(times) [1] 1970-01-02 1970-01-03 1970-01-04 1970-01-05 1970-01-06 Levels: 1970-01-02 1970-01-03 1970-01-04 1970-01-05 1970-01-06 Is this the intended behaviour? Note that the change is reflected on other functions which seems to use as.factor internally, for example 'tapply'. Consider the following code:...

Dear all, I have noticed a little change in the behaviour of as.factor from R-2.2.1 to R-2.3.0, and can't find it in the NEWS. In R-2.3.0: > times <- 1:5 > class(times) <- "Date" > as.factor(times) [1] 1 2 3 4 5 Levels: 1 2 3 4 5 In R-2.2.1: > as.factor(times) [1] 1970-01-02 1970-01-03 1970-01-04 1970-01-05 1970-01-06 Levels: 1970-01-02 1970-01-03 1970-01-04 1970-01-05 1970-01-06 Is this the intended behaviour? Note that the change is reflected on other functions which seems to use as.factor internally, for example 'tapply'. Consider the following code:...

Hi, I had a 'domain' called APP03. I was performing auto snapshots each night using /usr/bin/virsh snapshot-create APP03 . I then wanted the domain to be called APP01 for clarity's sake, so I did virsh dumpxml APP03 > APP03.xml, edited the name to APP01 and changed the ID. I then did virsh define APP03.xml to get APP01. I have now realised that the qcow2 images are huge (1.1TB

Dear all, I import my data from a csv-file containing one row with date-entries. How can I tell R to treat this data as dates? I've tried to bring it in character-format (as.charachter()) followed by as.POSIXlt() but I get an error message, that the character string is not in a standard unambiguous format, although the date is of format yyyy-mm-dd (what is standard format according to R

(Moving from offlist discussion.) I''m interested in opinions... Assume there are four single vcpu domains A, B, C, D, running on a 2-CPU physical machine. We wish to test for time skew on domain A. Assuming B, C, and D are all running some workload that attempts to fully saturate the (single) cpu. 1) Should the affect on domain A be essentially the same regardless of what load

...-15 21:29 GMT+01:00 Richard W.M. Jones <rjones@redhat.com>: > Gandalf, is there an XVA file publically available (pref. not > too big) that we can look at? I can try to provide one, but it's simple: # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 ---------- 0/0 42353 1970-01-01 01:00 ova.xml ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000000.checksum ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000001.checksum -...

...M SIZE DATE VM CLOCK �K�‘�Q�w���q���U��eInh�ik�{K?�M�w {����}���{�l6�z�Sa�ׂP��2ZZ �e�j��~_��� ^.���=I��=n�ӱ��5��^F���*��v�6��Oc�JfH-[,~9�/̫��%O�cn�2��V䴘t n��]m�UC2d� 2.4G 2096-06-18 11:54:302089366:21:24.846 0 1970-01-01 01:00:00 00:00:00.000 0 1970-01-01 01:00:00 00:00:00.000 0 1970-01-01 01:00:00 00:00:00.000 0 1970-01-01 01:00:00 00:00:00.000 0 1970-01-01 0...

Apparently, as.POSIXlt takes one o'clock as the start of the day : > as.POSIXlt(0,origin="1970-01-01") [1] "1970-01-01 01:00:00 CET" > as.POSIXlt(0,origin="1970-01-01 00:00:00") [1] "1970-01-01 01:00:00 CET" > as.POSIXlt(0,origin="1970-01-01 23:59:59") [1] "1970-01-02 00:59:59 CET" Cheers -- Joris Meys Statistical consultant...

Hi Team, While mounting the gluster volume using 'mount -t glusterfs' command it is getting failed. When we checked the log file getting the below logs [1970-01-02 10:54:04.420065] E [MSGID: 101187] [event-epoll.c:391:event_register_epoll] 0-epoll: failed to add fd(=7) to epoll fd(=0) [Invalid argument] [1970-01-02 10:54:04.420140] W [socket.c:3095:socket_connect] 0-: failed to register the event [1970-01-02 10:54:04.420406] E [glusterfsd-mgmt.c:1818:mg...

...> >> Gandalf, is there an XVA file publically available (pref. not > >> too big) that we can look at? > > > > I can try to provide one, but it's simple: > > > > # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 > > ---------- 0/0 42353 1970-01-01 01:00 ova.xml > > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 > > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000000.checksum > > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 > > ---------- 0/0 40 1970...

Can someone, please, explain the difference in as.POSIXct results before 1970 and on and after 1970 as illustrated below. After 1970, the use of 'EST' or "EST+5EDT' as the timezone does not affect the result of asPOSIXct, but before 1970 on 10/28 the results are different. > as.POSIXct('1970-10-29', tz='EST')+1 [1] "1970-10-29 00:00...

# R version 2.3.1 (2006-06-01) Debian Linux "testing" # Is the following behaviour a bug, feature or just a lack of # understanding on my part? I see that this was discussed here # last March with no apparent resolution. d <- as.factor(c("1970-04-04","1970-08-11","1970-10-18")) x <- c(9,10,11) ch <- data.frame(Date=d,X=x) d <- as.factor(c("1970-06-04","1970-08-11","1970-08-18")) y <- c(109,110,111) sp <- data.frame(Date=d,Y=y) df <- merge(ch,sp,all=TRUE,by="D...

...3 3 3 3 3 3 3 3 ... $ child_mortality : num 0.232 0.232 0.232 0.232 0.232 ... $ democracy : Factor w/ 1 level "dictatorship": 1 1 1 1 1 1 1 1 1 1 ... $ wealth : Factor w/ 5 levels "Lowest quintile",..: 2 4 1 4 5 1 4 1 4 5 ... $ birth_year : int 1970 1970 1970 1970 1970 1970 1970 1970 1970 1970 ... $ residence : Factor w/ 2 levels "Rural","Urban": 1 1 1 1 2 1 1 1 1 2 ... $ birth_order : int 1 2 2 5 1 1 3 1 2 2 ... $ maternal_educ : Factor w/ 4 levels "Higher","No education",..: 3 2 2...

> x<-as.POSIXct("1970-1-1", tz="UTC")-.5 > y<-as.POSIXct("1970-1-1", tz="UTC")+.5 > x==y [1] FALSE # of course but x and y "appear" to be the same when formatted, even with extra precision: > format(x, format="%Y-%m-%d %H:%M:%OS2") [1] "1970-01-01...

hi all, when i try to connnect to my smaba server from a win2000 workstation, it says the using network name is no longer usable. the log is like below: ... [1970/01/01 00:00:39, 10] ../lib/util.c:dump_data(1541) [000] 4D 5C E0 48 6D A0 99 2B CC 9F 15 9C AF E6 74 3B M\.Hm..+ ......t; [1970/01/01 00:00:39, 10] ../lib/util.c:dump_data(1549) [010] CB 61 96 1F 8B ED DD 3B 5C 5C 31 37 32 2E 39 36 .a.....; \\172.96 [1970/01/01 00:00:39, 10] ../lib/util.c:d...

...na.rm = T)) I crated the lag of the variable first and then attempted to compute the average but this does not seem to to what I want. What I am doing wrong? Any help will be appreciated. The data is below. Thank you. Sincerely, Milu dput(droplevels(head(df, 10))) structure(list(year = c(1970L, 1970L, 1970L, 1970L, 1970L, 1970L, 1970L, 1970L, 1970L, 1970L), citycode = c(1L, 1L, 1L, 1L, 1L, 1L, 1L, 1L, 1L, 1L), month = c(1L, 1L, 1L, 1L, 2L, 2L, 2L, 2L, 2L, 3L), week = c(1L, 2L, 3L, 4L, 5L, 5L, 6L, 7L, 8L, 9L), date = structure(c(1L, 2L, 3L, 4L, 5L, 5L, 6L, 7L, 8L, 9L), .Label = c("1...

...Jones <rjones@redhat.com>: >> Gandalf, is there an XVA file publically available (pref. not >> too big) that we can look at? > > I can try to provide one, but it's simple: > > # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 > ---------- 0/0 42353 1970-01-01 01:00 ova.xml > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000000.checksum > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 > ---------- 0/0 40 1970-01-01 01:00 Ref:175...

...nes <rjones@redhat.com>: > > Gandalf, is there an XVA file publically available (pref. not > > too big) that we can look at? > > I can try to provide one, but it's simple: > > # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 > ---------- 0/0 42353 1970-01-01 01:00 ova.xml > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 > ---------- 0/0 40 1970-01-01 01:00 Ref:175/00000000.checksum > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 > ---------- 0/0 40 1970-01-01 01:00 Ref:175...

...s there an XVA file publically available (pref. not >> >> too big) that we can look at? >> > >> > I can try to provide one, but it's simple: >> > >> > # tar tvf 20160630_124823_aa72_.xva.gz | head -n 50 >> > ---------- 0/0 42353 1970-01-01 01:00 ova.xml >> > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000000 >> > ---------- 0/0 40 1970-01-01 01:00 >> Ref:175/00000000.checksum >> > ---------- 0/0 1048576 1970-01-01 01:00 Ref:175/00000001 >> > ----------...

...at all as also with dropbear in combination with OpenSSH's sftp-server binary. More digging into details I checked the raw directory listing that is returned when requesting dir lsiting .. Command: ls Status: Listing directory / Listing: ?--------- 38 16893 15 1099511628032 Jan 1 1970 . Listing: ?--------- 38 16893 15 1099511628032 Jan 1 1970 .. Listing: ?--------- 19 16877 bin 1099511628032 Jan 1 1970 bin Listing: ?--------- 35 16877 adm 1099511628032 Jan 1 1970 dev Listing: ?--------- 18 16893 disk 1099511628032 Jan 1 1970 etc Li...