similar to: ISOdate/ISOdatetime performance suggestions, other date/time questions

Hi, I am trying to convert the following NLMIXED code to NLME, but am running into problems concerning 'Singularity in backsolve'. As I am new to R/S-Plus, I thought I may be missing something in the NLME code. NLMIXED *********** proc nlmixed data=kidney.kidney; parms delta=0.03 gamma=1.1 b1=-0.003 b2=-1.2 b3=0.09 b4=0.35 b5=-1.43 varu=0.5; eta=b1*age+b2*sex+b3*gn+b4*an+b5*pkn+u;

Hi, I'm working with timeseries data. The values are every 5 seconds and each series can last up to 4-5 days. To generate the x-axis labels, I'm doing the following: ========================= # Variable for displaying hours on the x-axis rtime <<- as.POSIXct(round(range(timedata), "hours")) # Variable for displaying days on the x-axis stime <<-

Dear all, I am using Windows and R 2.9.2 for my analyses. I have a large dataset and I am particularly interested in looking at time to an event for a continuous variable. I would like to produce a plot of log(relative risk) or relative risk (also known as hazard ratio) against the continuous variable. I have spent a long time looking for advice on how to do this but my search has proved

Dear all, I am facing problem with inserting the scheduled day of Observation in the dataset. In the dataset I have only  relative time (table 1) and not scheduled day of observation (day 1, 4, 8, 15, 22, 29, 36, 43). I would appreciate if any one could suggest me how to proceed. Eg: Table 1 The real dataset looks like this with Time, DV ... etc RTime   DV 1        101 4        95 8       

Dear all, I am using the ISOdatetime function like this: test.info$TradeTime = with(test.info, mapply(FUN = ISOdatetime, Year, Month, Day, Hour, Minute, 60, "EST")) Where Year, Month etc are all numeric. I think ISOdatetime should return a POSIXct object. However, the result I obtained from the line above is all numeric. Could you please advise? I wish to get POSIXct. Thank you

Hi All, I am watching a strange behaviour of ISOdatetime. In my work computer, I get NA when I try to do > ISOdatetime(1995,03,26,2,0,0) [1] NA But on other dates and/or times (hour) works OK > ISOdatetime(1995,03,25,2,0,0) [1] "1995-03-25 02:00:00 GMT" In my home computer, I do not have this problem. I am running the same version of R (2.8.1 patched) on both machines, the

Hi all, I am using ISOdatetime, and I just found out that when I do ISOdatetime(1995,03,26,2,10,0) (or any other value under minutes or seconds) I get NA This does not happen with the same time in other dates, nor with different hours in the same date. Any hint why this happens? Using R 2.8.1 under ESS/GnuEmacs under Windows XP Pedro -- View this message in context:

Dear list, I need to transform the DateTime of my GPS data from: "666.1751" into "yyyy/mm/dd hh:mm:ss" I have the following code: d$Date <- ISOdatetime(2009, 1, 1, 0, 0, 0, tz = "GMT")+d$Date*(24*3600) This gives me: 2010-10-29 04:12:09, which is wrong. It should be 2010-10-29 06:12:09 Another example: 418.3219 corresponds to: 2010-02-23 07:43:30, but it

"btrfs subvolume list" gets a new option "--fields=..." which allows to specify which pieces of information about subvolumes shall be printed. This is necessary because this commit also adds all the so far missing items from the root_item like the received UUID, all generation values and all time values. The parameters to the "--fields" option is a list of items to

I create a zooreg object that runs from Jan-1-2002 0:00 to Jun-1-2005 0:00... regts.start = ISOdatetime(2002, 1, 1, hour=0, min=0, sec=0, tz="") regts.end = ISOdatetime(2005, 6, 1, hour=0, min=0, sec=0, tz="") regts.zoo <- zooreg( NA, regts.start, regts.end, deltat=3600 ) Upon inspection: > regts.zoo[1:3] 2002-01-01 00:00:00 2002-01-01 01:00:00 2002-01-01 02:00:00

Thanks for this clarification. I have learned in the meantime that it is necessary to be very careful when using all these POSIX things. As another example, here is something that made me scratch my head just yesterday: When I create a sequence of days that happens to start before and ends in daylight savings time, I seem to lose a day: > seq(from = strptime("20030329",

Dear Brian and other R-developers, I have to say that I don't understand why what I wrote should have caused any offence. A smile was what I was hoping for. You know I devote more time than I am supposed to, to support R and its users, in partial repayment of my immeasurable debt to all the Developers. It's not much, it's sometimes misguided (I later discover), and my resources

Dear all, I have found the following (for me) incomprehensible behaviour of ISOdate (POSIXct): > ISOdate(1900,6,16) [1] "1900-06-15 14:00:00 Westeurop?ische Sommerzeit" > ISOdate(1950,6,16) [1] "1950-06-16 14:00:00 Westeurop?ische Sommerzeit" Note that in the first case I get the 15th of June back, not the 16th as I would have expected! This happened under R-1.7.1 on

Dear R-people! I am using R 1.8.0, under Windows XP. While using ISOdate() and strptime(), I noticed the following behaviour when "wrong" arguments (e.g., months>12) are given to these functions: > ISOdate(year=2003,month=2,day=20) #ok [1] "2003-02-20 13:00:00 Westeurop?ische Normalzeit" > ISOdate(year=2003,month=2,day=30) #wrong day, but returns a value [1]

Dear R-devel, I had attempted to compile r-devel (dated Oct. 31, 2001) on WinNT with link to ATLAS, with mostly success. However, when I tried the following, I got a visit from Dr. Watson: R : Copyright 2001, The R Development Core Team Version 1.4.0 Under development (unstable) (2001-10-31) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under

Prof. Bates & R-devel, I've done more test with the following results: I have two versions of ATLAS 3.2.1. One was compiled on my old Thinkpad 600E (PII), the other was compiled on my new Thinkpad T22 (PIIISSE1). I compiled R-devel dated 10/31, 11/01 and 11/04, linked against either of the two ATLAS libs. All gave Dr. Watson when given this code: La.svd(matrix(runif(1e5), 1e3,

From: Anand <anand.jain@oracle.com> This patch adds creation-time to the snapshot list display, which would help user to better manage the snapshots when number of snapshots grow substantially. This patch is developed and on top of the send/receive btrfs and btrfs-progs repo at git://github.com/ablock84/linux-btrfs.git (send-v2) git://github.com/ablock84/btrfs-progs.git (send-v2)

From: Anand Jain <anand.jain@oracle.com> (This patch is for the review/test not yet for the integration). Here is an implementation of the feature to add label to the subvolume and snapshots. Which would help sysadmin to better manager the subvol and snapshots. This can be done in two ways, one - using attr which is user land only changes but drawback is able to change the label

Dear All, I have a data set containing year, month, day and counts as shown below: data <- read.table("data.txt", col.names = c("year", "month", "day", "counts")) Using the formula below, I converted the data to as date and plotted. new.century <- data$year < 70 data$year <- ifelse(new.century, data$year + 2000, data$year + 1900)

I’m trying to export a file from R to excel using the xlsReadWritePro function and I keep getting the error below. I get the same error when I use the oledatetime function. My current date format is mm/dd/yyyy, which is how I want it in excel. Also is there anyway to export different datasets to multiple sheets similar to the ods function in SAS? <?xml:namespace prefix = o ns =