Displaying 20 results from an estimated 500 matches similar to: "How to add points to two plots parallelly ?"
2009 Aug 03
2
scatterplot3d bug??
Hey guys,
Not sure if I encountered a bug with the scatterplot3d function.
Here's the calls I made:
s3d1 <- scatterplot3d(TotLogDisttenp,TotDifftenp,TotMeasuredRSLtenp,pch=16,highlight.3d=TRUE,angle=40,type="h",main="MRSL
~ LogDist + Diff");
s3d1$plane3d(fitols);
s3d1 <-
2020 Nov 06
2
Process to Incorporate Functions from {parallely} into base R's {parallel} package
Hi all,
Henrik Bengtsson has done some fantastic work with {future} and, more importantly, greatly improved constructing and deconstructing a parallelized environment within R. It was with great joy that I saw Henrik slowly split off some functionality of {future} into {parallelly} package. Reading over the package?s README, he states:
> The functions and features added to this package are
2020 Nov 07
2
Process to Incorporate Functions from {parallely} into base R's {parallel} package
FWIW, there are indeed a few low hanging bug fixes in 'parallelly'
that should be easy to incorporate into 'parallel' without adding
extra maintenance. For example, in parallel::makePSOCKcluster(), it
is not possible to disable SSH option '-l USER' so that it can be set
in ~/.ssh/config. The remote user name will be the user name of your
local machine and if you try to
2020 Nov 07
0
Process to Incorporate Functions from {parallely} into base R's {parallel} package
If these are easy changes, maybe someone will incorporate them. You'll
make the argument stronger for doing that if you can explain why it's
better to do that than to keep them in parallely.
Duncan Murdoch
On 07/11/2020 1:39 p.m., Henrik Bengtsson wrote:
> FWIW, there are indeed a few low hanging bug fixes in 'parallelly'
> that should be easy to incorporate into
2020 Nov 07
0
Process to Incorporate Functions from {parallely} into base R's {parallel} package
On 06/11/2020 4:47 p.m., Balamuta, James Joseph wrote:
> Hi all,
>
> Henrik Bengtsson has done some fantastic work with {future} and, more importantly, greatly improved constructing and deconstructing a parallelized environment within R. It was with great joy that I saw Henrik slowly split off some functionality of {future} into {parallelly} package. Reading over the package?s README, he
2013 Oct 16
1
Parallel R expression evaluations
Hi all,
I am using R-3.0.1 under Linux platform to embed R into my C++ code.
I am facing an error while executing more than 1 R-expressions parallelly.
I am executing round(X) and abs(X) parallelly on a set of 50 input rows
which resulted in segmentation fault after getting the following errors.
Error: unprotect_ptr: pointer not found
Error: argument to 'findVar' is not an environment
2024 Feb 18
0
Packages sometimes don't update, but no error or warning is thrown
G'day Philipp,
On Fri, 16 Feb 2024 17:33:13 +0100
Philipp Schneider <philipp-schneider at gmx.net> wrote:
> Thanks for all the input. It's happening again. This time for the
> packages "DBI", "parallelly", "segmented", "survival", "V8". So,
> RStudio shows updates for those and updating them via RStudio leads
> to this
2024 Feb 16
1
Packages sometimes don't update, but no error or warning is thrown
Hey everyone,
Thanks for all the input. It's happening again. This time for the packages "DBI", "parallelly", "segmented", "survival", "V8". So, RStudio shows updates for those and updating them via RStudio leads to this output:
```
> install.packages(c("DBI", "parallelly", "segmented", "survival",
2013 Dec 24
2
Parallel computing: how to transmit multiple parameters to a function in parLapply?
Hi R-developers
In the package Parallel, the function parLapply(cl, x, f) seems to allow
transmission of only one parameter (x) to the function f. Hence in order to
compute f(x, y) parallelly, I had to define f(x, y) as f(x) and tried to
access y within the function, whereas y was defined outside of f(x).
Script:
library(parallel)
f <- function(x) {
z <- 2 * x + .GlobalEnv$y # Try to
2009 Dec 16
0
Read dataset in R language
Hello.
This is to get you started with data.frames, next time please
- read the posting guide
- see the documentation, especially the builtin "R data import/export"
manual form the help menu
## begin R examples, paste into console ##
data(mtcars) # builtin database
class(mtcars) # what it is
mtcars # print it out...
head(mtcars) # ...better: see first rows
fm <- mpg~hp+wt
2020 Apr 16
0
suggestion: "." in [lsv]apply()
This syntax is already implemented in the {purrr} package, more or
less -- you need to add a tilde before your function call for it to
work exactly as written:
purrr::map_dbl(split(mtcars, mtcars$cyl), ~ summary(lm(wt ~ mpg, .))$r.squared)
is equivalent to
sapply(split(mtcars, mtcars$cyl), function(d) summary(lm(mpg ~ wt,
d))$r.squared)
Seems like using this package is probably an easier
2018 Jul 02
2
Is there a large variance in xapian searching?
Dear XAPIAN developers,
I was using xapian to index large than 13 million document about Q &
A(Quora similarly). I will share some performance data about indexing
and searching, and I will seek some help for improving performance of
searching.
My computer has 8 i7 at 3.4G CPU and 16G memory, ubuntu 16.04. Dataset
include about 13M document, each document will be cut into 35
term(Chinese
2020 Apr 19
0
suggestion: "." in [lsv]apply()
You can get pretty close to that already using fn$ in the gsubfn package:
> library(gsubfn)
> fn$sapply(split(mtcars, mtcars$cyl), x ~ summary(lm(mpg ~ wt, x))$r.squared)
4 6 8
0.5086326 0.4645102 0.4229655
It is not specific to sapply but rather fn$ can preface most functions.
If the only free variables are the arguments to the function then you
can omit the left
2020 Apr 16
0
suggestion: "." in [lsv]apply()
Serguei,
> On 17/04/2020, at 2:24 AM, Sokol Serguei <sokol at insa-toulouse.fr> wrote:
>
> Hi,
>
> I would like to make a suggestion for a small syntactic modification of FUN argument in the family of functions [lsv]apply(). The idea is to allow one-liner expressions without typing "function(item) {...}" to surround them. The argument to the anonymous function is
2020 Apr 16
0
suggestion: "." in [lsv]apply()
Passing in a function passes not only an argument list but also an
environment from which to get free variables. Since your function doesn't
pay attention to the environment you get things like the following.
> wsapply(list(1,2:3), paste(., ":", deparse(s)))
[[1]]
[1] "1 : paste(., \":\", deparse(s))"
[[2]]
[1] "2 : paste(., \":\",
2007 Oct 01
4
how to plot a graph with different pch
I am trying to plot a graph but the points on the graph should be
different symbols and colors. It should represent what is in the legend.
I tried using the points command but this does not work. Is there
another command in R that would allow me to use different symbols and
colors for the points?
Thank you kindly.
data(mtcars)
plot(mtcars$wt,mtcars$mpg,xlab= "Weight(lbs/1000)",
2020 Apr 16
0
suggestion: "." in [lsv]apply()
Sergei,
the main problem that I was pointing out is is that there is no way you can introduce the new syntax without breaking the old one. The expression is evaluated to obtain a function, so by definition using anything that results in a valid expression for your syntax will break. E.g., using sapply(x, (foo)) is completely valid so you can't just change the evaluation of the expression to
2018 Jul 21
0
Model formulas with explicit references
> On Jul 20, 2018, at 3:05 PM, Lenth, Russell V <russell-lenth at uiowa.edu> wrote:
>
> Dear R-Devel,
>
> I seem to no longer be able to access the bug-reporting system, so am doing this by e-mail.
>
> My report concerns models where variables are explicitly referenced (or is it "dereferenced"?), such as:
>
> cars.lm <- lm(mtcars[[1]] ~
2020 Apr 16
2
suggestion: "." in [lsv]apply()
I'm sure this exists elsewhere, but, as a trade-off, could you achieve
what you want with a separate helper function F(expr) that constructs
the function you want to pass to [lsv]apply()? Something that would
allow you to write:
sapply(split(mtcars, mtcars$cyl), F(summary(lm(mpg ~ wt,.))$r.squared))
Such an F() function would apply elsewhere too.
/Henrik
On Thu, Apr 16, 2020 at 9:30 AM
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,