Hi Mark
Thats why I did all the examples in Sweave to pick up anything I
could not understand in practice but it did not help very much
It also gave me a quick reference as they are all bookmarked and are annotated
Duncan
At 00:01 22/04/2012, you wrote:
>Hi Duncan: Don't feel bad about it. I've
Hi Bert
Thank you for your comments.
I do use latticeExtra a lot - about 50% of my graphs at the moment
have useOuterStrips some involving combineLimits .
Many are complicated - one I have just finished involves
useOuterStrips in 8,3 (r,c) panels after
http://finzi.psych.upenn.edu/R/Rhelp02/a
Bert
I have read Deepayan's book and done all the examples but there is no
mention of panel.number and panel.groups in the books example.
I just cannot get the fully meaning of what has been written
regarding passing arguments to panel functions.
Regards
Duncan
At 14:31 21/04/2012, you w
A comment...
On Fri, Apr 20, 2012 at 8:32 PM, Duncan Mackay wrote:
> Hi David, ilai
>
> The root cause of the problem is the passing of arguments to panel functions
> to me and my colleagues.
> Just going through the archives there seems to be different ways for very
> similar/same outcomes and
>
On Fri, Apr 20, 2012 at 8:15 PM, David Winsemius wrote:
>
> Another puzzle. In the original posting there was this segment:
> ---
>
> but gives an error message without par.settings if i want to add
> panel.Locfit(x,y,nn= 0.9,lwd = c(1,2,3), ...)
>
> Error using packet 1
> fo
Hi David, ilai
The root cause of the problem is the passing of arguments to panel
functions to me and my colleagues.
Just going through the archives there seems to be different ways for
very similar/same outcomes and
trying to get a pattern is hard to discern.
I frequently have to use the subs
Hi David
if you go
library(locfit)
? panel.locfit
The function will do contour/wireframe like plots using par.settings
of region as well as normal 2D plots
I could not get panel.locfit to work using par.settings and created
my own panel function as panel.Locfit
at the time I did not think th
On Apr 20, 2012, at 9:14 PM, ilai wrote:
Oops - that is "reply all"
On Fri, Apr 20, 2012 at 5:29 PM, David Winsemius > wrote:
I'm a bit puzzled by this exchange. I know there is a
'panel.locfit', but
you two are spelling it differently. Can you explain why you are
doing so?
Hi David,
Oops - that is "reply all"
On Fri, Apr 20, 2012 at 5:29 PM, David Winsemius wrote:
>
> I'm a bit puzzled by this exchange. I know there is a 'panel.locfit', but
> you two are spelling it differently. Can you explain why you are doing so?
>
Hi David,
Thanks for stepping in. panel.Locfit is the OP'
On Apr 20, 2012, at 6:36 PM, Duncan Mackay wrote:
Hi ilai
Thank you for your advice I think I can now get what I need from
what you have said here.
I think I may have to get involved in packet.number but the original
packet.number with its arguments has stuck in my mind and I have not
us
Hi ilai
Thank you for your advice I think I can now get what I need from what
you have said here.
I think I may have to get involved in packet.number but the original
packet.number with its arguments has stuck in my mind and I have not used it.
I find locfit better than loess etc for a lot of
Duncan,
First off, I admit it is not clear to me what you are trying to
achieve and more importantly, why? by "why" I mean 1) I don't see the
advantage of writing one general panel function for completely
different situations (one/multiple smoothers, grouping levels etc.) 2)
your intended result as
Hi ilai
Thank you for your suggestions.
I do not know what happened yesterday I must have omitted a few
changes out in going from R to email
and apologies for the double posting - I had troubles sending it as
my ISP gave a message of not being connected for email but was for the web
I was t
On Thu, Apr 19, 2012 at 2:30 AM, Duncan Mackay wrote:
> Hi
>
> xyplot(y ~x|Farm,xx,
> groups = Padd,
> panel = panel.superpose,
> panel.groups=function(x,y, ...){
> panel.Locfit(x,y,...)
> panel.xyplot(x,y,...)
>
14 matches
Mail list logo
