similar to: Suggestions for improving R-FAQ

Hey, i want to define 3 ideal breaks (bin) for each variable one of those variables is attached in the previous email, i don't want to consider quartile method because quartile is not working ideally for that data set because data distribution is non normal. so i want you to suggest another method so that i can define 3 breaks with the ideal interval for Recency, frequency and monetary to

Hello, Using the following lines of code, I created the following graph:

Hello, Using the following lines of code, I created the following graph:

Hi, I am trying to find m breakpoints of a linear regression model. I used the segmented package. It works fine for small number of predicators and breakpoints.(3 r.v. 3 points). However, my model has 14 variables it even would not work even for just one breakpoints!. The error message is always estimated breakpoints are out of range. Since my problem is time related problem. So I

Hi all, Following up on the extensive discussions since January, many of us would like to put in place a process to improve LLVM’s decision making process for contentious issues. I’ve put together a proposal for how this works, and am recursively using it to get feedback on the process itself. Thank you to the many people who contributed great ideas and improvements during the pitch phases and

> And now we're against the Atom model? I'm quite new to the llvm community, and basically unfamiliar with LLD, so maybe I'm simply uninformed. If so, I will now proceed to demonstrate that to an entire list of people. :) I've read the doc on http://lld.llvm.org/design.html, but the list of features it says that you get with LLD/Atoms and don't get with the "old

On Sat, 2011-10-29 at 15:16 -0500, Hal Finkel wrote: > On Sat, 2011-10-29 at 14:02 -0500, Hal Finkel wrote: > > On Sat, 2011-10-29 at 12:30 -0500, Hal Finkel wrote: > > > Ralf, et al., > > > > > > Attached is the latest version of my autovectorization patch. llvmdev > > > has been CC'd (as had been suggested to me); this e-mail contains > >

On Mar 19, 2014, at 11:32 AM, Aaron Ballman <aaron at aaronballman.com> wrote: > On Wed, Mar 19, 2014 at 2:13 PM, Lang Hames <lhames at gmail.com> wrote: >> Hi all, >> >> As RFCs go this is short and sweet - I think it would be nice to add an >> empty method to iterator_range. Something like: >> >> bool empty() const { return begin() != end();

#is there a way to get NA in the table of descriptive statistics instead of the function stopping Thank you in advance #data x.f <- structure(list(Site = structure(c(9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L, 9L), .Label = c("BC", "HC", "RM119", "RM148", "RM179", "RM185",

I don't understand which is the problem Could you help me please? Thanks in advance Marta > str(data_indiciN2) 'data.frame': 200 obs. of 36 variables: $ gruppo: Factor w/ 2 levels "0","1": 2 2 2 2 2 2 2 2 2 2 ... $ I001N2: num 19.32 8.22 28.35 7.24 14.7 ... $ I002N2: num 2.92 2.54 0.11 1.6 7.12 ... $ I003N2: num -22.362 -0.222 -19.291

On Wednesday 30 April 2008 17:26, David Vandevoorde wrote: > >> ...malloc() is not specified to access a volatile > >> object, modify an object, or modifying a file (directly or > >> indirectly); i.e., it has no side effect from the language point of > >> view. > > > > Daveed: > > > > Good to know that I was looking at the correct

> You''re running on a shared server and when you startup the second > mongrel more than likely the VPS system is sending the second Mongrel > a kill signal because you''ve gone over your resource allocation. > > ~Wayne Thanks - are there other resources that would be contentious other than memory? I believe I had about 60Meg still available (even w/ 2 mongrels

Hello everyone, In an effort to get a better handle on nouveau's outstanding issues, I'm going to close all bugs that haven't seen any updates since 2011. I asked a core group of nouveau developers about this, and none of them seemed to object. Depending on how this goes, we may do the same thing up to the end of 2012, but that was more contentious. A lot of these bugs are pre-KMS,

On Sat, 2011-10-29 at 14:02 -0500, Hal Finkel wrote: > On Sat, 2011-10-29 at 12:30 -0500, Hal Finkel wrote: > > Ralf, et al., > > > > Attached is the latest version of my autovectorization patch. llvmdev > > has been CC'd (as had been suggested to me); this e-mail contains > > additional benchmark results. > > > > First, these are preliminary

Hi Your statement about attaching data is problematic. We cannot do much with it. Instead use output from dput(yourdata) to show us what exactly your data look like. We also do not know how do you want to split your data. It would be nice if you can show also what should be the bins with respective data. Unless you provide this information you probably would not get any sensible answer. Cheers

Hallo, I am totally confused why Excel and R give me totally different regression results for the data below. If you know the solution, please enlighten me. In Excel I used LINEST() and Data>Data Analysis>Regression and both (fortunately) gave the same result. The coefficients were: /b0=1.16, b1=0.957, b2=0.024, R2=0.0027, adjusted R2=-0.017/ In R I used

The MIR format currently has a short-hand syntax for declaring vreg classes and banks in the function body so you can write something like this: name: foo body: | %3:gpr(s64) = ... rather than the much more verbose and awkward: name: foo registers: - { id: 3, class: gpr } body: | %3(s64) = ... I'd like to make this shorthand the only way to do this. There are a few

Hi You expect us to solve your problem but you ignore advice already recieved. Your data are unreadable, use dput(yourdata) instead. see ?dput > test<-read.table("clipboard", heade=T) Error in scan(file = file, what = what, sep = sep, quote = quote, dec = dec, : line 115 did not have 6 elements What is ?ideal interval? can you define it? Should it be such to provide eqal

https://bugs.freedesktop.org/show_bug.cgi?id=43428 Bug #: 43428 Summary: Segmentation Fault in nv50_screen_fence_update Classification: Unclassified Product: Mesa Version: 7.11 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

On Wed, 2008-04-30 at 18:17 -0500, David A. Greene wrote: > On Wednesday 30 April 2008 17:26, David Vandevoorde wrote: > > > >> ...malloc() is not specified to access a volatile > > >> object, modify an object, or modifying a file (directly or > > >> indirectly); i.e., it has no side effect from the language point of > > >> view. > >