Displaying 18 results from an estimated 18 matches similar to: "lapply on long vector fails"
2017 Jun 27
0
Seg Fault memory violation
Greetings all,
Recently ran into a seg fault the keeps reoccurring whenever R-java is used (I believe). Not sure if this is an R issue or an openjdk issue so I'm trying to cover all bases with this report. I tried downgrading R version from 3.4.0 to 3.3.3 with the same results. Also tried downgrading java version from 1.8 to 1.7 with no luck. Running on a fully updated CentOS 7 x86_64,
2007 Apr 19
4
general question about plotting multiple regression results
Hi all,
I have been bumbling around with r for years now and still havent come up
with a solution for plotting reliable graphs of relationships from a
linear regression.
Here is an example illustrating my problem
1.I do a linear regression as follows
summary(lm(n.day13~n.day1+ffemale.yell+fmale.yell+fmale.chroma,data=surv))
which gives some nice sig. results
Coefficients:
2017 Jun 12
2
Possible with enableJIT function
In this email to the R-help list: https://stat.ethz.ch/pipermail/r-help/2017-June/447474.html
and in this question on Stackoverflow: https://stackoverflow.com/questions/44486643/nleqslv-memory-use-in-r
Andrew Leach has raised a question about the memory usage of my package nleqslv.
In a model with a loop within a function he has experienced continuously increasing memory usage
by package nleqslv
2004 Sep 13
6
Spare some CPU cycles for testing lme?
If anyone has a few extra CPU cycles to spare,
I'd appreciate it if you could verify a problem that I
have encountered. Run the code
below and tell me if it crashes your R before
completion.
library(lme4)
data(bdf)
dump<-sapply( 1:50000, function(i) {
fm <- lme(langPOST ~ IQ.ver.cen + avg.IQ.ver.cen, data = bdf,
random = ~ IQ.ver.cen | schoolNR);
cat("
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
2019 Mar 18
2
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
(Bcc: CRAN)
This is a proposal helping CRAN and alike as well as individual
developers to avoid stray R processes being left behind that might be
produced when an example or a package test fails to set up a
parallel::makeCluster().
ISSUE
If a package test sets up a PSOCK cluster and then the master process
dies for one reason or the other, the PSOCK worker processes will
remain running for 30
2017 Dec 14
4
cannot destroy connection (?) created by readLines in a tryCatch
On Thu, Dec 14, 2017 at 7:56 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote:
> Gabor,
>
> You can grab the connection and destroy it via getConnection and then a
> standard close call.
Yeah, that's often a possible workaround, but since this connection
was opened by
readLines() internally, I don't necessarily know which one it is. E.g.
I might open multiple
2007 Aug 23
0
Bug#439207: postgrey: multiple recipients generates slightly different whitelisted message
Package: logcheck
Version: 1.2.57
Severity: normal
Tags: patch
In ignore.d.server/postgrey,
change:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postgrey(\[[0-9]+\])?: action=.+, reason=.+, (delay=.+, )?client_name=.+,
client_address=.+, sender=.*, recipient=.+
to:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postgrey(\[[0-9]+\])?: ([0-9A-F]+: )?action=.+, reason=.+, (delay=.+, )?client_name=.+,
2017 Dec 14
2
cannot destroy connection (?) created by readLines in a tryCatch
Consider this code. This is R 3.4.2, but based on a quick look at the
NEWS, this has not been fixed.
tryCatch(
readLines(tempfile(), warn = FALSE)[1],
error = function(e) NA,
warning = function(w) NA
)
rm(list=ls(all.names = TRUE))
gc()
showConnections(all = TRUE)
If you run it, you'll get a connection you cannot close(), i.e. the
last showConnections() call prints:
?
2012 May 02
1
Help with writing a udev rule
Can someone please help me with writing a udev rule?
I need /dev/ttyUSB0 to automatically have 777 rights when plugged in. I'd like it to only apply to that one specific device.
I'm not sure where to start, what files to look at and also what to write to make it work.
TIA
Brad
This e-mail transmission contains information that is confidential and may be privileged. It is intended only
2012 Oct 26
3
Eaton , Powerare 9120 6kva
Are there driver to this device it works? I trie with 9130 and 9140 driver
but didn't work.
Thanks
Ignacio Fridemberg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20121025/af016ac1/attachment.html>
2017 Jun 13
0
Possible with enableJIT function
Thanks. This should be resolved in R-devel(r72788) and R-patched
(r72789)
Best,
luke
On Mon, 12 Jun 2017, Berend Hasselman wrote:
>
>
> In this email to the R-help list: https://stat.ethz.ch/pipermail/r-help/2017-June/447474.html
> and in this question on Stackoverflow: https://stackoverflow.com/questions/44486643/nleqslv-memory-use-in-r
>
> Andrew Leach has raised a question
2017 Dec 14
0
cannot destroy connection (?) created by readLines in a tryCatch
Gabor,
You can grab the connection and destroy it via getConnection and then a
standard close call. (it actually lists that it is "closed" already, but
still in the set of existing connections. I can't speak to that difference).
> tryCatch(
+ readLines(tempfile(), warn = FALSE)[1],
+ error = function(e) NA,
+ warning = function(w) NA
+ )
[1] NA
>
2017 Dec 15
1
cannot destroy connection (?) created by readLines in a tryCatch
Thanks for tracking this down. Yeah, I should use suppressWarnings(),
you are right.
Although, readLines() might throw another warning, e.g. for incomplete
last lines,
and you don't necessarily want to suppress that.
TBH I am not sure why that warning is given:
? con <- file(tempfile())
? open(con)
Error in open.connection(con) : cannot open the connection
In addition: Warning message:
In
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
2019 Mar 27
0
SUGGESTION: Proposal to mitigate problem with stray processes left behind by parallel::makeCluster()
The problem causing the stray worker processes when the master fails to
open a server socket to listen to connections from workers is not
related to timeout in socketConnection(), because socketConnection()
will fail right away. It is caused by a bug in checking the setup
timeout (PR 17391).
Fixed in 76275.
Best
Tomas
On 3/18/19 2:23 AM, Henrik Bengtsson wrote:
> (Bcc: CRAN)
>
>
2017 Dec 14
0
cannot destroy connection (?) created by readLines in a tryCatch
On Thu, Dec 14, 2017 at 12:17 PM, G?bor Cs?rdi <csardi.gabor at gmail.com>
wrote:
> On Thu, Dec 14, 2017 at 7:56 PM, Gabriel Becker <gmbecker at ucdavis.edu>
> wrote:
> > Gabor,
> >
> > You can grab the connection and destroy it via getConnection and then a
> > standard close call.
>
> Yeah, that's often a possible workaround, but since this
2017 Dec 14
0
cannot destroy connection (?) created by readLines in a tryCatch
This has nothing to do with on.exit. It is an iteraction between where
the warning is signaled in 'file' and your _exiting_ warning handler.
This combination has the same issue,
tryCatch(file(tempfile(), "r"), warning = identity)
showConnections(all = TRUE)
as does
options(warn=2)
file(tempfile(), "r")
showConnections(all = TRUE)
I haven't looked at the
2003 Mar 26
3
Samba 3.0 - a bunch of really high level questions
Hello everyone... I am a long time samba user (3 or 4 years), though I
never ventured into the alpha stages until recently (alpha 21, I'll move
to 22 in the near future once I get a better idea of what's going on). I
am very interested in Samba being part of a ADS domain, but I have been
a little frustrated due to the lack of documentation. Specifically, I've
read the HOWTO's from
2015 May 03
2
[LLVMdev] libiomp, not libgomp as default library linked with -fopenmp
A couple more data points. Current llvm 3.7svn with the two outstanding
OPENMP patches can build the openmp support in gdl 0.9.5 (which completely
passes its test suite) and apbs 1.4.1's limited openmp support.
On Sat, May 2, 2015 at 11:11 PM, Jack Howarth <
howarth.mailing.lists at gmail.com> wrote:
> On a positive note, current llvm 3.7svn with the two outstanding
> OPENMP