On Mon, Jun 20, 2011 at 9:22 PM, David Winsemius wrote:
>
> On Jun 20, 2011, at 10:49 AM, Bert Gunter wrote:
>
>> Hi all:
>>
>> Thanks, David. This is a good example of knowledgeable "R forensic
>> investigation." I leave it to Frank whether it meets his criteria.
>>
>> However, I would argue that
On Jun 20, 2011, at 10:49 AM, Bert Gunter wrote:
Hi all:
Thanks, David. This is a good example of knowledgeable "R forensic
investigation." I leave it to Frank whether it meets his criteria.
However, I would argue that that this is bad practice and quite
unwise. In general, these details are
Thanks very much Bert and David. I was looking for an approach that would
use objects that are active while the panel function was being executed.
Perhaps which.packet is the best way to go, e.g. if using y ~ x | a*b, fetch
levels(b)[which.packet()[2]] from the environment in which b is defined.
Hi all:
Thanks, David. This is a good example of knowledgeable "R forensic
investigation." I leave it to Frank whether it meets his criteria.
However, I would argue that that this is bad practice and quite
unwise. In general, these details are implementation dependent and
could change. Yes, they
Frank Harrell wrote:
>
> I know about the current.row, current.column, and panel.number functions
> that are useful within panel functions written for lattice. Are there
> easy ways to obtain the names of the conditioning variables (those
> appearing after |) and their values for the current pan
I know about the current.row, current.column, and panel.number functions that
are useful within panel functions written for lattice. Are there easy ways
to obtain the names of the conditioning variables (those appearing after |)
and their values for the current panel?
Thanks
Frank
-
Frank Har
6 matches
Mail list logo