search for: churned

Hello: If the question is how likely an event will occur at a give time point, can we use logistic regression with time t as a predictor variable? For example, if the data is ID Gender Tenure Churn 1 M 17 0 2 M 3 1 3 M 6 0 4 F 10 1 5 F 9 0 6 F

Hi, I am using rpart decision trees to analyze customer churn. I am finding that the decision trees created are not effective because they are not able to recognize factors that influence churn. I have created an example situation below. What do I need to do to for rpart to build a tree with the variable experience? My guess is that this would happen if rpart used the loss matrix while creating

Hi, On 2020-09-30 17:52:46 -0700, Lang Hames wrote: > I've just realised that we're going to need a change to the definition > generator API in the long term: Right now it is called under the session > lock, but we want to shift to calling it outside the lock and passing a > lookup-continuation. This would allow definition discovery to take an > arbitrarily long time

On 24.05.2018 13:11, Dean Michael Berris via llvm-dev wrote: > >> On 24 May 2018, at 20:19, Sam McCall via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> The coding guidelines say: >>> Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case

(Sorry for CC'ing piles of people, but didn't want folks to miss this in the mailing list churn.) See the subject. The problem is in the target-independent code generator and especially in the x86 backend. I would like to fix it. This will be a mechanical change just organizing code in a way that makes it easy and fast to find methods and related static helpers. It will not change any

On 07/06/2014 18:35, Filip Pizlo wrote: > That would work. :-) > > What about exposing C API a function to query for the presence of an intrinsic? It seems with hindsight that the "experimental" prefix has turned out to be a waste of time. At least without the prefix there was a good chance this churn could be avoided as long as the original review was sound, whereas the

Hi Philip, I think you might be reading more into the suggestion/discussion than is actually there. * I do not want upstream developers "trying to be polite" if that delays otherwise worthwhile work. Nobody suggested that. It’s perfectly possible to “be polite” and still not delay worthwhile work. * The current policy is "downstream is on their own". Nobody

The coding guidelines say: > Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case letter (e.g. openFile() or isFoo()). This means that functions that just compute or access a value (no side-effects) should be named e.g. `getParent()`, rather than `parent()` as they are in

On Sat, Jun 7, 2014 at 6:30 PM, Filip Pizlo <fpizlo at apple.com> wrote: > > > On June 7, 2014 at 1:29:04 PM, Alp Toker (alp at nuanti.com) wrote: > > > On 07/06/2014 18:35, Filip Pizlo wrote: >> That would work. :-) >> >> What about exposing C API a function to query for the presence of an >> intrinsic? > > It seems with hindsight that the

On 5 Feb 2013, at 01:32, Bill Wendling wrote: > No. It hasn't been written up. We typically don't do write-ups for API changes. However, we do list the thing we do change in the ReleaseNotes (these changes haven't made it there though). The attributes API has undergone a horrendous amount of churn over the last few months, both before and after the 3.2 release. I've lost

...re's similar cleanup done in a non-automated fashion as Mehdi pointed out in one of the threads I brought this up (see this thread: http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20170403/443547.html ). Usually some amount of cleanup has been acceptable if the code was generally being churned anyway (eg: clang-formatting a file so it's consistent, before doing major surgery to it anyway, so the surgical changes don't create formatting inconsistencies), or as a result of a new API change (add a range-based accessor then fix up existing call sites to use range-based-for). I'd...

On Sun, Jan 13, 2013 at 2:10 PM, Matthieu Monrocq <matthieu.monrocq at gmail.com> wrote: > gcc 4.5, MSVC 10, clang 3.1 > - decltype v1.0 [1] + late specified return type > - lambda v1.0 [2] > - local types as template arguments > - r-value 2.0 [3] > - static_assert > - built-in type traits This isn't very encouraging. Anecdotally from what I've seen in LLD

We've had a lot of churn in all the trunks (llvm, llvm-gcc, clang) recently, and the testing buildbots have been failing repeatedly. I spoke with Chris this AM, and he suggested we have a "stabilization day." Please avoid large, destabilizing changes for about twenty-four hours. We would like for the testing bots to begin working again. Thanks, stuart

Dear list, I have been using the Rmath library for quite a while: in the current instance, I am calling dnt (non-central t density function) repeatedly for several million. When the argument is small, I get the warning message: full precision was not achieved in 'pnt' which is nothing unexpected. (The density calls pnt, if you look at the function dnt.) However, to have this happen a

On Feb 4, 2013, at 11:54 PM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > On 5 Feb 2013, at 01:32, Bill Wendling wrote: > >> No. It hasn't been written up. We typically don't do write-ups for API changes. However, we do list the thing we do change in the ReleaseNotes (these changes haven't made it there though). > > The attributes API has

Sorry, I botched a commit and broke the build. I've just committed a fix. So expect to see some buildbot churning. -Dave

On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: > David Greene <dag at cray.com> writes: > > Sorry, I botched a commit and broke the build. I've just committed a > > fix. > > > > So expect to see some buildbot churning. > > Don't hurry. A buildbot already decided that I am the only culprit of > the breakage. :-/ Hmm...given that

On Tue, Jul 30, 2019 at 08:51:53AM +0300, Christoph Hellwig wrote: > This avoid having to abuse the vma field in struct hmm_range to unlock > the mmap_sem. I think the change inside hmm_range_fault got lost on rebase, it is now using: up_read(&range->hmm->mm->mmap_sem); But, yes, lets change it to use svmm->mm and try to keep struct hmm opaque to drivers

On Tue, Jul 30, 2019 at 03:10:38PM +0200, Christoph Hellwig wrote: > On Tue, Jul 30, 2019 at 12:35:59PM +0000, Jason Gunthorpe wrote: > > On Tue, Jul 30, 2019 at 08:51:53AM +0300, Christoph Hellwig wrote: > > > This avoid having to abuse the vma field in struct hmm_range to unlock > > > the mmap_sem. > > > > I think the change inside hmm_range_fault got lost

On 21.08.20 10:31, David Hildenbrand wrote: > On 16.08.20 14:53, David Hildenbrand wrote: >> For 5.10. Patch #1-#4,#6 have RBs or ACKs, patch #5 is virtio-mem stuff >> maintained by me. This should go via the -mm tree. >> > > @Andrew, can we give this a churn if there are no further comments? Thanks! ... I just spotted the patches in -next, strange I didn't get an