search for: summari

Dear R-Helpers, I suspect I'm about to ask a FAQ, but I haven't been able to find an answer in the FAQ, AItR or an R Site Search. When I look at the methods of summary (below) it says, "Non-visible functions are asterisked". I looked at the help file for summary.princomp, which did not comment on it being non-visible. I ran its help file example, which printed visible output. I

...fically to emit to LLVM assembly. Proposal below, please let me know your thoughts. Thanks, Teresa *RFC: LLVM Assembly format for ThinLTO Summary========================================Background-----------------ThinLTO operates on small summaries computed during the compile step (i.e. with “-c -flto=thin”), which are then analyzed and updated during the Thin Link stage, and utilized to perform IR updates during the post-link ThinLTO backends. The summaries are emitted as LLVM Bitcode, however, not currently in the LLVM assembly.There are...

...fically to emit to LLVM assembly. Proposal below, please let me know your thoughts. > > Thanks, > Teresa > > RFC: LLVM Assembly format for ThinLTO Summary > ======================================== > > Background > ----------------- > > ThinLTO operates on small summaries computed during the compile step (i.e. with “-c -flto=thin”), which are then analyzed and updated during the Thin Link stage, and utilized to perform IR updates during the post-link ThinLTO backends. The summaries are emitted as LLVM Bitcode, however, not currently in the LLVM assembly. > &gt...

On Thu, May 3, 2018 at 2:58 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > Hi Teresa, > > I have re-read your proposal, and I'm not getting how you plan to > represent combined summaries with this. Unless I'm missing something, there > doesn't seem to be a way to write out summaries that is independent of the > global values that they relate to. Is that something that you plan to > address later? > I envisioned that the combined index assembly files would onl...

...ally to emit to LLVM assembly. > Proposal below, please let me know your thoughts. > > Thanks, > Teresa > > > > > > > *RFC: LLVM Assembly format for ThinLTO > Summary========================================Background-----------------ThinLTO > operates on small summaries computed during the compile step (i.e. with “-c > -flto=thin”), which are then analyzed and updated during the Thin Link > stage, and utilized to perform IR updates during the post-link ThinLTO > backends. The summaries are emitted as LLVM Bitcode, however, not currently > in the LLVM...

Hi Teresa, I have re-read your proposal, and I'm not getting how you plan to represent combined summaries with this. Unless I'm missing something, there doesn't seem to be a way to write out summaries that is independent of the global values that they relate to. Is that something that you plan to address later? Peter On Tue, Apr 24, 2018 at 7:43 AM, Teresa Johnson <tejohnson at google.co...

Hi Teresa, Thanks for sending this proposal out. I would again like to register my disagreement with the whole idea of writing summaries in LLVM assembly format. In my view it is clear that this is not the right direction, as it only invites additional complexity and more ways for things to go wrong for no real benefit. However, I don't have the energy to argue that point any further, so I won't stand in the way here. On...

...Peter, Thanks for your comments, replies below. Teresa On Wed, Apr 25, 2018 at 2:08 PM Peter Collingbourne <peter at pcc.me.uk> wrote: > Hi Teresa, > > Thanks for sending this proposal out. > > I would again like to register my disagreement with the whole idea of > writing summaries in LLVM assembly format. In my view it is clear that this > is not the right direction, as it only invites additional complexity and > more ways for things to go wrong for no real benefit. However, I don't have > the energy to argue that point any further, so I won't stand in the...

...resa Johnson <tejohnson at google.com> wrote: > > > On Thu, May 3, 2018 at 2:58 PM, Peter Collingbourne <peter at pcc.me.uk> > wrote: > >> Hi Teresa, >> >> I have re-read your proposal, and I'm not getting how you plan to >> represent combined summaries with this. Unless I'm missing something, there >> doesn't seem to be a way to write out summaries that is independent of the >> global values that they relate to. Is that something that you plan to >> address later? >> > > I envisioned that the combined index...

...> wrote: > >> >> >> On Thu, May 3, 2018 at 2:58 PM, Peter Collingbourne <peter at pcc.me.uk> >> wrote: >> >>> Hi Teresa, >>> >>> I have re-read your proposal, and I'm not getting how you plan to >>> represent combined summaries with this. Unless I'm missing something, there >>> doesn't seem to be a way to write out summaries that is independent of the >>> global values that they relate to. Is that something that you plan to >>> address later? >>> >> >> I envisioned...

