search for: base10

...nif(100, min=0, max=100000) # create plot par(mfrow = c(1,3)) #plotting in the left side boxplot(x, xlab="Linear values") #plotting in the centre boxplot(x, log = "y", xlab="y axis logged") # creating log10 values and plotting on the right side Log.base10.x<-log10(x) boxplot(Log.base10.x, xlab="LOG10 of data") [[alternative HTML version deleted]]

Estimad en s, quería realizar una consulta Dado un data frame llamado aves, como puedo sustiuir las variables area, dist y distm por sus logaritmos en base10 y volver a crear un data frame? Muchas gracias Saludos Susana [[alternative HTML version deleted]]

Dear List, I have a problem I'm finding it difficult to make headway with. Say I have 6 ordered observations, and I want to find all combinations of splitting these 6 ordered observations in g groups, where g = 1, ..., 6. Groups can only be formed by adjacent observations, so observations 1 and 4 can't be in a group on their own, only if 1,2,3&4 are all in the group. For example,

...nd did test) definitions for other conversions (though I didn't post them), but this one also drives it home. ~]$ grep bin_to_hex ~/.bcrc define bin_to_hex(b) { obase=16; ibase=2; return b; } ~]$ echo "bin_to_hex(10101011)" | bc 9A2113 # so we're sending in a string with implied base10 ... sure enough matches what BC errantly decided to do ~]$ echo "obase=16; 10101011" | bc 9A2113 ~]$ echo "obase=16; ibase=2; 10101011" | bc AB > > Yes, and it?s a serious design mistake in bc, IMHO. No other programmable > system I?ve ever used changes how numbers...

...e your way back to sanity. > Not sure how this helps me with my most recent example of bin_to_hex where the ibase within the define clause wasn't honored. Working with bc interfactively or by piping produce the desired/correct values. Testing indicates the ibase is defaulted or overrode as base10 despite what is specified in the define clause. :-( > > My objection is that this is even necessary in the first place. Agreed. -- ---~~.~~--- Mike // SilverTip257 //

...obase=16 /* means 16-base-10 here */ > ibase=2 /* no possibility of confusion */ > 10101011 > > Result: AB, as expected. > Thank you. We're in agreement, your solution _does_ work when piped or interactively. Any order does not work from a definition stanza since base10 is (apparently) not capable of being overrode with definitions. tmp]$ grep bin_to_hex ~/.bcrc #define bin_to_hex(b) { obase=16; ibase=2; return b; } define bin_to_hex(b) { ibase=A; obase=A; obase=16; ibase=2; return b; } tmp]$ echo "bin_to_hex(10101011)" | bc 9A2113 tmp]$ echo "iba...

...and digit interweaving (as in x=135, y=246, interwoven=123456) which are ok for a small number of conversions or weaves, but, to be able to handle a large number of conversions or weaves, I'm hoping that some faster code already exists (ideally calling C or FORTRAN). Any suggestions for going base10 to base2, base2 to base4, or digit interweaving would be appreciated. regards, Richard Remington -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or...

...sage. I would appreciate any help if these issues are intuitively obvious to an experienced Lattice user. Thank you very much in advance! Stephen Tucker [using Windows XP and R 2.4.0] ######### Example code ######### #+++++ Define example data +++++ # x = 0.1 to 10 uniformly spaced in lognormal(base10) scale # y = log10(x) + random noise # this is repeated for four groups: a,b,c,d xpoints = c(rep(1:9,times=2)*10^rep(c(-1,0),each=9),10) df = data.frame(x=rep(xpoints,times=4), y = rep(log10(xpoints),times=4)+rep(rnorm(length(xpoints),0,0.2),times=4), g = rep(rep(letters[1:4],each=length(xpoint...

...o image across. That is when smbd crashes (about halfway/300M), and win gives the error 'cannot copy or replace <filename>: the resource or device is no longer available. That is the exact error everytime (from memory). I have tried different files, a different win98se box, a different base10 hub, and a different network card on the linux box (via-rhine as opposed to natsemi), because someone else using natsemi reported a similar problem on a newsgroup. I can ftp the file either way just fine every time and it uses less CPU. I do have debug level set to 10 though (i turned it up only...

...lain; format=flowed; charset="iso-8859-1"; reply-type=original Chris, I haven't seen anyone post a reply yet so thought I'd throw in my thoughts. I'm no R expert! When you talk about an exponential trend line are you refering to: 1) y=ax^b or 2) y=ae^(bx) If 1) then take base10 logs of y and x and then fit them with simple linear regression. Then calculate the antilog of the residulas and plot these as your trendline. If 2) then take natural logs of y and x and follow the rest of the procedure described in 1). Hope this helps. Murray M Cooper, Ph.D. Richland Statistics...

On Aug 31, 2015, at 6:55 AM, Mike - st257 <silvertip257 at gmail.com> wrote: > > I suppose my only options for this are to use shell functions or write a > script using a language that handles things properly (sanely?). No, there?s a fairly common hack around this problem: ibase=A and obase=A *always* means ?base 10? regardless of the current base, due to a quirk in the way values

Hi all, I have a dataset which consists of 2 columns. I'd like to plot them on a x-y scatter plot and fit an exponential trendline. I'd like R to determine the equation for the trendline and display it on the graph. Since I am new to R (and statistics), any advice on how to achieve this will be greatly appreciated. Many thanks, Chris -- View this message in context:

On Aug 28, 2015, at 9:50 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > > On 08/28/2015 07:15 AM, Mike - st257 wrote: >> Thoughts as to why my BC functions aren't properly converting between bases? >> >> Decimal to binary or hex works fine, but not binary or hex to decimal and >> so forth. > > I'm not an expert in bc, so I might be

On Aug 31, 2015, at 10:05 AM, Mike - st257 <silvertip257 at gmail.com> wrote: > > On Mon, Aug 31, 2015 at 11:15 AM, Warren Young <wyml at etr-usa.com> wrote: > >> ibase=A and obase=A > > Not sure how this helps me with my most recent example of bin_to_hex where > the ibase within the define clause wasn't honored. That?s because your bin_to_hex function

Colleagues, I have a routine in package labdsv that calls a FORTRAN subroutine. Recently, I was informed that it sometimes gives different results on a PC and Mac, and that the PC version is clearly wrong. I tested it on linux (because I don't have a PC), and I get the same (incorrect) behavior as the PC. Simply by inserting debug WRITE statements in the FORTRAN I would get different,