Re: [Rd] about integration of a library into package creation

Hello, I dont understand such error coming from my installed package and dont appearing when i load the code source directly . The problem occur when the function capture the path value (FileIn), and so cannot find the file inside the directory. > findModelCluster(MetOpt, MetLab, Nu, q, K=1, G,

[Rd] Bug in nortest cvm.test package (PR#8980)

I believe there to be a bug in the cvm.test module of the nortest package authored by Juergen Gross. I do not know how to contact the author directly. I've been running some normality tests using the nortest package. For some of my datasets the Cramer-von Mises normality test generates an

[Rd] separators in data()

just out of curiosity: why is the default behavior in data() for reading in .csv files to use sep=";" (semicolon rather than comma)? is this a historical artifact of some sort, or is there other logic to it? It caught me by surprise since I was expecting it to be sep="," as in read.csv() ..

[Rd] Bug or not? (PR#8977)

Hi, I am writing this email, because I am not sure if the issue I have discovered is a bug or not. For a few days I have been fiddling around with a small program that calculates the reflectance of multilayer dielectric mirrors (eg. bragg mirrors). It does not really matter what I did, what ma

Re: [Rd] Bug or not? (PR#8977)

I think you are computing your matrix to power N+1 instead of N. This code seems to work for me: Rs <- function(lambda, theta, N){ n0 <- 3.66 n1 <- 2.4 n2 <- 1.45 nn <- 1.00 lambda_ref <- 1000 d1 <- lambda_ref / 4 / n1 d2 <- lambda_ref / 4 / n2 theta0 <- asin( nn /

[Rd] More: Hopefully Final Fix for Bug 8141 (C stack overflow in substituteList)

Hi, Just in case anyone is interested in bug 8141. With some further testing, I found and fixed a small bug in my code and simplified it a bit. Here is the latest version of the coerce.c routine substituteList that fixes the C stack overflow problem as documented in Bug 8141. Comments w

[Rd] a new way to crash R? (PR#8981)

This is a multi-part message in MIME format. --010500030900050501010804 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear R Team, First, thank you for incredibly useful software! Now the bad news: The attached script (or the original ve

Re: [Rd] Bug or not? (PR#8977)

Joerg van den Hoff wrote: > >> Hi, >> >> I am writing this email, because I am not sure if the issue I have >> discovered is a bug or not. >> >> For a few days I have been fiddling around with a small program that >> calculates the reflectance of multilayer dielectric mirrors (eg. bragg >> mirrors

[Rd] package compile error on RHEL x86_64

I am unable to install the gmp package on an x86_64 (Xeon) machine. I have had the same problem with other packages (eg. MCMCpack) as well. I am running Red Hat Enterprise Linux 4.1. I get the following error: g++ -shared -L/usr/local/lib64 -o gmp.so biginteger.o biginteger_operator.o bigintegerR.

[Rd] loading library from network share (PR#8982)

Full_Name: roy kuraisa Version: 2.2.1 OS: Windows XP SP2 Submission from: (NULL) (155.91.28.232) When loading a library from network share drive (e.g., \\nnn\f1\f2\p1), when First.lib is called, the libray name contains "/" instead of "\" resulting in an invalid Windows filepath. Here's an examp

[Rd] Package naming best practices

R-devel, I'm in the process of choosing a name for a new package. I've already decided that the name will have two parts, 'portfolio' and 'sim', but can't decide between 'portfolioSim' and 'portfolio.sim'. Is there any good reason to choose one over the other? Thanks in advance, Jeff -- Jef

Re: [Rd] Package naming best practices

Only personal preferences, although you might argue that the two naming schemes hints at a package using either S3 or S4 methodology. Some packages also has a all cap naming scheme like PortfolioSim. But why not follow part of the R community and choose an incomprehensible abbreviation like