When I load a table from a data source and run summary() on it, the summary gives me basic summary statistics I'm looking for, and it also discriminates between quantitative and qualitative data and summarizes them accordingly. For example, if I do this: mydata <- read.table("data.txt") summary(mydata) I would get output like this: > summary(mydata) County BERNALILLO:2863 DONA ANA : 772 SANTA FE : 671 SANDOVAL : 579 SAN JUAN : 471 VALENCIA : 281 (Other...

...> Teresa > > On Wed, Apr 25, 2018 at 2:08 PM Peter Collingbourne <peter at pcc.me.uk> > wrote: > >> Hi Teresa, >> >> Thanks for sending this proposal out. >> >> I would again like to register my disagreement with the whole idea of >> writing summaries in LLVM assembly format. In my view it is clear that this >> is not the right direction, as it only invites additional complexity and >> more ways for things to go wrong for no real benefit. However, I don't have >> the energy to argue that point any further, so I won't...

Dear list members I have a doubt on how p-values for t-statistics are calculated in the summary of Linear Models. Here goes an example: x <- rnorm(100,50,10) y <- rnorm(100,0,5) fit1<-lm(y~x) summary(fit1) summary(fit1)$coef[2] # b summary(fit1)$coef[4] # Std. Error summary(fit1)$coef[6] # t-statistic summary(fit1)$coef[8] # Pr(>|t| summary(fit1)$df [2] # degrees of freedom #

...eloading it and making the thin-link faster). The fundamental problem is that an analysis result has to be able to be invalidated with IR changes, attaching this directly to the module wouldn't achieve this. The risk is that when the IR and the summary get out-of-sync (`clang -O2 my_module_with_summaries.ll -emit-llvm -o my_optimized module_with_summaries.ll`) the summaries would be badly wrong. Have you looked into what it'd take to make it a "real" analysis in the pass manager? Cheers, -- Mehdi Le mar. 1 mai 2018 à 11:10, Peter Collingbourne <peter at pcc.me.uk> a éc...

...ptable to everyone. =) > The fundamental problem is that an analysis result has to be able to be > invalidated with IR changes, attaching this directly to the module wouldn't > achieve this. The risk is that when the IR and the summary get out-of-sync > (`clang -O2 my_module_with_summaries.ll -emit-llvm -o my_optimized > module_with_summaries.ll`) the summaries would be badly wrong. > > Have you looked into what it'd take to make it a "real" analysis in the > pass manager? > Thanks for raising this issue specifically, I hadn't addressed it in my pr...

...pr 25, 2018 at 2:08 PM Peter Collingbourne <peter at pcc.me.uk> >> wrote: >> >>> Hi Teresa, >>> >>> Thanks for sending this proposal out. >>> >>> I would again like to register my disagreement with the whole idea of >>> writing summaries in LLVM assembly format. In my view it is clear that this >>> is not the right direction, as it only invites additional complexity and >>> more ways for things to go wrong for no real benefit. However, I don't have >>> the energy to argue that point any further, so...

...adability of the summary. > > > The fundamental problem is that an analysis result has to be able to be invalidated with IR changes, attaching this directly to the module wouldn't achieve this. The risk is that when the IR and the summary get out-of-sync (`clang -O2 my_module_with_summaries.ll -emit-llvm -o my_optimized module_with_summaries.ll`) the summaries would be badly wrong. > > Have you looked into what it'd take to make it a "real" analysis in the pass manager? > > Thanks for raising this issue specifically, I hadn't addressed it in my propos...

...> > >> The fundamental problem is that an analysis result has to be able to be >> invalidated with IR changes, attaching this directly to the module wouldn't >> achieve this. The risk is that when the IR and the summary get out-of-sync >> (`clang -O2 my_module_with_summaries.ll -emit-llvm -o my_optimized >> module_with_summaries.ll`) the summaries would be badly wrong. >> >> Have you looked into what it'd take to make it a "real" analysis in the >> pass manager? >> > > Thanks for raising this issue specifically, I had...

...undamental problem is that an analysis result has to be able to be >>>> invalidated with IR changes, attaching this directly to the module wouldn't >>>> achieve this. The risk is that when the IR and the summary get out-of-sync >>>> (`clang -O2 my_module_with_summaries.ll -emit-llvm -o my_optimized >>>> module_with_summaries.ll`) the summaries would be badly wrong. >>>> >>>> Have you looked into what it'd take to make it a "real" analysis in the >>>> pass manager? >>>> >>> >&g...

Hi, I'am using the Xiph Theora Encoder directshow Filter in a csharp application. It works fine but I would like to modify the configuration, like the quality settings. I would like to know if there is a possibility to configure it programmatically without using the propertyPage dialog. Thanks a lot for your help Mathieu -------------- next part -------------- An HTML attachment was