search for: stake

...or example would like to have a three axis bar plot - \ x-axis = location(discrete), y-axis = data value, z-axis = frequency of value occurance (of location and value)   Would also if could also do something like what "qplot" allows, i.e. doing stacked histograms.  I would like the "staked" histogram values to show age.   Thanks for any feedback and insight that can be provided.   * Amongst many others, thanks to : (1) Statistics with R, Vincent Zoonekynd, <zoonek@math.jussieu.fr> (2) An Introduction to R: Software for StatisticalModelling & Computing [[alte...

...ent set of requirements and seems like it would be extremely interesting to see how it would develop over time. This could really be an interesting choice for a certain type of project but as described feels like it is best explored outside of the umbrella of LLVM. > I don't have a strong stake in this decision, but Saleem's commentary matches my thoughts on the topic. Maybe some of this is related to messaging - would the proposed project be *an* LLVM libc or *the* LLVM libc. There is already at least one instance within the LLVM umbrella where a subproject designed and built to a...

...5.116 -2.673 waiting 1.117 4.948 NA NA NA complex 1.237 4.170 0.220 4.713 5.642 novelty 1.054 4.005 0.442 4.260 2.076 creative 1.031 3.561 0.362 3.689 2.549 evaluated 0.963 3.013 NA NA NA body 0.748 2.238 0.596 2.019 0.466 control 0.620 2.149 NA NA NA stakes 0.541 1.905 0.227 2.020 2.343 spont 0.496 1.620 NA NA NA chatter 0.460 1.563 0.361 1.382 0.540 present 0.428 1.236 0.215 1.804 2.194 reward 0.402 1.101 0.288 1.208 0.890 feedback 0.283 0.662 NA NA NA goal 0.237 0.474 NA NA NA Best wishes to al...

...67, NA, 2.34255027516667, NA, 0.5400824922975, 2.1935000655, 0.890007976866667, NA, NA)), row.names = c("skill", "predict", "waiting", "complex", "novelty", "creative", "evaluated", "body", "control", "stakes", "spont", "chatter", "present", "reward", "feedback", "goal"), class = "data.frame") itemInfo # examine column ddd When I try this, column ddd has 1 fewer digits than expected. See the attached screenshot. Why don...

...5.116 -2.673 waiting 1.117 4.948 NA 0.365 NA complex 1.237 4.170 0.220 4.713 5.642 novelty 1.054 4.005 0.442 4.260 2.076 creative 1.031 3.561 0.362 3.689 2.549 evaluated 0.963 3.013 NA NA NA body 0.748 2.238 0.596 2.019 0.466 control 0.620 2.149 NA NA NA stakes 0.541 1.905 0.227 2.020 2.343 spont 0.496 1.620 NA NA NA chatter 0.460 1.563 0.361 1.382 0.540 present 0.428 1.236 0.215 1.804 2.194 reward 0.402 1.101 0.288 1.208 0.890 feedback 0.283 0.662 NA NA NA goal 0.237 0.474 NA NA NA digits specifies...

...complex 1.237 4.170 0.220 4.713 5.642 > novelty 1.054 4.005 0.442 4.260 2.076 > creative 1.031 3.561 0.362 3.689 2.549 > evaluated 0.963 3.013 NA NA NA > body 0.748 2.238 0.596 2.019 0.466 > control 0.620 2.149 NA NA NA > stakes 0.541 1.905 0.227 2.020 2.343 > spont 0.496 1.620 NA NA NA > chatter 0.460 1.563 0.361 1.382 0.540 > present 0.428 1.236 0.215 1.804 2.194 > reward 0.402 1.101 0.288 1.208 0.890 > feedback 0.283 0.662 NA NA NA > goal...

...(so far) only been done via privcmd. Code overview: Though the hypercall simply does arithmetic within locks, some of the semantics in the code may be a bit subtle so let me explain a bit. The key variables (d->unclaimed_pages and total_unclaimed_pages) start at zero if no claim has yet been staked for any domain. (Perhaps a better name is "claimed_but_not_yet_possessed" but that''s a bit unwieldy.) If no claim hypercalls are executed, there should be no impact on existing usage. When a claim is successfully staked by a domain, it is like a watermark but there is no recor...

...and seems like it would be extremely interesting to see how it > would develop over time. This could really be an interesting choice for a > certain type of project but as described feels like it is best explored > outside of the umbrella of LLVM. > > > I don't have a strong stake in this decision, but Saleem's commentary > matches my thoughts on the topic. Maybe some of this is related to > messaging - would the proposed project be *an* LLVM libc or *the* LLVM > libc. There is already at least one instance within the LLVM umbrella > where a subproject desi...

.... But I'm not so sure about starting with a new pass then deleting the other two. I think it's likely to muddy the revision control history. I'd prefer to see a gradual evolution of the AtomicExpandLoadLinked.cpp (perhaps starting with a "git mv" and some internal renaming to stake out the intent, followed by adding and using the extra hooks). Cheers. Tim.

