similar to: R evolution suggestion request

Naming policies are always tricky. The one proposed by Hadley, as the one proposed by Google, are usable but not optimal according to most common needs, that are 1. Name a package 2. Name a class 3. Name a function 4. Name a parameter of a function 5. Name a variable My approach is the following 1. Package names should be made of lowercase characters, dash, dot and underscore 2. Class names

On 2019-08-09 14:27, neonira Arinoem wrote: > I do not follow you Gabriel. Package name must not use digit numbers. > Tarbal will use them, taken from the DESCRIPTION file, version field. > > That's why I consider the weird case name you presented as irrelevant, > and > not to be considered. ggplot2 ? Numbers are allowed in package names right now. > Le ven. 9 ao?t

Creeping code complexity ... I like to think that the cuteR names will have a Darwinian disadvantage in the long run. FWIW Hadley Wickham argues (rightly, I think) against mixed-case names: http://r-pkgs.had.co.nz/package.html#naming. I too am guilty of picking mixed-case package names in the past. Extra credit if the package name and the standard function have different cases! e.g.

On Fri, Aug 9, 2019 at 11:05 AM neonira Arinoem <neonira at gmail.com> wrote: > Won't it be better to have a convention that allows lowercase, dash, > underscore and dot as only valid characters for new package names and keep > the ancient format validation scheme for older package names? > Validation isn't the only thing we need to do wrt package names. we also need to

I do not follow you Gabriel. Package name must not use digit numbers. Tarbal will use them, taken from the DESCRIPTION file, version field. That's why I consider the weird case name you presented as irrelevant, and not to be considered. Le ven. 9 ao?t 2019 ? 20:41, Gabriel Becker <gabembecker at gmail.com> a ?crit : > > > On Fri, Aug 9, 2019 at 11:05 AM neonira Arinoem

On Thu, Nov 29, 2018 at 1:10 PM S Ellison <S.Ellison at lgcgroup.com> wrote: > > > > > plot(x=1:10, y=) > > > plot(x=1:10, y=, 10:1) > > > > > > In both cases, 'y=' is ignored. In the first, the plot is for y=NULL (so not > > 'missing' y) > > > In the second case, 10:1 is positionally matched to y despite the

Won't it be better to have a convention that allows lowercase, dash, underscore and dot as only valid characters for new package names and keep the ancient format validation scheme for older package names? This could be implemented by a single function, taking a strictNaming_b_1 parameter which defaults to true. Easy to use, and compliance results will vary according to the parameter value,

I am wondering if there is any procedure to write a particular value in Percentage format, still maintaining it's numeric character. for example I want to write '.33' as '33%' regards, thanks in advance --------------------------------- [[alternative HTML version deleted]]

> However, my variable is simulated from the cumulative distribution function > of the Poisson distribution. Then I am afraid I don't know what you're trying to achieve. Or why. However, the principle holds; write a function that maps [0,1] to the 'pattern' you want, do that and apply it to the result from randomLHS. It happens that for generating data that follow a given

Hello, I am performing a sensitivity analysis using a Latin Hypercube sampling. However, I have difficulty to draw a Hypercube sample for one variable. I?ve generated this variable from a Poisson distribution as follows: set.seed(5) mortality_probability <- round(ppois(seq(0, 7, by = 1), lambda = 0.9), 2) barplot(mortality_probability, names.arg = seq(0, 7, by = 1), xlab = "Age

Dear r developers, I'm writing a set of new functions for an existing R package on R-forge (called COGARCH). I wrote the new R code (but still no documentation), and updated the NAMESPACE file. I installed it from my local repository and everything seems to work. I checked the local repository and the check did not produces errors, but 2 warnings and 2 notes (I attach the log) one of which

Firstly hi to everyone on the list, I am new to this list ans also R so please forgive the simplicity of my questions over the next few months. I have version R 1.9.1 and want to perform z-scoring for a benchmarking procedure. I have tried to install Henrik Bengtsson's R.classes bundle (http://www.maths.lth.se/help/R/R.classes). I have downloaded the .zip file and placed the relevant folders

Thanks for your answer. However, my variable is simulated from the cumulative distribution function of the Poisson distribution. So, the pattern obtained from the function "qpois" is not the same as the observed pattern (i.e., obtained from the function "ppois") set.seed(5) mortality_probability <- round(ppois(seq(0, 7, by = 1), lambda = 0.9), 2)

Hi, A have small technical question about the calculation of R-squared using lm(). In a study case with experimental values, it seems more logical to force the regression line to pass through origin with lm(y ~ x +0). However, R-squared values are higher in this case than when I compute the linear regression with lm(y ~ x). It seems to be surprising to me: is this result normal ? Is there

Hello! you, Emil Bode <emil.bode at dans.knaw.nl>, wrote on Tuesday, July 31, 2018 1:55 PM: > Some of the changes you're proposing could be made (with effort), but note that you're not > restricted to providing strings with a format. > What you're trying to do can be accomplished with as.difftime(12, units='weeks'), see also > ?as.difftime > > Or if

Hello Dave Here is the code I have tried. getwd() setwd("D:/BAP Session/Nuance") getwd() AmbientTr <- read.csv("AmbientBatchbox.csv", stringsAsFactors = TRUE) str(AmbientTr) summary(AmbientTr) install.packages("ggplot2") library(ggplot2) boxplot(RTF~Batch,data=AmbientTr, ylim = c(0,30), main="RTF By Batch", xlab="Batch",

> The former co-author contributed, so he is still author and probably copyright > holder and has to be listed among the authors, otherwise it would be a CRAN > policy violation ... It's a bit of a philosophical question right now, but at some point in a developing package's life - particularly one that starts small but is subsequently refactored in growth - there may be no code

Dear All, I have the following problem: I have a function in which I check if the difference between values is smaller or equal to a certain threshold. I however realized that I might get there some unexpected results: > abs(1 - 0.95) >= 0.05 [1] TRUE ## So that?s fine, but: > abs(1 - 0.95) <= 0.05 [1] FALSE Apparently, abs(1 - 0.95) is not equal to 0.05, which I find however quite

Dear Forum, I have a data frame as  mydat = data.frame(basel_asset_class = c(2, 8, 8 ,8), defa_frequency = c(0.15, 0.07, 0.03, 0.001)) > mydat   basel_asset_class defa_frequency 1                 2          0.150 2                 8          0.070 3                 8          0.030 4                 8          0.001 I need to get the subset of this data.frame where no of records for the

Dear Forum, I have a data frame as  mydat = data.frame(basel_asset_class = c(2, 8, 8 ,8), defa_frequency = c(0.15, 0.07, 0.03, 0.001)) > mydat   basel_asset_class defa_frequency 1                 2          0.150 2                 8          0.070 3                 8          0.030 4                 8          0.001 I need to get the subset of this data.frame where no of records for the