similar to: evaluation in unattached namespace

Displaying 20 results from an estimated 3000 matches similar to: "evaluation in unattached namespace"

2008 Jun 16
2
Lattice: Superpose bwplot and dotplot [newbie question]
Hello everyone I have dataset containing a monetary value (ABS) and two factors (Fct, Group). I am able to create useful using: bwplot(ABS~Group|Fct) and dotplot(ABS~Group|Fct) Question: What do I have to do to overlay the dotplot with the bwplot (same data set)? I've found a couple of posts that hinted at the possibility of doing that, and checked the panel.superpose() help, but the info
2008 Jun 16
1
Lattice: Superpose bwplot on dotplot [Newbie Question]
Hello everyone I have dataset containing a monetary value (ABS) and two factors (Fct, Group). I am able to create useful using: bwplot(ABS~Group|Fct) and dotplot(ABS~Group|Fct) Question: What do I have to do to overlay the dotplot with the bwplot (same data set)? I've found a couple of posts that hinted at the possibility of doing that, and checked the panel.superpose() help, but the
2018 Jul 28
1
possible bug in plot.intervals.lmList
Dear R-devel members, I think I've found a minor bug in plot.intervals.lmList. ( The guide https://www.r-project.org/bugs.html suggests to report it here, as I do not have a bugzilla account.) Here is a minimal reproducible example to demonstrate the problem: fm1 <- lmList(distance ~ age | Subject, Orthodont) plot(intervals(fm1),ylab="a") This results in: "Error in
2008 May 06
2
Lattice problems / cannot load lattice
Hi, My problem is simple: since having updated the lattice package, I cannot load lattice anymore. If I type in the command 'library(lattice)' the loading fails with the following message: --- cut here --- Error in library.dynam(lib, package, package.lib) : shared library 'lattice' not found In addition: Warning messages: 1: In loadNamespace(package, c(which.lib.loc,
2006 Dec 08
1
lattice: defining an own function using args for "formula" and "groups"
x.fun <- function( formula, data ) dotplot( formula, data ) x.grp <- function( formula, groups, data ) dotplot( formula, groups, data ) data( barley ) > x.fun( variety ~ yield | site, data=barley ) # no problem > dotplot( variety ~ yield | site, groups=year, data=barley ) # no problem > x.grp( variety ~ yield | site, groups=year, data=barley ) object "year" not found
2010 Mar 24
2
Multi-panel Pie Charts.
Hi All, I'm trying to find out a way to plot multi-panel pie charts. It may not be the best way to present data, but I would still need one. 1. Is anyone aware of some in-built script/function which can do this for me. I'm aware of one given in Deepayan's book, but anything apart from this? 2. I tried using Deepayan's script on following data set but it doesn't seem to work
2004 Sep 09
2
Skipping panels in Lattice
Dear all, I wish to generate a lattice boxplot which skips an empty cell in a design. I have trawled r-help, scruitinized xyplot(lattice) help page, and merrily reproduced examples of using skip from a couple of previous r-help queries and the example given in Pinheiro & Bates. But I must be missing something... Here's an example (running R 1.9.1 on Win2k): # generate some data df1
2006 Jun 13
2
levelplot and source() problems
I have been using levelplot but have had trouble calling it inside functions - something seems to go wrong when it's not called directly from the R command prompt. Simplest reproducible example: $ R --vanilla > library(lattice) > levelplot(matrix(1:4,2,2)) - This gives a nice plot in soothing pastel colors. Now, with a file lptest.r containing 2 lines: library(lattice)
2007 Jul 10
1
Lattice: vertical barchart
barchart(Titanic, stack=F) produces a very nice horizontal barchart. Each panel has four groups of two bars. barchart(Titanic, stack=F, horizontal=F) doesn't produce the results I would have expected, as it produces this warning message: Warning message: y should be numeric in: bwplot.formula(x = as.formula(form), data = list(Class = c(1, And it results in each panel having 22 groups of
2010 Feb 26
1
bwplot() {lattice}
Hi All, I'm trying to plot boxplot graph. I tried barchart with "groups=" option and it worked fine. But when I try to generate same kind of graph using bwplot(), "groups=" option doesn't seem to work. Though this works, yield ~ variety | site * year I'm thinking why "groups=" doesn't work in this case, can anyone help please... #Code:
2004 Sep 17
2
lattice: bwplot and panel.lmline()
On Friday 17 September 2004 13:52, RenE J.V. Bertin wrote: > Hello again, > > I am doing regressions (using panel.lmline() (and panel.abline( > rlm(...))) ) inside a panel method which I pass to bwplot(). > > What I would like to do is create a boxplot of categorised data > (binned on the independent variable), and superpose a regression line > which is calculated using the
2002 Apr 18
2
Background in lattice plots using dotplot()
platform i586-pc-linux-gnu arch i586 os linux-gnu system i586, linux-gnu status major 1 minor 4.1 year 2002 month 01 day 30 language R I can't seem to get rid of the slightly green background when I use dotplot(). It shows on the screen in the
2006 Mar 01
2
lattice-Internal
Hi, The functions prepanel.default.bwplot() and lpretty() are not running in Deepayan's barley example concerning vertical bars with the lattice function barchart(). Why, is there a restricted use for the package lattice-Internal? Urs Simmen mailto:usimmen at dtc.ch
2007 Jun 08
1
still trying to wrap xyplot - ignore previous
As you may not be surprised to hear, no sooner did I post the previous message than I realized I had a really dumb mistake. I've now gotten a bit farther but am still stuck. New code: graph <- function (x, data, groups, xlab) { pg <- function(x, y, group.number, ...) fnord body(pg) <- substitute({ panel.xyplot(x, y, ..., group.number=group.number) panel.text(2,
2014 Feb 03
2
[LLVMdev] Weird msan problem
The code for ccall looks right. Sounds like you have a very small range of instructions where an uninitialized value appear. You could try debugging at asm level. Shadow for b should be passed at offset 0 in __msan_param_tls. MSan could propagate shadow through arithmetic and even some logic operations (like select). It could be that b is clean on function entry, but then something uninitialized
2017 Mar 31
2
How to write the same things as `opt` command in C++ API
Hi, I'm Ryo Ota. I'm using LLVM 3.8.1. I have a quesion about inlining function in C++ API. I'd like to inline some functions in a module in the same way as `opt -inline` command. But my C++ code didn't work what I want to do. For example, by using `opt -inline` command,`main.ll` is converted into the `inlined.ll`(`opt` command worked what I want to do) [main.ll (Not inlined)]
2014 Feb 05
2
[LLVMdev] Weird msan problem
Looks like when you materialize the stores, you should check the size of the the store and emit an appropriate amount of stores to the origin shadow (or just a memset intrinsic?). On Wed, Feb 5, 2014 at 2:13 PM, Keno Fischer <kfischer at college.harvard.edu>wrote: > The @entry stuff is just a gdb artifact. I've been tracking this back a > little further, and it seems there's
2005 Feb 01
2
How to write a new "top-level" Trellis/lattice function?
Hello, I am trying to write a new "top level" Trellis/lattice function. By "top-level", I mean a function like 'xyplot', 'histogram', 'bwplot', etc. These functions all call 'trellis.skeleton', which I am unable to call; an attempt to invoke the function that does so yields the error message: ----- Error in do.call("trellis.skeleton",
2014 Feb 07
2
[LLVMdev] Weird msan problem
Yes, it would be great to get that fixed. On Wed, Feb 5, 2014 at 4:09 PM, Evgeniy Stepanov <eugeni.stepanov at gmail.com>wrote: > On Thu, Feb 6, 2014 at 12:21 AM, Keno Fischer > <kfischer at college.harvard.edu> wrote: > > Looks like when you materialize the stores, you should check the size of > the > > the store and emit an appropriate amount of stores to the
2014 Feb 02
2
[LLVMdev] Weird msan problem
How is ccall() implemented? If it manually sets up a stack frame, then it also needs to store argument shadow values in paramtls. I don't think there is an overflow, unless you have a _lot_ of arguments in a function call. On Sun, Feb 2, 2014 at 9:26 AM, Keno Fischer <kfischer at college.harvard.edu> wrote: > Also, I was looking at the instrumented LLVM code and I noticed that the