similar to: question about ... passed to two different functions

Hello list, I'm trying to make sure that I'm performing a path analysis correctly using the sem package. the figure at http://flame.cs.dal.ca/~sstewart/regressDiag.png has a detailing of the model. The challenge I'm having is that reuse is an indicator (0/1) variable. Here's the code I'm using: corr =

The functions metrop and temper in the mcmc package have a debug = FALSE argument that when TRUE adds a lot of debugging information to the returned list. This is absolutely necessary to test the functions, because one generally knows nothing about the simulated distribution except what what one learns from MCMC samples. Hence you must expose all details of the simulation to have any hope of

Hello all, I have a large parameter problem with the following very simple likelihood function: fn<-function(param) { x1<-param[1:n] g1<-param[(n+1):(2*n)] beta<-param[(2*n+1):(2*n+k)] sigma2<-param[2*n+k+1]^2 meang1sp<-mean(g1[sp]) mu<-beta%*%matrix(x1,1,n)-(g1[sp]-meang1sp)%*%matrix(g1,1,n) return(sum((ydc-mu)^2)/(2*sigma2) + n*k*log(sqrt(sigma2)) +

Dear R-users (and developers), I am looking for an efficient framework to carry out parameter estimations based on MCMC (optionally with specified priors). My goal is as follow: * take ANY R-function returning a likelihood-value (this function may itself call external programmes or other code!) * run a sampler that covers the multidimensional parameter space (thus creating a posterior

Hi list, I am writing several functions and running out variable names. I am using words such as "t", "c", "matrix" to keep the notation same as formulas I am using. For example I have, unnormalized <- function(t, x, y){ val <- rnorm(t, mean=x, var=y) return(val) } metropolis <- function(t, c, x, y){ den1 <- unnormalized(t, mean=x, sd=y)

Hi Duncan et al, Our linker guy brought up a problem with how we pad out our exception tables. Right now we pad them out like this: .section __DATA,__gcc_except_tab .align 2 GCC_except_table13: .byte 0x0 #< --- hun? .byte 0x0 #< --- hun? Lexception13: .byte 0xFF .byte 0x0 .byte 0xB2, 0x1 > Here are his comments: The problem is that the linker parses FDE which gives it

Hi Bill, > It looks like your goal is to keep the 32-bit pointers in the call-site table 4-byte aligned. Here is another solution, instead of having two labels at the start of the LSDA (with pad bytes between them), have no pad bytes and instead use an unnormalized uleb128 for the call-site table length. By unnormalized, I mean one with leading zeros. For instance, instead of: this sounds

> I was wondering why survreg (in survival package) can not handle > three-way interactions. I have an AFT ..... You have given us no data to diagnose your problem. What do you mean by "cannot handle" -- does the package print a message "no 3 way interactions", gives wrong answers, your laptop catches on fire when you run it, ....? Also, make sure you read

Hi I am using metrop in MCMC library.  Since some times the prior density is 0 and the log prior density would be –Inf, I ask the return value for loglikelihood equal to Min.log, which is defined as log(.Machine$double.xmin)-400, whenever a –Inf occurs to the logdensity.  However, I noticed if two Min.log’s happen in a row, the sampled parameter value for the second Min.log is treated as

Hola! I have the following in a .Rd file: \eqn{\mbox{coef} = c(\mbox{coef}[1],\ldots, \mbox{coef}[n]) } {coef = c(coef[1], coef[2], \dots, coef[n])} However, both arguments come out in the latex file! Whats happening? Kjetil Halvorsen

I have a package with in the documentation: in \usage : \dots in \arguments: \ldots This is how I interpreted "Use \dots for the dots in function argument lists ..., and \ldots for ellipsis dots in ordinary text" in "Writing R Extensions". When I did `R CMD check' in R version 1.3.1 all was fine. With R version 1.4.0 I get : * checking for undocumented arguments

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields

This set of two patches adds a new field called default_mtu to the configuration area of network devices. The motivation is to allow libvirt to set initial MTU different from 1500 on guests virtual NICs. We also propose to use this new field to report MTU changes by the guest OS to the device to facilitate debugging and mtu tunning. The first patch just clarify the definition of existing fields

>> It looks like your goal is to keep the 32-bit pointers in the call-site table 4-byte aligned. Here is another solution, instead of having two labels at the start of the LSDA (with pad bytes between them), have no pad bytes and instead use an unnormalized uleb128 for the call-site table length. By unnormalized, I mean one with leading zeros. For instance, instead of: > > this sounds

On Feb 5, 2010, at 4:00 PM, Duncan Sands wrote: > Hi Bill, > >> It looks like your goal is to keep the 32-bit pointers in the call-site table 4-byte aligned. Here is another solution, instead of having two labels at the start of the LSDA (with pad bytes between them), have no pad bytes and instead use an unnormalized uleb128 for the call-site table length. By unnormalized, I mean one

Clarify general description of the mac, status and max_virtqueue_pairs fields. Specifically, the old description is vague about configuration layout and fields offsets when some of the fields are non valid. Also clarify that validity of two status bits depends on two different feature flags. Signed-off-by: Victor Kaplansky <victork at redhat.com> --- content.tex | 42

On Mon, Aug 17, 2015 at 10:43:46AM +0800, Jason Wang wrote: > > > On 08/16/2015 09:42 PM, Victor Kaplansky wrote: > > Clarify general description of the mac, status and > > max_virtqueue_pairs fields. Specifically, the old description is > > vague about configuration layout and fields offsets when some of > > the fields are non valid. > > > > Also

On Mon, Aug 17, 2015 at 10:43:46AM +0800, Jason Wang wrote: > > > On 08/16/2015 09:42 PM, Victor Kaplansky wrote: > > Clarify general description of the mac, status and > > max_virtqueue_pairs fields. Specifically, the old description is > > vague about configuration layout and fields offsets when some of > > the fields are non valid. > > > > Also

Hi, I wanted to know if there existed an good implementation in R of the following classical subset Integers : $P_{n,m} = {k_1, \ldots, k_m \in \mathbb{N} : k_1 + \ldots + k_m = n }$ for any integers $m < n$. There is an obvious not optimal code which would be to run through $m$ sums and put a boolean condition to report if the integers respect these condition but it would take $m^n$

Hola. Intento crear un archivo .html a partir de un .Rmd que tenga Toc, LaTeX y tablas. Empleo RStudio (v. 0.97.551), pero aparece un error en la función "markdownToHTML" Pasos: 1) creo un fichero Rmd (adjunto ejemplo) => con knitr (v. 1.0.5) crea un fichero ".md" 2) Si quiero añadirle el TOC (table of contents) necesito emplear la función "markdownToHTML" del