search for: provenance

Dear R users, I 'm working on a dataset consisting of 4 different dataframes with tree, leaf, fruit and seed measurements made on 300 trees, coming from 10 provenances (30 trees per provenance, 10 leaves/fruits/seeds per tree). Provenances are fixed effects (they were not randomly chosen), but trees within provenances and leaves/fruits/seeds within trees were randomly assigned. I wanted to check whether there were any between-provenance differences concerning th...

...ear R-group, I am trying desperately to get this Tukey test working. Its my first time here so I hope my question is not too stupid, but I couldn't find anything helpful in the help or in the forum. I am analysing a dataset of treated grasses. I want to find out, if the grasses from different Provenances react differently. In the aov test I found a significance for the combination Treatment and provenance: summary(PAMaov<-aov(PAMval~Treatmentf*Pretreatmentf*Provenancef+Error(Datef/Code))) Treatmentf:Provenancef p-value: 0.008023 ** In the Linear fixed effects model lme, I can...

...is unfortunate, it has various negative > connotations, e.g., the release notes that read: > "LLVM 10.0 now has sidechannel support for your restrict pointer" > will raise a lot of follow up questions. > > What I think we actually do, and what we should call it, is "provenance" > tracking. > > Now beyond the pure renaming of "sidechannel" into "provenance" (or sth. > similar) I want us to decouple provenance tracking from the noalias > logic. Noalias/restrict is one use case in which (pointer) provenance > information is useful...

Hi Alexey, >From: Alexey Zhikhartsev [..] > We would love to see your patches merged as soon as possible, so I was wondering: do you think the lack of bitcode support will prevent that from happening? Yes, I think that the lack of bitcode support will prevent it. During the Developers meeting, I also talked with Hal and Johannes. They had some extra remarks: - (1) the restrict

...; is unfortunate, it has various negative > connotations, e.g., the release notes that read: > "LLVM 10.0 now has sidechannel support for your restrict pointer" > will raise a lot of follow up questions. > > What I think we actually do, and what we should call it, is "provenance" > tracking. > > Now beyond the pure renaming of "sidechannel" into "provenance" (or sth. > similar) I want us to decouple provenance tracking from the noalias > logic. Noalias/restrict is one use case in which (pointer) provenance > information is useful...

On 01/28/2013 06:51 PM, Hal Finkel wrote: > Is this sufficient to implement #pragma ivdep in clang? I'm not completely sure of this: "Note: The proven dependencies that prevent vectorization are not ignored, only assumed dependencies are ignored."

...; is unfortunate, it has various negative > connotations, e.g., the release notes that read: > "LLVM 10.0 now has sidechannel support for your restrict pointer" > will raise a lot of follow up questions. > > What I think we actually do, and what we should call it, is "provenance" > tracking. > > Now beyond the pure renaming of "sidechannel" into "provenance" (or sth. > similar) I want us to decouple provenance tracking from the noalias > logic. Noalias/restrict is one use case in which (pointer) provenance > information is useful...

...t; is unfortunate, it has various negative > connotations, e.g., the release notes that read: > "LLVM 10.0 now has sidechannel support for your restrict pointer" > will raise a lot of follow up questions. > > What I think we actually do, and what we should call it, is "provenance" > tracking. > > Now beyond the pure renaming of "sidechannel" into "provenance" (or sth. > similar) I want us to decouple provenance tracking from the noalias > logic. Noalias/restrict is one use case in which (pointer) provenance > information is useful...

hi all i''m trying to pass a variable name right round the block and need a hand to ease my aching brain. ##in my sidebar i have <li><%= SidebarItem(''catalogue'') %></li> <li><%= SidebarItem(''provenance'') %></li> <li><%= SidebarItem(''status'') %></li> ##linked to a helper def SidebarItem(name) link_to_remote "#{name}", :url=> {:action => name, :id => @work.id, :layout => false } end but at...