...<hfinkel at anl.gov> wrote: > > > ------------------------------ > > *From: *"Xinliang David Li" <davidxl at google.com> > > On Mon, Apr 18, 2016 at 2:33 PM, Mehdi Amini <mehdi.amini at apple.com> > wrote: >> >> In the current case at stake: the issue is that we can't make the >> Analysis library using anything from the ProfileData library. Conceptually >> there is a problem IMO. >> > > > Yes -- this is a very good point. > > Independent of anything else, +1. > The design of ProfileData and rea...

The second release of TentSteak is out and available as a gem on rubyforge ("gem install tent_steak"). This version introduces a handful of new form helpers, a couple method renames, editable HTML tables, and some application bootstrappers for kickstarting Camping and initializing ActiveRecord. It''s still in active development, and I''d very much appreciate

...to see how they change. Name and email will not be shared, but affiliation will (should it?). I'm expecting the free-text descriptions to be very telling to that respect, so there's no point is hiding it. 2. Gathering people's involvement in LLVM is important. We want to know how much stake people have in LLVM, so we can weight more the choices of people with more stake, but weight the same the *opinions* of everyone. What I mean by this is that, if most of the core developers feel strongly towards using Git and a few external developers feel strongly against, the people that will be...

...be shared, but affiliation will (should it?). > > I'm expecting the free-text descriptions to be very telling to that > > respect, so there's no point is hiding it. > > > > 2. Gathering people's involvement in LLVM is important. We want to > > know how much stake people have in LLVM, so we can weight more the > > choices of people with more stake, but weight the same the *opinions* > > of everyone. > > > > What I mean by this is that, if most of the core developers feel > > strongly towards using Git and a few external develope...

...se, and a number of other things that I tried to enumerate in previous emails. I don't know if anything has changed and the responses I got back originally were "we're going to do it anyway" so it didn't leave much room for engagement. (Disclaimer: Not taking sides, I have no stake in Flang or Fortran). I think David's comparison to LLDB is interesting. It started very distant, and then with time merged with the codebase and now it's a full fledged LLVM project. The current Flang (F18) is meant to be much closer to LLVM than the previous one, and the whole mindset w...

Normally I don't like posting on this list for off-topic info, but I need to know "un-biased" opinions regarding Barracuda's Spam Firewall as we're looking to get one soon where I work and I want to know any pros/cons before I stake my credibility on it for our spam fighting. If you've had good or bad experiences with one of these devices, please contact me _off_ list regarding this. I don't want to spam the list with a major OT thread. Thanks.

...dering if someone could point me at 3 things that I appear to have "lost"? 1) ZapEC(off) - Is there an equivalent dialplan command to request no EC on a channel before dialling in DAHDI? 2) rxfax(file.tiff) - I have found ReceiveFax(), but I am aware that much has happened in the faxing stakes recently, is there a good starting point to read about how this works in 1.6 with T.38 passthru/gateways etc? 3) Bristuff came with its own version of PickupChan() - Does anyone know if native Asterisk supports their Pickup mechanism? Or perhaps the Bristuff work has been ported to 1.6.2? I...

...v will be useful for more advanced use cases, and is generally preferable. What is the argument for not doing that from the start? If it was made I must have missed it. Is it just unwillingness to write the extra 300 lines of code? Sounds like a pretty weak argument when adding kernel ABI is at stake...

...------------------------ >>> >>> *From: *"Xinliang David Li" <davidxl at google.com> >>> >>> On Mon, Apr 18, 2016 at 2:33 PM, Mehdi Amini <mehdi.amini at apple.com> >>> wrote: >>>> >>>> In the current case at stake: the issue is that we can't make the >>>> Analysis library using anything from the ProfileData library. Conceptually >>>> there is a problem IMO. >>>> >>> >>> >>> Yes -- this is a very good point. >>> >>> Independe...

...t; instead hampering communications by pushing unnecessary political > correctness. +2!!! > * Small, on the side jokes are OK if people are not offended. I don't > think any Canadian is offended by "Canadian Cross compiler". If I am > wrong, complain. Assume an honest mistake instead of intention to > offend. You mean the cross compiler that instead of saying "error:" says, "sorry sir, you may have made a mistake here:"? > * In a similar case, "cargo cult" refers to a set of existing beliefs. > Using that in the context of softw...

...analysis (that are not shared with other clients) -- > those code stay with the transformation -- it does not make sense to move > those code in to Analysis. For the same reason, we need to ask first if > InlineCost is intended to be a shared utility? > > > In the current case at stake: the issue is that we can't make the Analysis > library using anything from the ProfileData library. Conceptually there is > a problem IMO. > Yes -- this is a very good point. David > > Moving something from Analysis to TransformUtils just because it needs to > access Pr...