similar to: The case for freezing CRAN

This has been a fascinating discussion. Carl Boettinger replied with a set of examples where the world is much more fragile than my examples. That was useful. It seems that people in my area (medical research and survival) are more careful with their packages (whew!). Gabor Csardi discussed the problems with maintaining a package with lots of dependencies. I maintain the survival package

There is a central assertion to this argument that I don't follow: > At the end of the day most published results obtained with R just won't be reproducible. This is a very strong assertion. What is the evidence for it? I write a lot of Sweave/knitr in house as a way of documenting complex analyses, and a glm() based logistic regression looks the same yesterday as it will

Vagrant and packer look like the could be useful to developers, especially when testing, as they make it relatively painless to 'reinstall' a machine to a (mostly) known state. I find that, no matter how hard I try, there always seem to be a few keystrokes that don't make it into the changelog, and recreating from scratch is how I find them. Thanks for pointing them out. I would

Dear R developers, I am seeking advice on some $subject matter. My package will have an update soon, that is not backward compatible with the current version. It will likely break much of the existing code. Many (~50) packages depend on 'igraph' and they, too, will most probably break with the new version. My intended solution is, that I create a snapshot of the current package, under

This came up again recently with an irreproducible paper. Below an attempt to make a case for extending the r-devel/r-release cycle to CRAN packages. These suggestions are not in any way intended as criticism on anyone or the status quo. The proposal described in [1] is to freeze a snapshot of CRAN along with every release of R. In this design, updates for contributed packages treated the same as

I am using the code below to output some network measures: central_social <- data.frame(V(s641_social)$name, indegree_social, outdegree_social, incloseness_social, outcloseness_social, betweenness_social, eigen_social) and I get the following error: Error in Re(z) : non-numeric argument to function I know this has to do with V but I cannot figure out what is wrong. s641-social is a graph

Hi, I am a Newbie for R. I just installed R-base on my notebook with openSuSE 11. However, I always got compilation errors in installing add-on packages. For example, when installing "igraph" I got the following error: ___________________________________________________________________ * Installing *source* package 'igraph' ... checking for gcc... gcc checking for C compiler

igraph is a package for graphs/networks. It has a C core and uses a simple and fast graph representation allowing millions of vertices and edges. LINKS Release notes for the 0.5.2 version: http://igraph.sourceforge.net/relnotes-0.5.2.html Release notes for the 0.5.1 version: http://igraph.sourceforge.net/relnotes-0.5.1.html Complete list of changes: http://igraph.sourceforge.net/news.html The

igraph is a package for graphs/networks. It has a C core and uses a simple and fast graph representation allowing millions of vertices and edges. LINKS Release notes for the 0.5.2 version: http://igraph.sourceforge.net/relnotes-0.5.2.html Release notes for the 0.5.1 version: http://igraph.sourceforge.net/relnotes-0.5.1.html Complete list of changes: http://igraph.sourceforge.net/news.html The

Hello, I'm having trouble getting the igraph package to load on Solaris. I can get igraph to compile and install from a local directory without issues using simply "R CMD INSTALL igraph", however "library(igraph)" from within R gives the following errors: Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library

Hi R users, I got warning messages when installing the package, and I pasted the messages below. I checked updates that my R-studio is already the newest version. I don't know how to solve the problem. Thanks for your help. > library(igraph) Error in dyn.load(file, DLLpath = DLLpath, ...) : unable to load shared object

Dear All, we have released version 0.6 of the igraph package today. This is a major new version, with a lot of new features, and (sadly) it is not completely compatible with code that was written for the previous igraph versions. (See "Major new features" below for details.) I have included below a list of (bigger) changes. Please see the details in the release notes and the NEWS

Dear All, we have released version 0.6 of the igraph package today. This is a major new version, with a lot of new features, and (sadly) it is not completely compatible with code that was written for the previous igraph versions. (See "Major new features" below for details.) I have included below a list of (bigger) changes. Please see the details in the release notes and the NEWS

Hi, I would like to be able to develop a function to plot an igraph object with lattice (trellis type displays will be usefull for grouping etc). Anyway, I mostly feeble Igraph requires that you convert two columns of data two an igraph object and to be able to plot the graph...I have tried a very, very simplistic (if not naive) approach and surprise, surprise, it didn't work. First of all,

Been and R-user for about 5 years now in an industrial setting, and always find the mailing list most helpful. I have run into problem compiling igraph on R. I have contacted the maintainer of igraph, and he has determined that it is not an igraph problem. System is FreeBSD 7.2, R-2.10.1 [also have a sandbox machine running FreeBSD 7.3, R-2.11]. Both machines fail the installation of igraph.

Hi, what does this mean? --8<---------------cut here---------------start------------->8--- > graph <- graph.data.frame(merged[!v,], vertices=ve, directed=FALSE) cedta decided 'igraph' wasn't data.table aware cedta decided 'igraph' wasn't data.table aware cedta decided 'igraph' wasn't data.table aware cedta decided 'igraph' wasn't

Hi all Is there any systematic way to compute all possible paths, first-order loops and j-th order loops between two given nodes in a flowgraph (directed graph with cycles) - preferably using the igraph library in R? I have checked the igraph documentation but I can't figure out any direct and systematic way to do so. Any ideas? I use the following definitions from Butler, R. and A.

Hello, Could you please test the solution at https://stackoverflow.com/questions/45318188/getting-error-in-function-igraph-write-graph-graphml-while-installing-igrap Specifically - install.packages("devtools") library(devtools) install_github("igraph/rigraph") Please let us know if this works Regards, -- Saint Pai On Tue, Oct 10, 2017 at 01:40:53AM +0100, Paul Smith

igraph is a package for graphs and networks. It has a C core and uses a simple and fast graph representation allowing millions of vertices and edges. NEW FEATURES: - We use the ARPACK library for graph related eigenvalue problems, like Page Rank calculation, Kleinberg's hub and authority scores, eigenvector centrality, etc. There is also a generic interface if someone wants to use

igraph is a package for graphs and networks. It has a C core and uses a simple and fast graph representation allowing millions of vertices and edges. NEW FEATURES: - We use the ARPACK library for graph related eigenvalue problems, like Page Rank calculation, Kleinberg's hub and authority scores, eigenvector centrality, etc. There is also a generic interface if someone wants to use