Displaying 20 results from an estimated 20000 matches similar to: "documentation for legend(): possible missing info for pch."
2001 Jul 25
2
pch with plot and legend
I'm trying to plot a scatterplot of two variables using pch to plot
different characters based on a third factor. Here is my example
> data("ToothGrowth")
> attach(ToothGrowth)
> levels(supp)
[1] "OJ" "VC"
> plot(len ~ dose,pch=as.numeric(supp))
> legend(locator(1),pch=as.numeric(supp),legend=levels(supp))
The command as.numeric(supp) returns 2 2
2008 Nov 04
1
problem with plot style (pch) with lattice in legend
Un texte encapsul? et encod? dans un jeu de caract?res inconnu a ?t? nettoy?...
Nom : non disponible
URL : <https://stat.ethz.ch/pipermail/r-help/attachments/20081104/b667d8da/attachment.pl>
2019 Nov 30
2
Inconsistent behavior for the C AP's R_ParseVector() ?
Hi again,
Beside R_ParseVector()'s possible inconsistent behavior, R's handling of
zero-length named elements does not seem consistent either:
```
> lst <- list()
> lst[[""]] <- 1
> names(lst)
[1] ""
> list("" = 1)
Error: attempt to use zero-length variable name
```
Should the parser be made to accept as valid what is otherwise possible
2017 Jan 01
3
Definition of uintptr_t in Rinterface.h
On 29/12/2016 15:55, Simon Urbanek wrote:
> The problem is elsewhere - Rinterface.h guards the ultima-ratio fallback with HAVE_UINTPTR_T but that config flag is not exported in Rconfig.h. Should be now fixed in R-devel - please check if that works for you.
Rconfig.h would be appropriate if Rinterface.h is being included from C
code using the same compiler as used for R. But as Rinterface.h
2019 Dec 07
2
Inconsistent behavior for the C AP's R_ParseVector() ?
Thanks for the quick response Tomas.
The same error is indeed happening when trying to have a zero-length
variable name in an environment. The surprising bit is then "why is this
happening during parsing" (that is why are variables assigned to an
environment) ?
We are otherwise aware that the error is not occurring in the R console,
but can be traced to a call to R_ParseVector() in
2017 Jan 02
1
Definition of uintptr_t in Rinterface.h
> On Jan 1, 2017, at 5:12 PM, Laurent Gautier <lgautier at gmail.com> wrote:
>
>
>
> 2017-01-01 8:28 GMT-05:00 Prof Brian Ripley <ripley at stats.ox.ac.uk>:
> On 29/12/2016 15:55, Simon Urbanek wrote:
> The problem is elsewhere - Rinterface.h guards the ultima-ratio fallback with HAVE_UINTPTR_T but that config flag is not exported in Rconfig.h. Should be now
2018 Oct 07
4
Warning when calling formals() for `[`.
Hello,
I don't see why you say that the documentation seems to be wrong:
class(args(`+`))
#[1] "function"
args() on a primitive does return a closure. At least in this case it does.
Rui Barradas
?s 14:05 de 07/10/2018, Peter Dalgaard escreveu:
> There is more "fun" afoot here, but I don't recall what the point may be:
>
>> args(get("+"))
2008 Aug 11
1
line with of the symbols in the legend -- changable?
Dear R users,
I plot data with
points(my_data[x]~x, col = x, type = "o", lwd="4")
where x is an integer running from 1 to 10, I get points drawn at the plot.
When want to do a legend to this I try
legend(leg.txt[x], col = x, text.col = 1, pch = 1, bty = "n")
where leg.txt contains the names of the variable and x behaves the same. The
difference between the
2016 Dec 27
3
Definition of uintptr_t in Rinterface.h
Hi,
I was recently pointed out that a definition in Rinterface.h can be conflicting
with a definition in stdint.h:
/usr/include/R/Rinterface.h has:
typedef unsigned long uintptr_t;
/usr/include/stdint.h has:
typedef unsigned int uintptr_t;
(when 32bit platform complete definition is:
#if __WORDSIZE == 64
# ifndef __intptr_t_defined
typedef long int intptr_t;
# define
2019 Dec 14
2
Inconsistent behavior for the C AP's R_ParseVector() ?
Le lun. 9 d?c. 2019 ? 09:57, Tomas Kalibera <tomas.kalibera at gmail.com> a
?crit :
> On 12/9/19 2:54 PM, Laurent Gautier wrote:
>
>
>
> Le lun. 9 d?c. 2019 ? 05:43, Tomas Kalibera <tomas.kalibera at gmail.com> a
> ?crit :
>
>> On 12/7/19 10:32 PM, Laurent Gautier wrote:
>>
>> Thanks for the quick response Tomas.
>>
>> The same error
2008 Jul 28
1
cairo device and pch="+"
Dear list,
I have spotted what could be a memory leak somewhere.
The example below shows how to quickly use up RAM on a linux machine
(the example is taylored for a 2Gb machine, change the size of the matrix m
is needed).
# ---
m <- matrix(rnorm(130), nrow=6000, 6)
X11(type="cairo")
pairs(m)
# --- here the trouble starts (monitor the memory usage as the plot goes).
pairs(m,
2017 Mar 24
2
Error in documentation for ?legend
To whom it may concern:
The help page for ?legend refers to a `title.cex` parameter, which suggests that the function has such a parameter. As far as I can tell, though, it doesn't; here's an example:
> plot(1,1)
> legend("topright",pch=1, legend="something", title="my legend", title.cex=2)
Error in legend("topright", pch = 1, legend =
2019 Dec 14
1
Inconsistent behavior for the C AP's R_ParseVector() ?
Hi Simon,
Widespread errors would have caught my earlier as the way that code is
using only one initialization of the embedded R, is used quite a bit, and
is covered by quite a few unit tests. This is the only situation I am aware
of in which an error occurs.
What is a "correct context", or initial context, the code should from ?
Searching for "context" in the R-exts manual
2019 Dec 09
3
Inconsistent behavior for the C AP's R_ParseVector() ?
Le lun. 9 d?c. 2019 ? 05:43, Tomas Kalibera <tomas.kalibera at gmail.com> a
?crit :
> On 12/7/19 10:32 PM, Laurent Gautier wrote:
>
> Thanks for the quick response Tomas.
>
> The same error is indeed happening when trying to have a zero-length
> variable name in an environment. The surprising bit is then "why is this
> happening during parsing" (that is why
2019 Nov 30
2
Inconsistent behavior for the C AP's R_ParseVector() ?
Hi,
The behavior of
```
SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP);
```
defined in `src/include/R_ext/Parse.h` appears to be inconsistent depending
on the string to be parsed.
Trying to parse a string such as `"list(''=1+"` sets the
`ParseStatus` to incomplete parsing error but trying to parse
`"list(''=123"` will result in R sending a message to the
2018 Oct 06
5
Warning when calling formals() for `[`.
Hi,
A short code example showing the warning might the only thing needed here:
```
> formals(args(`[`))
NULL
*Warning message:In formals(fun) : argument is not a function*
> is.function(`[`)
[1] TRUE
> is.primitive(`[`)
[1] TRUE
```
Now with an other primitive:
```
> formals(args(`sum`))
$...
$na.rm
[1] FALSE
> is.function(`sum`)
[1] TRUE
> is.primitive(`sum`)
[1] TRUE
2017 Mar 25
2
Error in documentation for ?legend
Right, that's my point. The help page mentions a `title.cex`, like I said; saying that `cex` sets the default `title.cex` sure implies to me (and presumably to the other people whose discussion I linked) that a `title.cex` parameter exists. Since no such parameter exists, this bit in the documentation is misleading (suggesting that there is a `title.cex` parameter which can be set, when there
2019 Sep 08
6
Error: package or namespace load failed for ‘utils
Hi,
When starting an embedded R I encounter the following issue under certain
conditions:
```
Error: package or namespace load failed for ?utils? in if (.identC(class1,
class2) || .identC(class2, "ANY")) TRUE else {:
missing value where TRUE/FALSE needed
```
(more such errors for grDevices, graphics, and stats)
And in the end:
```
Warning messages:
1: package ?utils? in
2015 May 04
2
C-API: check whether R has been initialized ?
rPython appears to provide an interface from R to Python by embedding
Python and I'd think that it can safely assume that R has been initialized,
but might not be the point here.
The issue is that a Python package embedding itself R (here rpy2) appears
to have no way to know that earlier in the life of the process R was
initialized.
2015-05-03 19:48 GMT-04:00 Duncan Murdoch
2006 Sep 03
4
How can I fit the secondary y axis legend on my graph?
Dear All,
Having a bit of trouble with plotting two y variables on the same
graph. I cannot manage to get the secondary y axis label on to the right
of the axis - it gets plotted beyond the graphic window I assume?! The
way I constructed the graph is thus:
plot(data[,3],data[,2],axes=F, type="b") ## plots my data from two
data colums without axes - fine
axis(1, at=data[,3])