search for: pad1

...If i read the config files correctly, dovecot seems to have no equivalent of courier's IMAP_EMPTYTRASH=Trash:7 setting. Therefore, i wrote a script that dives into the user's directories and their maildirs. It looks like this: ============================================= #!/bin/bash for pad1 in $(ls /home) do if [ -e "/home/$pad1/Maildir/.Prullenbak" ] then find "/home/$pad1/Maildir/.Prullenbak/cur" -mtime +2 -type f -delete find "/home/$pad1/Maildir/.Prullenbak/new" -mtime +2 -type f -delete fi if [ -e "/home/$pad1/Maildir/.Allerlei...

Hi all: I've been trying to figure out a way to move the tick mark labels in my lattice plots closer to the the axes. I've tinkered with a lot of the "buffer" parameters (those listed by trellis.par.get()), but haven't had any luck. Any ideas? Cheers. [[alternative HTML version deleted]]

...tck setting in the lattice package as the ticks on left sided axis aren't drawn at all with the following setting: dados <- data.frame(varsep = factor(rep(1:2,10)), i = runif(20)) library(lattice) my.theme <- list( axis.components = list(left = list(tck = 1, pad1 = 1, pad2 = 2), top = list(tck = 0, pad1 = 1, pad2 = 0), right = list(tck = 0, pad1 = 1, pad2 = 0), bottom = list(tck = +0.5, pad1 = 1, pad2 = 2))) trellis.par.set(theme = my.theme) bwplot(varsep ~ i, dados, xlab = names(dados)[1], ylab = names(dados)[2], panel = function(.....

...Year, levels = c("1999","2000","2001","2002","2003","2004","2005","2006","2007","2008") , ordered = TRUE) library(lattice) my.theme <- list( axis.components = list(left = list(tck = 0.5, pad1 = 1, pad2 = 2), top = list(tck = 0, pad1 = -1.3, pad2 = 0), right = list(tck = 0.5, pad1 = 1, pad2 = 2), bottom = list(tck = +0.5, pad1 = 1, pad2 = 2))) trellis.par.set(theme = my.theme) panel1 = fu...

...rectory #### > > > my.directory <- "C:/Users/Masoud/Desktop/r/" > #my.directory <- "C:/Documents and Settings/laurent/My > Documents/Bioinfo_workshop/" > setwd("C:/Users/Masoud/Desktop/r/") > > #### Read data #### > > > > PAD1 <- read.delim("C:/Users/Masoud/Desktop/r/PAD.txt", header=TRUE) > > attach(PAD1) > > head(PAD1) Code PAD Age High_ratio Smoke DM1_2 HT HxVasc PI_NonPI n 1 EE-001 0 46 0 1 0 0 0 1 1 2 SK-002 0 56 1 0 0 1 1...

Good morning! I have the following data frame (df): X.outer Y.outer X.PAD1 Y.PAD1 X.PAD2 Y.PAD2 X.PAD3 Y.PAD3 X.PAD4 Y.PAD4 73 574690.0 179740.0 574690.2 179740.0 574618.3 179650 574729.2 179674 574747.1 179598 74 574680.6 179737.0 574693.4 179740.0 574719.0 179688 574831.8 179699 574724.9 179673 75 574671.0 179734.0 574696.2 179740.0 574719.0 179688 574807.8 1797...

...tion (http://r.789695.n4.nabble.com/Lattice-distance-of-tick-labels-from-axis-line-tp3693014p3693014.html). This works for xyplot, but *not* for wireframe: xyplot(z ~ x, df, scales = list(arrows = FALSE, col = "black", font = 1, tck=0.6), par.settings=list(axis.components=list(left=list(pad1=2)))) wireframe(z ~ x*y, df, scales = list(arrows = FALSE, col = "black", font = 1, tck=0.6), par.settings=list(axis.components=list(left=list(pad1=2)))) Any ideas on how to pad the axis labels in wireframe plots? Thanks, Felix

Hi, I am doing fine editing on a lattice plot, now have the Y-axis title in the correct position, but the tick labels are too far from the axis line. I looked at the help documentation but could not find how to change this. This seems to be easy to do in basic plots with "at=c(value1, value2, value3)" . Is there some equivalent in lattice? Thanks. -- View this message in context:

...main.key.padding =1, axis.xlab.padding=1, key.sub.padding =1, bottom.padding =1), axis.components=list(top=list(tck=1, pad1=1, pad2=1), right=list(tck=1, pad1=1, pad2=1))) print(plot1) dev.off() ########################### -- *Sebastien...

