Re: [R] Smallest Space Analysis (SSA) in R

Get Outlook for Android On Mon, Sep 24, 2018 at 3:18 PM +0200, "Andrew" mailto:phaedr...@gmail.com>> wrote: Ha! Even better - thank you. Plenty here for me to play around with. Many thanks Andrew On 23/09/18 15:22, Michael Friendly wrote: > On 9/22/2018 6:49 AM,

Re: [R] cut{base}: is it a bug?

You need to know the number of decimal places reported for the data. I don't know of any straightforward way to compute that from the data. Given the number of decimals, you can compute "true" limit boundaries. This would be a way to compute the upper and lower boundaries and the number of int

Re: [R] cut{base}: is it a bug?

> On Sep 24, 2018, at 12:00 PM, Jose Claudio Faria > wrote: > > Dears, > > Thank you for your contribution! > > However, this function is important in a generic usage package for > frequency distribution tables: fdth ( > https://cran.r-project.org/web/packages/fdth/index.html). > > In this

Re: [R] reading data problem

Hi Jan; Thanks so much. It is much appreciated. The problem has been solved. Regards, Greg On Mon, Sep 24, 2018 at 3:05 PM Jan T Kim wrote: > hmm... I don't see the quote="" paraneter in your read.csv call > > > Best regards, Jan > -- > Sent from my mobile. Apologies for typos and terseness >

Re: [R] reading data problem

hmm... I don't see the quote="" paraneter in your read.csv call Best regards, Jan -- Sent from my mobile. Apologies for typos and terseness On Mon, Sep 24, 2018, 20:40 greg holly wrote: > Hi Jan; > > Thanks so much for this. Yes, I did. Her is my code to read > data: a<-read.csv("for_R_graphs.

Re: [R] reading data problem

Hi Jan; Thanks so much for this. Yes, I did. Her is my code to read data: a<-read.csv("for_R_graphs.csv", header=T, sep=",") On Mon, Sep 24, 2018 at 2:07 PM Jan T Kim via R-help wrote: > Yet one more: have you tried adding quote="" to your read.table > parameters? Quote characters have a 50% ch

Re: [R] reading data problem

Hi Bert; Thanks for writing. Here are my answers to your questions: Regards, Greg 1. What is your OS? What is your R version? *The version is 3.5.0* 2. How do you know that your data has 151 rows? *Because I looked in excel also I work on the same data in SAS* 3. Are there stray chara

Re: [R] cut{base}: is it a bug?

Dears, Thank you for your contribution! However, this function is important in a generic usage package for frequency distribution tables: fdth ( https://cran.r-project.org/web/packages/fdth/index.html). In this case, when I do not know in advance what the user data is, what is the best option to

Re: [R] reading data problem

Yet one more: have you tried adding quote="" to your read.table parameters? Quote characters have a 50% chance of being balanced, and they can encompass multiple lines... On Mon, Sep 24, 2018 at 11:40:47AM -0700, Bert Gunter wrote: > One more question: > > 5. Have you tried shutting down, restart

Re: [R] reading data problem

One more question: 5. Have you tried shutting down, restarting R, and rereading? -- Bert On Mon, Sep 24, 2018 at 11:36 AM Bert Gunter wrote: > *Perhaps* useful questions (perhaps *not*, though): > > 1. What is your OS? What is your R version? > 2. How do you know that your data has 151 rows? >

Re: [R] reading data problem

*Perhaps* useful questions (perhaps *not*, though): 1. What is your OS? What is your R version? 2. How do you know that your data has 151 rows? 3. Are there stray characters -- perhaps a stray eof -- in your data? Have you checked around row 96 to see what's there? 4. Are the data you did get in R

[R] reading data problem

Hi Dear all; I have a dataset with 151*291 dimension. After making data read into R I am getting a data with 96*291 dimension. Even though I have no error message from R I could not understand the reason why I cannot get data correctly? Here are my codes to make read the data a<-read.table("for_

[R] object 'nativeRoutines' not found

Hi all, Since a couple of days travis-ci fails for my package coRanking with "R: devel". The error message is: Error in nativeRoutines[[lib]] <- routines : object 'nativeRoutines' not found "R: release" and "R: oldrel" work fine. Did some R internals change or is the "R: devel" on travis cur

Re: [R] About uniroot error

uniroot REQUIRES that the function be of opposite sign at each end of the starting interval. I won't address the other issues raised, but you can use simple stepping from a starting argument until a sign change occurs. Or you could try a different type of rootfinder, such as newtonRaphson in packa

Re: [R] cut{base}: is it a bug?

Yes, I should have included that point. The cut() function "encourages" exact comparison of values by including the right= argument without a warning that this may create unexpected results. With truly continuous data, values falling exactly on the boundary would be rare. Most data arrives fro

[R] About uniroot error

Thanks for your answers. I continue to learn R and now I am detained in an error with uniroot that I see happens to others but I can not find the solution. Next the code x1 <- BAaxOrd$V1 y1 <- BAaxOrd$V2 x1R <- BAaxOrdRCOS$V1 y1R <- BAaxOrdRCOS$V2 FCOS1 <- splinefun(smooth.spline(x1,y1)) FRCOS1 <-

Re: [R] For Loop

One issue I haven't seen mentioned (and apologize if I've missed it) is that of making programs readable for long-term use. In the histoRicalg project to try to document and test some of the codes from long ago that are the underpinnings of some important R computations, things like the negative i

Re: [R] For Loop

In my opinion this is a pretty reasonable question for someone new to R. Yes, it can be written without a for loop, and it would be better. Rich Heiberger gave a good solution early on, but I'd like to add an outline of the reasoning that leads to the solution. You are taking the log of a ratio

Re: [R] cut{base}: is it a bug?

"Subtracting a bit" only fixes the problem for the test data... it introduces a bias in any continuous data you happen to throw at it. However, if you have data with known rounding applied (e.g. published tabular data) then the subtracting trick can be useful. In general you should not expect fl

Re: [R] cut{base}: is it a bug?

You've been bitten by FAQ 7.31: Why doesn't R think these numbers are equal? https://cran.r-project.org/doc/FAQ/R-FAQ.html#Why-doesn_0027t-R-think-these-numbers-are-equal_003f Your boundaries and your data values are not what you think they are. This is a limitation of digital computing not R. >

[R] cut{base}: is it a bug?

Dears members, Is the below a bug of the cut {base} function? dat <- c( 0.6, 0.6, 0.6, 0.7, 0.7, 0.7, 0.7, 0.7, #(8) 0.8, 0.8, 0.8, 0.9, 0.9, 0.9, 0.9,#(7) 1.0, 1.0, 1.0, 1.0, 1.1, 1.1, 1.1,#(7) 1.2, 1.2, 1.2, 1.2, 1.3, 1.3, 1.3,#(7) 1.4, 1.4, 1.4, 1.5, 1.5, 1.5,

Re: [R] Smallest Space Analysis (SSA) in R

Ha! Even better - thank you. Plenty here for me to play around with. Many thanks Andrew On 23/09/18 15:22, Michael Friendly wrote: On 9/22/2018 6:49 AM, Andrew wrote: Hi Michael This looks like it could be really helpful in moving my project forwards thank you. I remember many years ago u