search for: pad2

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 179787 574729.2 179674...

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]]

...g 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(...) {...

...ls = 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 = function(x,...

...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 Bihorel, PharmD, PhD* PKPD Scientist Cognigen Corp Ema...

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:

...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.theme) } df <- data.frame(x=-10:10,y=rnorm(21)) myp...

...ellis 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~mdep, data=m1, scales=list( x=lis...

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, Hong Hu <huhong789 at gmail.com> wrote: &...

...llvm.org> wrote: > 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:4...

As it turns out, with the proprietary firmware, the VP3 and VP4 interfaces are identical. Furthermore, this is all already implemented for nvc0. So these patches (a) move the easily sharable bits of the nvc0 implementation into the nouveau directory, and then (b) implement the other parts in nv50. The non-shared parts are still largely copies, but there are some differences, not the least of which

...8 Reserved2: 0 Parameter Count: 10 Parameter Offset: 56 Parameter Displacement: 0 Data Count: 108 Data Offset: 68 Data Displacement: 0 Setup Count: 0 Reserved3: 0 Byte Count (BCC): 121 Pad1: \000 Parameter: \000\001\001\000\001\000\000\000\000\000 Pad2: \000\000 Data: l\000\000\000\000\000\000\000\2003???p?\001\200t5\222\000q?\001\000@???p?\00 1\000@???p?\001?F\000\000\000\000\000\000?F\000\000\000\000\000\000 \000\000\000\f\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\0 00\000\000\00

Hi, I would like to combine multiple xyplots into a single, multipanel display. Using R 3.0.1 in Ubuntu, I have used c() from latticeExtra to combine three plots, but the x-axis for two plots are on a log scale and the other is on a normal scale. I also have included equispace.log=FALSE to clean up the tick labels. However, when I try all of these, the x-axis scale of the first panel is used

Thanks, Eli. Next question is how to get the layout of the original C++ class from LLVM IR? Regards, Hu Hong On 29 December 2016 at 01:57, Friedman, Eli <efriedma at codeaurora.org> wrote: > On 12/28/2016 5:41 AM, Hong Hu via llvm-dev wrote: > > Hi all, > > I'm writing a pass to understand the memory access to C++ class members. > For each GetElementPtr instruction,

https://bugs.freedesktop.org/show_bug.cgi?id=106994 Bug ID: 106994 Summary: [PATCH] Fix null pointer dereference in drmmode_output_dpms Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component:

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

Hi, This is a proof of concept of GPU forwarding for Linux guest on Linux host. I'd like to get comments and suggestions from community before I put more time on it. To summarize what it is: 1. It's a solution to bring GPU acceleration for Linux vm guest on Linux host. It could works with different GPU although the current proof of concept only works with Intel GPU. 2. The basic idea

..._init_qp_minus26; // 8c + uint32_t chroma_qp_index_offset; // 90 + uint32_t deblocking_filter_control_present_flag; // 94 + uint32_t constrained_intra_pred_flag; // 98 + uint32_t redundant_pic_cnt_present_flag; // 9c + uint32_t transform_8x8_mode_flag; // a0 + uint32_t pad2[(0x1c8 - 0xa0 - 4) / 4]; + uint32_t second_chroma_qp_index_offset; // 1c8 + uint32_t u1cc; // 1cc + uint32_t curr_pic_order_cnt; // 1d0 + uint32_t field_order_cnt[2]; // 1d4 + uint32_t curr_mvidx; // 1dc + struct iref { + uint32_t u00; // 00 + uint32_t...

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some