similar to: Using a NAMESPACE or the Imports field in DESCRIPTION?

Hi, Could someone point me to the relevant documentation that covers what should be in the DESCRIPTION file for packages that have functions imported via the NAMESPACE file? I have read the R Extensions manual, but I cannot find where it covers the DESCRIPTION file vis a vis importing from a namespace. An example: I have a package foo that uses two functions x and y from package bar. Both

Dear list, I want to perform a biplot, using customized titels for the x and y axis. Setting xlab="" and ylab="" resulted in an error, e.g.: > data(USArrests) > biplot(princomp(USArrests),xlab="",ylab="") Error in biplot.default(t(t(scores[, choices])/lam), t(t(x$loadings[, : length of dimnames[1] not equal to array extent > How do I

Hi! The postscript device in 0.90 does not produce symbols (pch=) as it should. E.g.: postscript(file="test.ps",width=8,height=6.4,horizontal=FALSE) plot(1:10,1:10,pch=1:5) legend(1,9,letters[1:5],pch=1:5) dev.off() The result looks quite different compared to the X-windows version. The symbol 1 (pch=1) is much to small, while the other symbols seem to big. Is it a bug? How can I

Dear R-List, I have a dataframe X containing factor f and numeric variable x1, x2, ... I want to create a new dataframe (or possibly a matrix) that gives statistics (e.g. sum) for the variables x1, x2, ... in each group defined by factor f. What is the simplest way to do this? I tried: attach(X) Z <- data.frame(f=levels(f),x1=as.vector(lapply(split(x1,f),sum))) and stumbled on: Error

Dear R-Users! My aim is to produce boxplots without the outliers included in the plot. I started to write a function that looks something like: myboxplot <-function(x,fa) { bpdata <- boxplot(x~fa,plot=FALSE) bpnames <- names(bpdata) for (JJ in bpnames) { command <- paste("bpdata$",JJ,"$out <- numeric(0)",sep=""); eval(command) }

Dear all, It is my understanding that using 'importFrom' in the NAMESPACE of a package allows to avoid conflicts between different packages defining objects with identical names. However, I can still see conflicts while loading the package using 'library'. Here is a toy example, with a package 'foo' importing 'as.igraph' from the igraph package, and 'nj'

This is a follow-up on the discussion originally posted on the R-devel list ( http://tolstoy.newcastle.edu.au/R/e4/devel/08/06/1901.html ), as I have encountered the exact same issue mentioned in Martin's email. Here is a simplified version of my problem: ##================================================================= ## I created a package, say, "tmpA", with a NAMESPACE with

In > R.version.string [1] "R Under development (unstable) (2011-12-15 r57901)" section 1.6.6 of 'Writing R Extensions' says Note that exporting methods on a generic in the namespace will also export the generic, and exporting a generic in the namespace will also export its methods. and Note that importMethodsFrom will also import any generics defined in

Hello! When I know the vector of the variance of the disturbances (i.e. the structure of heteroskedasticity), say Var(u_{i})=v_{i}, what is the weights I should use as argument to lm(): M <- lm(y~x,weigths=1/v) or M <- lm(y~x,weights=1/(v^0.5)) ??? In the help pages I did not find a clear answer to this question, so please could someone help me! Thanks, Wolfgang Koller

I am cleaning up the rms package to not export functions not to be called directly by users. rms uses generic functions defined in other packages. For example there is a latex method in the Hmisc package, and rms has a latex method for objects of class "anova.rms" so there are anova.rms and latex.anova.rms functions in rms. I use:

Hi, I am a bit unsure about using imports in packages and have a few questions. I'm sure the answer to some of these is 'it depends', but I'm interested in what others think and 'best practices' when this is the case. 1) If I use an import or importFrom declaration in a NAMESPACE, should I also qualify the package in calls to the imported function (e.g.

Dear R-developpers, currently the function window shows the following behaviour, if start or end is out of range: > x <- ts(1:14,start=c(1950,2),frequency=4) > y <- window(x,start=c(1950,1),end=c(1953,4)) Warning messages: 1: start value not changed in: window.default(x, ...) 2: end value not changed in: window.default(x, ...) Instead of this I would like it to fill with NAs the

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

Full_Name: Wolfgang Koller Version: 1.0.0 OS: linux Submission from: (NULL) (137.208.7.48) > data(UKLungDeaths) > ts.union(mdeaths, fdeaths,dframe=TRUE) Error in names<-.default(*tmp*, value = nmsers) : names attribute must be the same length as the vector > cbind(mdeaths, fdeaths,dframe=TRUE) Error in names<-.default(*tmp*, value = nmsers) : names attribute

Hi, I am working at adding namespace to my packages, carefully following the doc "Writing R extensions" and some threads on the web. However I cannot find clear explanation about how to best deal with the import or importFrom functions in the name space. To make it short: To declare dependencies in the description file either after Depends: (packages including functions that are

On Mon, Mar 12, 2018 at 2:18 PM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: > [...] > Is that so? Not according to my reading of the 'Writing R > Extensions' manual, nor according to what I have been doing in > all of my packages for ca. 2 years: > > The rule I have in my mind is > > 1) NAMESPACE Import(s|From) \ >

Dear R-Users and Developpers, Currently R does not include functions to compute the skewness and kurtosis. I programmed it myself in the following way, but probably *real* programmers/statisticians can do that better: mykurtosis <- function(x) { m4 <- mean((x-mean(x))^4) kurt <- m4/(sd(x)^4)-3 kurt } myskewness <- function(x) { m3 <- mean((x-mean(x))^3) skew <-

Dear All, I understand the R CMD checks with only the base package attached, everything else (including the other packages bundled with the base R) should be imported and most importantly declared in the Imports field from the DESCRIPTION file. However, I do use functions from other packages than base (utils, grDevices, stats, graphics), for which it is sufficient to declare importFrom() in the

I am developing a package that imports some functions from another package. The imported package (qcc) does not have a namespace and this is causing problems with loading of my package, which has a namespace. Is there a workaround to allow loading the namespace-less package? I searched the archives and found a suggestion that the package should be included in the Depends list, but this has not

Dear All, before its latest version my package had 'Imports: Matrix' in its DESCRIPTION file, but it did not import anything in NAMESPACE. Rather, some functions explicitly loaded Matrix, as they needed. The reason for this was that importing Matrix is really slow, and only very few igraph functions need it. (I guess Matrix is slow because of the many registered names, but that is another