----- Original Message ----- > From: "Nadav Rotem" <nrotem at apple.com> > To: "Pekka Jääskeläinen" <pekka.jaaskelainen at tut.fi> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Monday, January 28, 2013 10:45:36 AM > Subject: Re: [LLVMdev] [PATCH] parallel loop awareness to the LoopVectorizer > > Hi Pekka,

About these disclaimers associated with ivdep and such... You guys are overthinking it. They're just saying you cannot force the compiler to vectorize or parallelize a loop that it knows (can prove!) is not a parallel loop. They are not obliging the compiler to do dependence analysis or alias analysis or anything. For example len = 0; while (A[i]) { i++; len++; } Assert all you want;

For those who come across this thread, I've found the exact list of changed and dropped package between rhel:7 and rhel:8: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/considerations_in_adopting_rhel_8/index#package-replacements_changes-to-packages Too bad that the "note" column is empty in the dropped package table. NO word about reason or

...his scheme might solve/mitigate some of the scalability challenges associated with the pure-metadata solution. * The full-restrict implementation is being used, and Jerone is currently updating this implementation based on feedback from that usage, he also will update the implementation to use provenance instead of sidechannel and repost. * Johannes notes that we need more reviewers for this patch set. **** Thanks again, Hal Hal Finkel Lead, Compiler Technology and Programming Languages Leadership Computing Facility Argonne National Laboratory ________________________________ From: llvm-d...

Gene Cumm wrote:- >TC64 still has ISOLINUX. The basics are to use chain.c32 to boot >USB-B:p3 but syntax depends. Ideally, it's a modern enough Syslinux >version that you can use the "guid" or "label" options to auto-detect >its location rather than "chain.c32 hdN M". Hopefully your FS >label/GUID is unique sdb3 Boot Primary

Hi all, I am trying to identify when a write to memory (store) is safe or not (based on LLVM IR). I refer "safe" to spatial safety (no out of bounds write) and not temporal safety (no double free() etc). My current approach would be to declare every pointer as unsafe that is computed somewhere by a GEP instruction with non constant indices, as well as constant indices that can be

...reading for many days trying to predict with lmer but I haven't managed to do it. I've fitted an allometric model for trees where I have included climatic variables and diameter in the fixed part and in the random part I've included the experimental sites where trees are and also their provenance region. The model is like this : f431<-lmer(log(H05)~log(DN05)*(PwS+ PoS+ PpS+ TpS)+PoP:log(DN05)+PwP:log(DN05)+(log(DN05)-1|P)+(log(DN05)-1|S/B)+(log(DN05)|SP), data=data) once I 've fitted the model I would like to make predictions for a new data frame of values. But i don't know h...

Hi all: I'm testing a new installation of *, bringing up some ATA186. In * environment, all stuff works greats. The only thing that don't work is a Call Transfer, but the 3Party works ok. Some time ago I read that somebody had proven this functionality successfully. If somebody knows what I missing, please let me know. Thanks in advance, Gus -------------- next part -------------- An

Peter, similar to the OpenSSL test and "with_ssl", can we make the libusb test in configure.in depend on "with_usb=yes"? It's not as important as not linking against OpenSSL unless requested, but it caused a bit of confusion when I was trying to rebuild. I forgot that "--with-drivers=all" does not imply "--with-usb", and it was not registering that the

Upstream commit 4370eec05a88 "arm64: Expand arm64 image header" ended up changing the zImage magic (which was actually the initial branch instructio encoding!). The new header has a proper magic number at a fixed location. Switch Xen itself to using this format. Neither the bootwrapper nor the models care about this header themselves and real bootloaders are not widely used, so now is

Hey Timo, Just curious if you ever thought about supporting other than just OpenSSL? PolarSSL looks really interesting, has no major dependencies and is very lightweight compared to OpenSSL, GNUTLS or others... https://polarssl.org/ I guess it could be a lot of work, or not, anyway, I'm just curious... -- Best regards, */Charles/*