search for: pnames

As far as I know this patch has no security implications -- I don't believe that allowing sshd to use get_local_name() (in canohost.c) on a connected socket to determine it's own fqdn will allow a malicious client (or router or dns server) to make it come to the wrong conclusion. But please let me know if you think I'm wrong. Please also let me know if you're just not interested

In preparation for adding other optional flag arguments to the python bindings, start by making the existing 'may_trim' flag to 'zero' be optional. That is, the plugin need not define the parameter if it does not make any semantic difference (ie. if the plugin ignores the hint and never trims); while if the parameter exists, we now pass it as a keyword argument rather than as a

In trying to create a plotmath expression for plot labeling, such as R = 6, beta = 15 where I want beta to be the Greek beta and, possibly, R in italics (like one would get in an explicit expression. The reason for this is that I want to write a string builder function that takes vectors of variable names and their values and return a plotmath expression for labeling a plot. One approach I

In preparation for adding other optional flag arguments to the python bindings, start by making the existing 'may_trim' flag to 'zero' be optional. That is, the plugin need not define the parameter if it does not make any semantic difference (ie. if the plugin ignores the hint and never trims); while if the parameter exists, we now pass it as a keyword argument rather than as a

Hi, Again, sorry for the length of this post. Once I get my new office I will get a website set up on my work machine and will simply post a link to the log since I doubt many people are truly interested in these logs. To further analyze what is happening, I added my own routine in main.c called DEBUG_SET_NAMED and then redefined the SET_NAMED macro to use it and then rebuilt R. I

FYI >Mailing-List: contact vulnwatch-help@vulnwatch.org; run by ezmlm >List-Post: <mailto:vulnwatch@vulnwatch.org> >List-Help: <mailto:vulnwatch-help@vulnwatch.org> >List-Unsubscribe: <mailto:vulnwatch-unsubscribe@vulnwatch.org> >List-Subscribe: <mailto:vulnwatch-subscribe@vulnwatch.org> >Delivered-To: mailing list vulnwatch@vulnwatch.org

...L-BFGS-B") ## --> works without problems ## 3) THE PROBLEM nlminb(start, hdev, lower = 0.001, upper = Inf) ## --> $objective is NA because names of "start" are not passed through ## 4) workaround ------------------------------------------------------- hdev <- function(par, pnames) { names(par) <- pnames -sum(dnbinom(x, mu = par["mu"], size = par["size"], log = TRUE)) } nlminb(start, hdev, pnames = names(start), lower = 0.001, upper = Inf) ## --> works, but is it possible to improve nlminb ## so that the workaround can be avoided ?...

This Index: src/main/altrep.c =================================================================== --- src/main/altrep.c (revision 79385) +++ src/main/altrep.c (working copy) @@ -275,10 +275,11 @@ SEXP psym = ALTREP_SERIALIZED_CLASS_PKGSYM(info); SEXP class = LookupClass(csym, psym); if (class == NULL) { - SEXP pname = ScalarString(PRINTNAME(psym)); + SEXP pname =

...intervals are computed for all parameters anyway, and then assigned to a matrix which is too small for all of them (see function body below). As I said, I think it's worth knowing it. Best, Giovanni > confint.lm function (object, parm, level = 0.95, ...) { cf <- coef(object) pnames <- names(cf) if (missing(parm)) parm <- seq(along = pnames) else if (is.character(parm)) parm <- match(parm, pnames, nomatch = 0) a <- (1 - level)/2 a <- c(a, 1 - a) pct <- paste(round(100 * a, 1), "%") ci <- array(NA, dim = c...

Dear all, I am trying to gain some experience with the function gnls from the nlme package. I tried to model the Theophyline data by trying to model the presumed dependency of the clearance on the body weight. This is my function call of gnls: gnls(conc~SSfol(Dose,Time,lKe,lKa,lCl),data=Theoph, params=list(lKe~1,lKa~1,lCl~Wt),start=c(-2.4,0.46,-3.22,0.01)) That's been the result: Error

...r-project.org/plugins/scmsvn/viewcvs.php/*checkout*/pkg/R/utilities.R?rev=2&root=rcmdr>). However, with a few minor changes, the function in the nnet package could work as I had expected it to: confint.mult<-function (object, parm, level = 0.95, ...) { cf <- coef(object) pnames <- if (is.matrix(cf)) colnames(cf) else names(cf) if (missing(parm)) parm <- seq_along(pnames) else if (is.character(parm)) parm <- match(parm, pnames, nomatch = 0) a <- (1 - level)/2 a <- c(a, 1 - a) pct <- paste(round(1...

Dear all, I was trying to see how the function 'confint' is defined. Doing > confint function (object, parm, level = 0.95, ...) UseMethod("confint") <environment: namespace:stats> does not really enlighten me. How can I get to see the implementation (I guess it should be possible according to the general philosophy of the R project)? Thanks in advance S??ren

Dear All, I'm running into issues with calling mccollect on a list containing NULL using R 3.6 (this used to work in 3.5.3): jobs <- lapply( list(NULL, 'foobar'), function(x) mcparallel(identity(x))) mccollect(jobs, wait = FALSE, timeout = 0) #> Error in names(res) <- pnames[match(s, pids)] : #> 'names' attribute [2] must be the same length as the vector [1] Note, setting a "name" for the jobs does not help, but the above works with "wait=TRUE", and also if I change the order of NULL and "foobar", although in that case, the s...

Hi I have the following formula (I hope it is clear - if no, I can try to do better the next time) h(x, a, b) = integral(0 to pi/2) ( ( integral(D/sin(alpha) to Inf) ( ( f(x, a, b) ) dx ) dalpha ) and I want to do an mle with it. I know how to use mle() and I also know about integrate(). My problem is to give the parameter values a and b to the

...am getting nowhere. Could someone point me to some references beyond the standard documentation that might help. Here's my latest attempt: BuildParString = function(params) { nPar = length(params) # params is a vector of numerical values s = NULL if(nPar < 1) { return } pNames = c("R","P[m]","k[a]","alpha[r]","beta[r]","phi") vparams = format(params,digits=3) s = as.expression(substitute(pp==vv,list(vv=vparams[1],pp=pNames[1]))) for(i in 2:nPar) { s = c(s,eval(as.expression(substitute(expression(pp==vv)...

...e of the parameters to be plotted. annotate: Logical value indicating that a legend be included in the plot. I tried boa.plot.trace(B) and boa.plot.trace(B,"B") but both do not give me a trace plot for chain B and print FALSE. I am obviously misinterpreting lnames and pnames. Can anyone help please? Thanks in advance Emma -- View this message in context: http://r.789695.n4.nabble.com/more-boa-plots-questions-tp3330312p3330312.html Sent from the R help mailing list archive at Nabble.com.

When I run notepad or sthing that needs winspool I get : err:winspool:AddPrinterW pName = L"" - unsupported err:winspool:PRINTCAP_ParseEntry lp not added by AddPrinterA (87) What should I do fix it ? The docu didnt help about this. (Perhaps it should be updated, as the psdrv.reg doesnt exist anymore.) [syl@snoop Temp]$ notepad --debugmsg +winspool trace:winspool:AddPrinterDriverA

Hi, I am little bit interested in Wine source code. There is one thing I don't understand. How does HeapAlloc() work? Is it the same behavior as Winapi HeapAlloc()? If so then I have to check NULL value after each calling of this function, don't I? I have found this code in Wine 0.9.57: In dlls/dbghelp/stabs.c function 'static int stabs_new_include(const char* file, unsigned long

hi Jerry et al, when I use the 'ADD PRINTER WIZARD' it looks like this: ----------------------------------------- |[]\\whatevernthost\mydeskjetanywhere | |[]\\computeronmydesk\printernexttome | |[]\\Ididn'tevennowIm\sharingaprinter | |+[]SAMBAPRINTSERVER | ----------------------------------------- The shared printers on the SAMBA server get visible by

I'm trying to track down a bug in some experimental code, where an object's attribute is getting messed up. This means I'd like to examine R objects while within gdb. One of the things I'd like to do is to examine the names of all the attributes. This is exactly what an example in the R Extensions manual section 4.11.2 "Inspecting R objects when debugging" does,