...padding = 0, ylab.axis.padding = 0, axis.key.padding = 0, units="mm"), layout.heights=list(bottom.padding=b, top.padding=t, main.key.padding = 0, key.axis.padding = 0, axis.xlab.padding = 0, xlab.key.padding = 0, key.sub.padding = 0, units="mm"), axis.components=list(bottom=list(pad1=.8), left=list(pad1=.8))); But still, the resulting margins are larger than I expect and to achieve the desired effect I have to set some parameters to negative numbers. So I guess there are some other graphical parameters that come into play, about which I do not know. Which margins are these *....

...ll the function (@cc_invoke) that throws a “core::CatchThrow” > exception like this: > > call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) > ;; Comment out the next two lines and > ; to label %return0 unwind label %landing-pad1 > ;return0: > ret void > > landing-pad1: ; No predecessors! > %6 = landingpad { i8*, i32 } personality i32 (...)* @__gxx_personality_v0 > cleanup > resume { i8*, i32 } %6 > } > > > It fails with: libc++abi.dylib: ter...

Hi Christian, Andy's already covered the major points, but you could consider filing a bug at http://llvm.org/bugs too, especially if you've got a small test-case that demonstrates the issue. Exception handling hasn't been a priority in the past, but as more people adopt LLVM's JIT APIs I suspect it will get more attention, and bug reports will help us figure out what needs doing.

Hello, I'm attempting to alter the location of text in my axis labels in lattice plots and have been unsuccessful so far. For example, the y-axis labels are always right-justified, but I would like them to be horizontally centered. Here's an example: library(lattice); # create fake dataset to plot to.plot <- data.frame( x = 1:5, y = c("1\nAAA", "2\nBBB",

..._invoke) that throws a “core::CatchThrow” >> exception like this: >> >> call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) >> ;; Comment out the next two lines and >> ; to label %return0 unwind label %landing-pad1 >> ;return0: >> ret void >> >> landing-pad1: ; No predecessors! >> %6 = landingpad { i8*, i32 } personality i32 (...)* @__gxx_personality_v0 >> cleanup >> resume { i8*, i32 } %6 >> } >> >>...

...@cc_invoke) that throws a “core::CatchThrow” exception like this: >>> call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) >>> ;; Comment out the next two lines and >>> ; to label %return0 unwind label %landing-pad1 >>> ;return0: >>> ret void >>> >>> landing-pad1: ; No predecessors! >>> %6 = landingpad { i8*, i32 } personality i32 (...)* @__gxx_personality_v0 >>> cleanup >>> resume { i8*, i32 } %6...

...a “core::CatchThrow” exception like this: >>>>> call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) >>>>> ;; Comment out the next two lines and >>>>> ; to label %return0 unwind label %landing-pad1 >>>>> ;return0: >>>>> ret void >>>>> >>>>> landing-pad1: ; No predecessors! >>>>> %6 = landingpad { i8*, i32 } personality i32 (...)* @__gxx_personality_v0 >>>>>...

...axis.xlab.padding=0, key.sub.padding =0, bottom.padding =0.5), axis.text=list(cex=1), axis.components=list(top=list(tck=0, pad1=0, pad2=0), right=list(tck=0, pad1=0, pad2=0))) inter.theme <- modifyList(cur.settings, theme) return(inter.the...

...chThrow” exception like this: >>>>>> call void @cc_invoke({ {}*, i64 }* %result-ptr, {}* %3, i64 2, {}* %4, {}* %5, {}* null, {}* null, {}* null) >>>>>> ;; Comment out the next two lines and >>>>>> ; to label %return0 unwind label %landing-pad1 >>>>>> ;return0: >>>>>> ret void >>>>>> >>>>>> landing-pad1: ; No predecessors! >>>>>> %6 = landingpad { i8*, i32 } personality i32 (...)* @__gxx_personality_v0 >>...

...t can be controlled by standard trellis graphics. I am able to set any parameters that are given in trellis.par.get() easily enough, for example: axis.components <- trellis.par.get("axis.components") axis.components$right$tck <- 0 axis.components$top$tck <- 0 axis.components$left$pad1 <- 2 axis.components$left$pad2 <- 2 trellis.par.set("axis.components", axis.components) but I have been unable to change other axis parameters such as setting the number of ticks on the bottom and left axes. I can do this in a conventional lattice plot such as xyplot xyplot(lar~mde...

Here is an example: I can define two classes: A and Apad: class A { bool b1, b2; double d1; int i1; }; class Apad { bool b1, b2; bool pad1[6]; double d1; int i1; bool pad2[4]; }; A and Apad will have the same layout, from the LLVM IR level: %class.A = type <{ i8, i8, [6 x i8], double, i32, [4 x i8] }> %class.Apad = type { i8, i8, [6 x i8], double, i32, [4 x i8] } Regards, Hu Hong On 29 December 2016 at 10:44, Hon...