similar to: confint Attempts to Use All Server CPUs by Default

Displaying 20 results from an estimated 1000 matches similar to: "confint Attempts to Use All Server CPUs by Default"

2024 May 21
1
confint Attempts to Use All Server CPUs by Default
? Tue, 21 May 2024 08:00:11 +0000 Dario Strbenac via R-devel <r-devel at r-project.org> ?????: > Would a less resource-intensive value, such as 1, be a safer default > CPU value for confint? Which confint() method do you have in mind? There is at least four of them by default in R, and many additional classes could make use of stats:::confint.default by implementing vcov(). >
2024 May 22
1
confint Attempts to Use All Server CPUs by Default
Following up on this -- on my system, I have 69 packages installed that appear to provide something like a confint() method: h <- help.search("confint", agrep = FALSE) p <- sort(unique(h$matches$Package)) length(p) ## [1] 69 p [1] "bamlss" "bbmle" "binom" "brglm2" [5] "broom"
2016 Aug 04
1
R, OpenBLAS and OMP_NUM_THREADS
Hi, I was be half asleep in the heat ... 2016-08-04 0:04 GMT+09:00 Dirk Eddelbuettel <edd at debian.org>: > > On 3 August 2016 at 16:45, Gordon Ball wrote: > | On 02/08/16 03:10, Ei-ji Nakama wrote: > | > Hi, > | > > | > Create /etc/profile.d/openblas.sh. > | > Write the following during in this file. > | > OPENBLAS_NUM_THREADS = 1 > | > export
2016 Aug 03
2
R, OpenBLAS and OMP_NUM_THREADS
On 02/08/16 03:10, Ei-ji Nakama wrote: > Hi, > > Create /etc/profile.d/openblas.sh. > Write the following during in this file. > OPENBLAS_NUM_THREADS = 1 > export OPENBLAS_NUM_THREADS > > OPENBLAS_NUM_THREADS environment variable does not affect the OMP_NUM_THREADS. > Thanks for the response. This works fine for R run from the command line (as does setting the same
2016 Jan 15
1
Multiple cores are used in simple for loop
Dear Martyn, On Fr, Jan 15, 2016 at 4:01 , Martyn Plummer <plummerm at iarc.fr> wrote: > > Alternatively, you may be able to control the maximum number of > threads > by setting and exporting an appropriate environment variable depending > on what backend you are using, e.g. OPENBLAS_NUM_THREADS or > MKL_NUM_THREADS. Thanks a lot. Running export OPENBLAS_NUM_THREADS
2012 Mar 09
2
How do I force confint() for glm() to be quiet?
I need confint() for glm() to supress the messages "Waiting for profiling to be done..." because they mess up the caching mechanism of pgfSweave (see https://github.com/cameronbracken/pgfSweave/issues/40). I have read the help page of confint(), but I do not know how to get the help page for the glm() version, if any such help page exists. Is there a general way of turning of output
2009 Dec 07
5
confint for glm (general linear model)
Hi, I have a glm gives summary as follows, Estimate Std. Error z value Pr(>|z|) (Intercept) -2.03693352 1.449574526 -1.405194 0.159963578 A 0.01093048 0.006446256 1.695633 0.089955471 N 0.41060119 0.224860819 1.826024 0.067846690 S -0.20651005 0.067698863 -3.050421 0.002285206 then I use confint(k.glm)
2016 Aug 01
2
R, OpenBLAS and OMP_NUM_THREEADS
What is the correct way to globally configure R to default to single (or at least, << NUM_CPUS) threaded operation? Using R 3.3.1 (both in debian unstable or using the CRAN repository for xenial) with OpenBLAS (0.2.18) defaults to using one thread per available CPU, which isn't ideal for machines more than a couple of CPUs. Setting the environment (OMP_NUM_THREADS or
2001 Sep 13
2
trouble locating confint function/ nls library/
A non-text attachment was scrubbed... Name: not available Type: text/enriched Size: 3706 bytes Desc: not available Url : https://stat.ethz.ch/pipermail/r-help/attachments/20010913/b4135232/attachment.bin
2018 Jul 20
3
Should there be a confint.mlm ?
It seems that confint.default returns an empty data.frame for objects of class mlm. For example: ``` nobs <- 20 set.seed(1234) # some fake data datf <- data.frame(x1=rnorm(nobs),x2=runif(nobs),y1=rnorm(nobs),y2=rnorm(nobs)) fitm <- lm(cbind(y1,y2) ~ x1 + x2,data=datf) confint(fitm) # returns: 2.5 % 97.5 % ``` I have seen proposed workarounds on stackoverflow and elsewhere, but
2004 Jul 13
2
confint.glm in a function
I can't get confint.glm to work from within a function. Consider the following (using R 1.9.1, Windows 2000): # FIRST: SOMETHING THAT WORKS FROM A COMMAND PROMPT DF <- data.frame(y=.1, N=100) (fit <- glm(y~1, family=binomial, data=DF, weights=DF[,"N"])) Call: glm(formula = y ~ 1, family = binomial, data = DF, weights = DF[, "N"]) Coefficients:
2011 Feb 11
2
Problem with confint function
Hi, I am currently doing logistic regression analyses and I am trying to get confidence intervals for my partial logistic regression coefficients. Supposing I am right in assuming that the formula to estimate a 95% CI for a log odds coefficient is the following: log odds - 1.96*SE to log odds + 1.96*SE then I am not getting the right CI. For instance, this is a summary of my model:
2007 Dec 05
1
confint for coefficients from lm model (PR#10496)
Full_Name: Christian Lajaunie Version: 2.5.1 OS: Fedora fc6 Submission from: (NULL) (193.251.63.39) confint() does not use the appropriate variance term when the design matrix contains a zero column (which of course should not happen). Example: A 10x2 matrix with trivial column 1: > junk <- data.frame(x=rep(0,10), u=factor(sample(c("Y", "N"), 10, replace=T))) The
2024 Aug 07
1
Another issue using multi-processing linear algebra libraries
I also have this questions for this. I wonder if R initiates a system environment or options to instruct the packages on the number of cores to use? It doesn't have to be mandatory for now, but at least package maintainers can have shared consensus and start to adopt this humble settings rather than abusing parallel::detectCores() to max out the number of threads by default. > On Aug 7,
2012 Jan 18
4
confint function in MASS package for logistic regression analysis
I have the following binary data set: Sex Response 0 1 0 159 162 1 4 37 My commands library(MASS) sib.glm=glm(sib~sex,family=binomial,data=sib.data) summary(sib.glm) The coefficients in the output are Estimate Std. Error z value Pr(>|z|) (Intercept) -3.6826 0.5062 -7.274 3.48e-13
2011 Aug 02
1
How to 'mute' a function (like confint())
Dear R-helpers, I am using confint() within a function, and I want to turn off the message it prints: x <- rnorm(100) y <- x^1.1+rnorm(100) nlsfit <- nls(y ~ g0*x^g1, start=list(g0=1,g1=1)) > confint(nlsfit) Waiting for profiling to be done... 2.5% 97.5% g0 0.4484198 1.143761 g1 1.0380479 2.370057 I cannot find any way to turn off 'Waiting for. .." I tried
2019 Apr 24
1
Bug in "stats4" package - "confint" method
Dear R developers, I noticed a bug in the stats4 package, specifically in the confint method applied to ?mle? objects. In particular, when some ?fixed? parameters define the log likelihood, these parameters are stored within the mle object but they are not used by the ?confint" method, which retrieves their value from the global environment (whenever they still exist). Sample code: >
2003 Nov 17
1
confint: which method attached?
the function confint uses the profiling method of the function of the package MASS confint.glm even after the package has been detached! 1: might this be the intenden behavior? 2. How does the function remember its 'MASS' functionality after detaching the package? R: 1.8.0; Windows 2000 Here is a sample program > set.seed(7882) > x<-rep(c(0,1),c(20,20)) >
2009 Oct 02
1
confint fails in quasibinomial glm: dims do not match
I am unable to calculate confidence intervals for the slope estimate in a quasibinomial glm using confint(). Below is the output and the package info for MASS. Thanks in advance! R 2.9.2 MASS 7.2-48 > confint(glm.palive.0.str) Waiting for profiling to be done... Error: dims [product 37] do not match the length of object [74] > glm.palive.0.str Call: glm(formula = cbind(alive, red) ~ str,
2005 Dec 22
3
Windows crash in confint() with nls fit (PR#8428)
Full_Name: Ben Bolker Version: 2.2.1 OS: Windows XP and 2000 Submission from: (NULL) (128.227.60.124) The following code, using confint() to try to get confidence intervals on an nls object that has been fitted with algorithm="port" reliably crashes R 2.2.0 and 2.2.1 with the latest version of MASS on a Windows 2000 and a Windows XP machine here. I *think* earlier versions of MASS