search for: idat

Debugging this issue: https://github.com/Rdatatable/data.table/issues/2008 We have custom class 'IDate' which inherits from 'Date' (it just forces integer storage for efficiency, hence, I). The concatenation done by rbind, however, breaks this and returns a double: library(data.table) DF = data.frame(date = as.IDate(Sys.Date())) storage.mode(rbind(DF, DF)$date) # [1] "double&quot...

On Sun, May 26, 2019 at 4:06 AM Michael Chirico <michaelchirico4 at gmail.com> wrote: > > Have finally managed to come up with a fix after checking out sys.calls() > from within the as.Date.IDate debugger, which shows something like: > > [[1]] rbind(DF, DF) > [[2]] rbind(deparse.level, ...) > [[3]] `[<-`(`*tmp*`, ri, value = 18042L) > [[4]] `[<-.Date`(`*tmp*`, ri, value = 18042L) > [[5]] as.Date(value) > [[6]] as.Date.IDate(value) > > I'm not sure why [...

...ger snap of clarity on the whole issue. I'll add that actually it was data.table's code at fault on the storage conversion -- note that if you use an arbitrary sub-class 'foo' with no methods defined, it'll stay integer. That's because [<- calls as.Date and then as.Date.IDate, and that method (ours) has as.numeric(); earlier I had recognized that if we commented that line, the issue was "fixed" but I still wasn't understanding the root cause. My last curiosity on this issue will be in my follow-up thread. Mike C On Mon, May 27, 2019, 10:25 PM Joshua Ul...

...it would be good to summarize my thoughts, since I made a few hypotheses that turned out to be false. This isn't a bug in base R, in either rbind() or `[<-.Date`. To summarize the root cause: base::rbind.data.frame() calls `[<-` for each column of the data.frame, and there is no `[<-.IDate` method to ensure the replacement value is converted to integer. And, in fact, `[<-.Date` calls as.Date() and data.table::as.Date.IDate() calls as.numeric() on the IDate object. So the problem exists, and can be fixed, in data.table. Best, Josh On Mon, May 27, 2019 at 9:34 AM Joshua Ulrich...

Have finally managed to come up with a fix after checking out sys.calls() from within the as.Date.IDate debugger, which shows something like: [[1]] rbind(DF, DF) [[2]] rbind(deparse.level, ...) [[3]] `[<-`(`*tmp*`, ri, value = 18042L) [[4]] `[<-.Date`(`*tmp*`, ri, value = 18042L) [[5]] as.Date(value) [[6]] as.Date.IDate(value) I'm not sure why [<- is called, I guess the implementation...

...6:47 AM Joshua Ulrich <josh.m.ulrich at gmail.com> wrote: > > On Sun, May 26, 2019 at 4:06 AM Michael Chirico > <michaelchirico4 at gmail.com> wrote: > > > > Have finally managed to come up with a fix after checking out sys.calls() > > from within the as.Date.IDate debugger, which shows something like: > > > > [[1]] rbind(DF, DF) > > [[2]] rbind(deparse.level, ...) > > [[3]] `[<-`(`*tmp*`, ri, value = 18042L) > > [[4]] `[<-.Date`(`*tmp*`, ri, value = 18042L) > > [[5]] as.Date(value) > > [[6]] as.Date.IDate(valu...

...y on the whole issue. > > I'll add that actually it was data.table's code at fault on the storage conversion -- note that if you use an arbitrary sub-class 'foo' with no methods defined, it'll stay integer. > > That's because [<- calls as.Date and then as.Date.IDate, and that method (ours) has as.numeric(); earlier I had recognized that if we commented that line, the issue was "fixed" but I still wasn't understanding the root cause. > > My last curiosity on this issue will be in my follow-up thread. > > Mike C > > On Mon, May 2...

Dear Bioc and R List Users, I am having trouble analysing illumine data generated from BeadScan. I have .idat files and JPEG images. I realise that i need bead-level summary data to be able to begin quality control followed by normalization. Is there a way i can read .idat files for expression analysis or do i need to go back to BeadScan and generate .txt files/tiff files ? Appreciate any help here. Many...

This is an attempt to make supermin check for the existing results of an output when checking whether the appliance must be rebuilt using --if-newer. At the moment it is implemented only for the build mode, and for its ext2 output format. Pino Toscano (4): build: factor ext2 filenames Tighten Unix_error check for missing outputdir Extend modes with list of outputs build: set

...1 insertions(+), 7 deletions(-) diff --git a/src/supermin.ml b/src/supermin.ml index 7c7135b3..b997643 100644 --- a/src/supermin.ml +++ b/src/supermin.ml @@ -236,13 +236,17 @@ appliance automatically. *) if if_newer then ( try - let odate = (lstat outputdir).st_mtime in - let idates = List.map (fun d -> (lstat d).st_mtime) inputs in - let pdate = (get_package_handler ()).ph_get_package_database_mtime () in - if List.for_all (fun idate -> idate < odate) (pdate :: idates) then ( - if debug >= 1 then - printf "supermin: if-newer: outpu...

...with + | Prepare -> Mode_prepare.get_outputs args inputs + | Build -> Mode_build.get_outputs args inputs in + let mode_outputs = List.map ((//) outputdir) mode_outputs in + let odates = List.map (fun d -> (lstat d).st_mtime) (outputdir :: mode_outputs) in let idates = List.map (fun d -> (lstat d).st_mtime) inputs in let pdate = (get_package_handler ()).ph_get_package_database_mtime () in - if List.for_all (fun idate -> idate < odate) (pdate :: idates) then ( + if List.for_all (fun idate -> List.for_all (fun odate -> idate <...

Hi Experts, I have a problem in Dates. I have a zoo object called 'intra'. And the class of index(intra) is ("Chron" "Dates" "Time"). I need to put the index of this zoo object into a data frame. So I used, idat<-data.frame(Datetime=as.POSIXlt(index(intra),"GMT")) But I get the values of 'idat' to be: "01joulu2006 09:59:59" "01joulu2006 10:09:59" "01joulu2006 10:19:59" "01joulu2006 10:30:00" "01joulu2006 10:40:00" "01j...

...th <shubhak at ambaresearch.com> Date: Nov 24, 2006 7:54 PM Subject: Dates Conversion/write.foreign To: Shubha Karanth <shubhakaranth at gmail.com>, Shubha Vishwanath Karanth <shubhak at ambaresearch.com> Hi R experts, I need an urgent help... I have an a dataframe caled idat. Below i give a snapshot of it. Datetime Volume_a Volume_b (11/21/06 12:50:00) (11/21/06 12:50:00) 0 0 (11/21/06 13:00:00) (11/21/06 13:00:00) 0 0 (11/21/06 13:10:00) (11/21/06 1...

...amp;& if_newer then ( try - let odate = (lstat outputdir).st_mtime in + let outputs = Mode_build.get_outputs args inputs in + let outputs = List.map ((//) outputdir) outputs in + let odates = List.map (fun d -> (lstat d).st_mtime) (outputdir :: outputs) in let idates = List.map (fun d -> (lstat d).st_mtime) inputs in let pdate = (get_package_handler ()).ph_get_package_database_mtime () in - if List.for_all (fun idate -> idate < odate) (pdate :: idates) then ( + if List.for_all (fun idate -> List.for_all (fun odate -> idate <...

...mode. So shouldn't this just give an error (either here, or earlier) if we're in prepare mode? Rich. > + let mode_outputs = List.map ((//) outputdir) mode_outputs in > + let odates = List.map (fun d -> (lstat d).st_mtime) (outputdir :: mode_outputs) in > let idates = List.map (fun d -> (lstat d).st_mtime) inputs in > let pdate = (get_package_handler ()).ph_get_package_database_mtime () in > - if List.for_all (fun idate -> idate < odate) (pdate :: idates) then ( > + if List.for_all (fun idate -> List.for_all (fun odate -...

This is an attempt to make supermin check for the existing results of an output when checking whether the appliance must be rebuilt using --if-newer. At the moment it is implemented only for the ext2 output format of the build mode. Changes from v1: - drop empty stub for the prepare mode - add patch to ignore --if-newer on modes different than build - squash patch with stub for the build mode

...cause the table is huge and the memory not large enough for the whole table.: number.of.records=100 fp=file("abc.csv","r") pos=seek(fp, rw="read") for (i in 1:number.of.record){ current.row=scan(file=fp, sep=',', what=list(count=1, cusip6="", idate=1, spread=1.1, vol252=1.1, vol1000=1.1, st_debt=1.1, lt_debt=1.1 , total_liab= 1.1, cr=1.1, shrout=1.1, prc=1.1, mkt_cap=1.1, rtng=1.1, sec=1.1, cr3m=1.1, cr5y=1.1, ust3m=1.1, ust5y=1.1), flush=TRUE, nlines=1,quiet=T) ... } I need to know the number of records in the table and put it in th...

...what I''ve been able to get working is: <%= text_field_tag(''date'', illness_date, :size => 30) %></p> <%= observe_field(''date'', :url => {:action => ''update_date'', :id => illness_id}, :with => "''idate=''+$(''date'').value" ) %> Of course, maybe I''m just doing it wrong. I suppose it might make some sense if it''s possible to send more than one params value back with the :with option. Does anybody know anything about how that might be possible?...

...er works a little bit like SPSS, actually, because the metadata is accessed, but the data is not really loaded until later (as far as I can tell, one must run either subset or as.data.set to force the actual data read). One can generate the description and codebook without accessing the data. > idat <- spss.system.file("gss2006.sav") > show(idat) SPSS system file 'gss2006.sav' with 5137 variables and 4510 observations A subset function can access the particular variables from the data. > idat2 <- subset(idat, select=c(gunlaw)) > idat2 Data set with 4510...

I have a simple query as follows: "SELECT m_id,sale_date,YEAR(sale_date),WEEK(sale_date),return_type,DATEDIFF(return_date,sale_date) AS elapsed_time FROM risk_input" I can get, and view, all the data that that query returns. The question is, sale_date is a timestamp, and I need to call split to group this data by m_id and the week in which the sale occurred. Obviously, I would