Displaying 20 results from an estimated 10000 matches similar to: "selecting unique columns of a matrix/data frame"
2004 Aug 26
2
text() with text, variables and math HOWTO?
Hello,
One more question from the 'abusing R for blotting - particularly
anally' department:
How can I in the expression below make the '%~~%' show up as the
aprrox-sign I want it to be?
Thanks for any hint,
Joh
text(
500,1.5,
cex=0.75,
substitute(
paste(
OD[600][~nm],
" of 1 at ",
time1,
" min ",
"%~~%",
time1h,
2004 May 01
0
log(0) error is not handled in xyplot, Windows
Hi,
We had some exchanges off the list with Deepayan Sarkar about a bug (?) we cannot fix (it seems it does not occur under Unix). It
likely needs the help of somebody on Windows.
The initial problem was that when running the following script (Windows XP, R 1.8.1 as well as R 1.9.0):
> lset(col.whitebg())
> xyplot(rdens ~ annee | habitat,
> groups = sp, type = 'b',
>
2009 Jun 30
0
bug in nlme package function predict.lmList (PR#13788)
Full_Name: Vaidotas Zemlys
Version: 2.9.0
OS: Ubuntu 8.10
Submission from: (NULL) (213.197.173.50)
Steps to reproduce the bug:
library(nlme)
data(Oxboys)
qm=lmList(height~age|Subject,data=Oxboys)
grid=with(Oxboys,expand.grid(age=seq(min(age),max(age),length=50),Subject=levels(Subject)))
res <- predict(qm,grid,se=TRUE)
Erreur dans if (pool) { : l'argument est de longueur nulle
res <-
2005 Jun 02
0
Thanks! (was panel.axis() & grid/lattice settings)
Deepayan, Paul:
Thanks very much for the very useful leads. I just spent some time this
afternoon implementing your suggestions and my early test results are very
encouraging.
Paul, I understand the potential device re-sizing issue with the convert
family of functions in grid, and will be in touch in case it becomes
problematic for my applications. I very much look forward to your upcoming
2009 Feb 16
0
problem with gls finding model terms without specifying data=named.object
Hello R-help
I am having trouble getting gls to find the R objects that comprise a linear model when the data=named.object option(option!) is not specified. In the gls() help it states data is "an optional data frame containing the variables named in model, correlation, weights, and subset. By default the variables are taken from the environment from which gls is called".
An example:
2010 Jun 15
1
Fwd: Re: "Graphics history" in UNIX
Many thanks again for your code.
Actually, manual typing of the function names to record or review plots
is not a practical solution for me.
I taught it would be a quick task to program Function keys for this purpose.
I uselessly spent time messing with a "<home>.initrc " file.
The only solution I found is to write the functions names, via Bash
menu
2002 Dec 16
1
Lattice: panel.superpose function does not pass subscripts and groups arguments (PR#2377)
Full_Name: Volker Franz
Version: 1.5.1
OS: Debian-Linux
Submission from: (NULL) (134.176.77.64)
Hi,
working with the panel.superpose function, I found out that this
function does not pass the subscripts and groups arguments to
panel.groups functions.
In my view, this seems an unnecessary restriction, because the
subscripts-mechanism which allows to access the original data should
also work if
2004 Dec 15
1
RE: Lattice update error (PR#7423)
OK. Sorry to have bothered you. It may well have been the namespace issue, a
subtlety that I would have been unaware of. Thanks. I've cc'ed this to
r-bugs in case there is anything they wish to do about it.
-- Bert Gunter
> -----Original Message-----
> From: Deepayan Sarkar [mailto:deepayan@stat.wisc.edu]
> Sent: Wednesday, December 15, 2004 12:05 PM
> To: Berton Gunter
2001 Oct 23
1
Rows function in nlme package
The Rows function which is called from plot.compareFits in the nlme package
is not found.
> plot(compareFits(coef(bp.model3),coef(bp.model3M)))
Error in plot.compareFits(compareFits(coef(bp.model3), coef(bp.model3M))) :
couldn't find function "Rows"
>
Can I find it elswhere? Have I missed a required package?
Thanks
Ross Darnell
> library(help=nlme)
nlme
2008 May 27
1
Fwd: Re: Seeking help with trellis: log scales on xyplot
Deepayan:
Sorry for the additional email, but I'm concerned that I wasn't being clear.
In the end, I would like a graphic that portrays my y-values on a log scale in their native data range. That is to say, I would prefer to see the axis labels as 1000 rather than 3 (log10 of 1000).
Thank you for your kind assistance,
Hobie Perry
St. Paul, MN
Hobie Perry <hobie_perry@yahoo.com>
2004 Aug 10
1
date axes and formats in levelplot
Hi all (and particularly Deepayan),
A while back Deepayan helped me with the query in the text below (thanks
again). Specifically it was about changing the way that dates plotted on
the axes of lattice plots.
While this works using xyplot, everything comes apart when I use
levelplot. The axis labels on the date axis are shown as the integer
representation of the date (number of seconds since
2019 Dec 06
1
inappropriate warning in latticeExtra
This problem is still present in
> version
_
platform x86_64-w64-mingw32
arch x86_64
os mingw32
system x86_64, mingw32
status Under development (unstable)
major 4
minor 0.0
year 2019
month 12
day 03
svn rev 77513
language R
version.string R Under development (unstable)
2023 Apr 04
1
on lexical scoping....
Dear Duncan,
THanks for the reply...!
So the takeaway is that define the symbol in the same environment before using it right!?
Thanking you,
Yours sincerely,
AKSHAY M KULKARNI
________________________________
From: Duncan Murdoch <murdoch.duncan at gmail.com>
Sent: Tuesday, April 4, 2023 8:21 PM
To: akshay kulkarni <akshay_e4 at hotmail.com>; Deepayan Sarkar
2023 Apr 04
1
on lexical scoping....
No, there are lots of situations where that doesn't make sense. You
don't want to have to define local copies of the functions from every
package you use, for example.
I think the takeaway is to learn how R scoping works, and keep things
simple. That's one reason I tend to avoid "tidyverse" packages. There
are a lot of really good ideas in those packages, but
2012 Nov 22
2
BibTeX entries in CITATION file
Dear List,
While trying to define a customised CITATION file for a package,
following R-exts, I realised that if I use only one 'citEntry' I got
both a text description and a BibTex entry for the package, as for the
'nlme' package:
--------------------------
citation('nlme')
To cite package 'nlme' in publications use:
Jose Pinheiro, Douglas Bates, Saikat
2023 Nov 14
1
data.frame weirdness
In that case identical should be FALSE but it is TRUE
identical(a1, a2)
## [1] TRUE
On Tue, Nov 14, 2023 at 8:58?AM Deepayan Sarkar
<deepayan.sarkar at gmail.com> wrote:
>
> They differ in whether the row names are "automatic":
>
> > .row_names_info(a1)
> [1] -3
> > .row_names_info(a2)
> [1] 3
>
> Best,
> -Deepayan
>
> On Tue, 14 Nov
2004 Apr 30
0
Deepayan Sarkar wins the 2004 Chambers Award
It was announced today that Deepayan Sarkar has won the 2004 Chambers
Award sponsored by the Statistical Computing section of the American
Statistical Association. This award, made possible by a generous
donation by Dr. John M. Chambers, is given annually in recognition
of outstanding contributions to statistical software by a student.
Deepayan received the award for his lattice package for R.
2004 Apr 30
0
Deepayan Sarkar wins the 2004 Chambers Award
It was announced today that Deepayan Sarkar has won the 2004 Chambers
Award sponsored by the Statistical Computing section of the American
Statistical Association. This award, made possible by a generous
donation by Dr. John M. Chambers, is given annually in recognition
of outstanding contributions to statistical software by a student.
Deepayan received the award for his lattice package for R.
2010 Apr 23
1
help in conditional histogram
Dear Dr. Sarkar,
When I try to run the codes, I found the following problem:
> h<- sample(1:14, 319, rep=T)
> c<- sample(1:14, 608, rep=T)
> n<- sample(1:14, 1140, rep=T)
> vt<-c(h, c, n)
> ta<-rep(c("h", "c", "n"), c(319, 608, 1140))
>
> to<-data.frame(vt,ta)
> library(lattice)
Attaching package: 'lattice'
2023 Nov 14
1
data.frame weirdness
On Tue, 14 Nov 2023 at 09:41, Gabor Grothendieck
<ggrothendieck at gmail.com> wrote:
>
> Also why should that difference result in different behavior?
That's justifiable, I think; consider:
> d1 = data.frame(a = 1:4)
> d2 = d3 = data.frame(b = 1:2)
> row.names(d3) = c("a", "b")
> data.frame(d1, d2)
a b
1 1 1
2 2 2
3 3 1
4 4 2
> data.frame(d1,