Displaying 20 results from an estimated 1000 matches similar to: "Hist and extra space"
2005 Sep 01
1
Spacing and margins in lattice...
Similar to my last question, I want to tighten up the spacing and
margins in a plot I am doing with lattice.
Here are the commands I'm using:
data <- data.frame(x=c(1:3, 1:3), y=c(1:3, 1:3*2),
cat=c("foo","foo","foo","bar", "bar","bar"))
xyplot(panel=panel.superpose, y~x, data=data, groups=cat, type="b",
2005 Dec 11
1
(PR#8376 inconsistency between plot(hist(...)) and hist(...)
On Sun, 11 Dec 2005 clausen at econ.upenn.edu wrote:
> Full_Name: Andrew Clausen
> Version: 2.1.0
> OS: Debian GNU/Linux
> Submission from: (NULL) (71.242.192.73)
>
>
> Hi,
>
> When I type
>
> hist(x, freq=F)
>
> I get a density function, as I expect. However, if I type
>
> plot(hist(x, freq=F))
>
> then I get the same output as if I had
2000 Jul 12
1
plot.times error -- missing or illegal tck parameter (PR#601)
There seems no default setting for tck, causing problems
for plot.times()
> library(chron)
> dts <- dates(c("02/27/92", "02/27/92", "01/14/92",
+ "02/28/92", "02/01/92"))
> y<-chron(dts,out.format=c("dmy","h:m:s"))
> y
[1] 270292 270292 140192 280292 010292
> plot(y,1:5)
Error in axis(n, at =
2013 Jul 26
0
[LLVMdev] floor
Here is a test case:
extern double floor(double);
extern double floor_(double);
double x = 1.5;
double y, y_;
void foo() {
double y = floor(x);
double y_ = floor_(x);
}
If I compile this for Mips16, it calls the proper helper function for
floor_ but not for floor, because the signature for floor in callee info
is wrong. Args[0] = void RetTy = void
2013 Jul 26
2
[LLVMdev] floor
I'm getting some problems because it seems that the compiler is treating
"floor" differently from other math library functions like "sin".
The Args and RetVal have the parameter and return types marked as void.
For mips16, it's important that I be able to know the original signature
for floating point functions.
In some cases, need to create calls to helper
2013 Feb 20
3
[LLVMdev] Is va_arg correct on Mips backend?
I didn't have Mips board. I compile as the commands and check the asm output as below.
1. Question:
The distance of caller arg[4] and arg[5] is 4 bytes. But the the callee get every
arg[] by 8 bytes offset (arg_ptr1+8 or arg_ptr2+8). I assume the #BB#4 and #BB#5 are the arg_ptr which is the pointer to access the stack arguments.
2. Question:
Stack memory 28($sp) has no initial value. If
2013 Feb 20
0
[LLVMdev] Is va_arg correct on Mips backend?
Does it make a difference if you give the "-target" option to clang?
$ clang -target mips-linux-gnu ch8_3.cpp -o ch8_3.bc -emit-llvm -c
The .s file generated this way looks quite different from the one in your
email.
On Tue, Feb 19, 2013 at 5:06 PM, Jonathan <gamma_chen at yahoo.com.tw> wrote:
> I didn't have Mips board. I compile as the commands and check the asm
>
2018 Feb 06
2
Re: [libvirt] [PATCH tck] Relabel SELinux when customizing virt-builder image
On 02/06/2018 10:53 AM, Pino Toscano wrote:
> On Tuesday, 6 February 2018 16:40:04 CET Daniel P. Berrangé wrote:
>> When you tell virt-builder to install extra RPMs, this potentially
>> looses the SELinux labelling that Anaconda had originally setup. Thus we
>> must tell virt-builder to enable SELinux relabelling.
>>
>> Signed-off-by: Daniel P. Berrangé
2014 Aug 31
1
System ACL and Samba ACL
My destination is :/Example(folder) / ITD(folder) / LW(folder) ,user(lw) of group(ITD) can enter and do everything(rwx) in LW(folder),the following is ACL settings On Freebsd:
-----------------------
/Example(folder) :
# owner: root
# group: wheel
user::rwx
group::r-x
other::r-x
---------------------
/Example(folder) / ITD(folder):
# owner: root
# group: wheel
user::rwx
group::r-x
group:ITD:r-x
2010 May 26
1
persp(); help with 'tck' option
Hi All,
I'm using 'tck' option to *reduce* the length of tick marks but it is not
working, can anyone please tell me where I'm going wrong...
require(graphics)
require(grDevices)
x <- seq(-10, 10, length= 30)
y <- x
f <- function(x,y) { r <- sqrt(x^2+y^2); 10 * sin(r)/r }
z <- outer(x, y, f)
z[is.na(z)] <- 1
# 'bg' works but 'tck' is not showing
2007 Jul 12
1
[LLVMdev] backend problem with LiveInterval::removeRange
Hi all,
When compiling some programs using the Mips backend
i'm getting this assert message on lib/CodeGen/LiveInterval.cpp:227:
"Range is not entirely in interval!"
I don't know yet if it's something that is missing on the backend code or
why
the range to be removed it outside the interval, does anyone have any clue?
A more detailed output is attached.
The program i tried
2009 Dec 11
3
`mgp[1:3]' are of differing sign (PR#14130)
Full_Name: Cornell Gonschior
Version: 2.10.0
OS: Linux
Submission from: (NULL) (212.201.28.40)
Hi,
in the introduction to R, you can find the following sentence in the par()
chapter:
"Use tck=0.01 and mgp=c(1,-1.5,0) for internal tick marks."
I thought that's nice, because I wanted to have tick marks and tick labels
inside and the axis title outside.
But:
> plot(z, las=1,
2007 Jan 23
1
How to generate 'minor' ticks in lattice (qqmath)
Dear group,
I tried to generate labels for every second tick in lattice (qqmath).
Version: 0.14-16
Date: 2006/12/01
R version 2.4.1 (2006-12-18)
An example:
library(lattice)
numy=100
y=runif(numy,min=0,max=1)
sig=0.05
numsig=length(which(y<sig))
tck.no=11 # number of ticks
tcks=1:tck.no
labl=as.character(0.1*tcks-0.1) # label for all ticks
labl[seq(2,tck.no-1,2)]="" # delete
2008 May 14
1
lw in legend also changes thickness of characters in the legend??
Here's a simple example:
x <- 1:5
plot(x,x^2)
lines(x,x^2)
points(x,x,cex=2)
lines(x,x,lw=3)
legend("topleft",legend=c("y=x^2","y=x"),pch=1,pt.cex=1:2,lw=c(1,3))
The thickness of the circles in the legend changes with lw. If you change
the lw argument in legend to lw=c(1,1) then the thickness of the circles
goes back to normal. How can I make the above
2018 Feb 07
0
Re: [libvirt] [PATCH tck] Relabel SELinux when customizing virt-builder image
On Tue, Feb 06, 2018 at 12:50:51PM -0500, Laine Stump wrote:
> On 02/06/2018 10:53 AM, Pino Toscano wrote:
> > On Tuesday, 6 February 2018 16:40:04 CET Daniel P. Berrangé wrote:
> >> When you tell virt-builder to install extra RPMs, this potentially
> >> looses the SELinux labelling that Anaconda had originally setup. Thus we
> >> must tell virt-builder to
1998 Jan 08
0
R-beta: Using par(tck=,xaxs=)
I found that par(tck=xx) was ignored and par(xaxs="s") gave an error in
v0.61. I've made the following quick hacks in the code to get these to
function. Please let me know if I'm setting myself up for trouble and...
Thanks for R! ...Steve Oncley (oncley at ucar.edu)
-------------------------------------------------------
A hack to get par(tck) to work:
2003 Mar 17
1
postscript and ps.option metrics
Good Afternoon All,
I am working on a project to generate a particular celeration graph that requires a very specific height and width in the format of the postscript output.
I have attempted to specify my height and width parameters in inches as I found in the R help documentation, but this produces a graph much smaller than what it should if the standard metric is indeed inches.
Since inches
2013 Feb 27
2
[LLVMdev] Mips backend 3.2 va_arg possible bug
i have this code
typedef long long L;
typedef integer I;
void test2(auto L p0, auto L p1, auto L p2, auto L p4, ...)
{
va_list select;
va_start (select, p4);
report( va_arg(select,L) );
report( va_arg(select,I) );
report( va_arg(select,L) );
2013 Feb 19
0
[LLVMdev] Is va_arg correct on Mips backend?
Which part of the generated code do you think is not correct? Could you be
more specific?
I compiled this program with clang and ran it on a mips board. It returns
the expected result (21).
On Tue, Feb 19, 2013 at 4:15 AM, Jonathan <gamma_chen at yahoo.com.tw> wrote:
> I check the Mips backend for the following C code fragment compile result.
> It seems not correct. Is it my
1998 Feb 04
1
R-beta: Functionality of tck=1, and mtext()
In the version of R that I am running I have found two advertised
features that don't appear to work correctly:
Version 0.61.0 Alpha (December 21, 1997)
(installed using r-base-0.61.0-2.i386.rpm)
1. mtext adj parameter is seriously offset to the right. For example:
> par(oma=c(0,0,3,0))
> mtext("Try this", side=3, outer=T) # nothing is observed on x11
> mtext("Now