Displaying 9 results from an estimated 9 matches for "p_3".
Did you mean:
p3
2009 Aug 04
3
Accuracy (PR#13867)
...p_1=c(0.2,0.2,0.2,0.2,0.1,0.25,0.4,0.1,0.25,0.4,0.1,0.25,0.4,0.1,0.25,0.4,0.2,0.5,0.8,0.2,0.5,0.8,0.2,0.5,0.8,0.2,0.5,0.8)
p_2=c(0,0,0,0,0.5,0.5,0.5,0.5,0.5,0.5,0.5,0.5,0.5,0.5,0.5,0.5,0.4,0.25,0.1,0.4,0.25,0.1,0.4,0.25,0.1,0.4,0.25,0.1)
As these are probabilities, I calculated the remainder as
p_3=1-p_1-p_2
There the values which ought to be 0.1 were lateron not recognised by p_3==0.1,
but only if I used p_3 <= 0.1.
The full calculation is actually bigger but the core issue remains: I used
values input by hand, built a difference and it was wrong.
I know that exactly the value 0.1 is o...
2008 Aug 19
1
Polynomial regression help
I have a simple X, Y data frame that I am trying to run regression analysis
on. The linear regression looks great, but when I use lm(formula = y ~
poly(x, degree = 5)) I get the same coeffecients. So for example if I use
degree =3 my formula would look like y = 4.2 x^3 + 3.2x^2 + 2.1x + 1.0 and
my degree 5 would look like y = 6.5x^5+ 5.4x^4 + 4.2 x^3 + 3.2x^2 + 2.1x +
1.0, which doesn't make
2011 Aug 10
0
[LLVMdev] Handling of pointer difference in llvm-gcc and clang
...value.
>
> Is this a bug in llvm-gcc?
in llvm-gcc (and dragonegg) this is coming directly from GCC's gimple:
f (int * p, int * q)
{
long int D.2718;
long int D.2717;
long int p.1;
long int q.0;
int D.2714;
<bb 2>:
q.0_2 = (long int) q_1(D);
p.1_4 = (long int) p_3(D);
D.2717_5 = q.0_2 - p.1_4;
D.2718_6 = D.2717_5 /[ex] 4;
D.2714_7 = (int) D.2718_6;
return D.2714_7;
}
Signed overflow in the difference of two long int (ptrdiff_t) values results in
undefined behaviour according to the GCC type system, which is where the nsw
flag comes from.
The C...
2011 Aug 10
3
[LLVMdev] Handling of pointer difference in llvm-gcc and clang
Hi,
We are developing a bounded model checker for C/C++ programs
(http://baldur.iti.kit.edu/llbmc/) that operates on LLVM's intermediate
representation. While checking a C++ program that uses STL containers
we noticed that llvm-gcc and clang handle pointer differences in
disagreeing ways.
Consider the following C function:
int f(int *p, int *q)
{
return q - p;
}
Here's the
2002 Dec 06
0
Non-R question.
...were the same as in the 2002 study, so probaby the
overdispersion were the same (at least assuming that is the best I can
do).
So assuming equal overdispersion I can get four confidence interval s
of "binomial" p's, but people will want an hypothesis test of the overall
null: p_1=p_2=p_3=p_4. Is there some way I can construct an hypothesis test
for that null, from the four confidence intervals?
Hoping this is enough information of the background, as the mail is
already to long!
Thanks,
Kjetil Halvorsen
2003 Mar 02
1
Final Ogg 1.0 submission to IETF
...--------------
> | packet_1 | packet_2 | packet_3 | <
-----------------------------------------------------------------
|segmentation (logically only)
v
packet_1 (5 segments) packet_2 (4 segs) p_3 (2 segs)
------------------------------ -------------------- ------------
.. |seg_1|seg_2|seg_3|seg_4|s_5 | |seg_1|seg_2|seg_3|| |seg_1|s_2 | ..
------------------------------ -------------------- ------------
| page encapsulation
v...
2003 Mar 02
1
Final Ogg 1.0 submission to IETF
...--------------
> | packet_1 | packet_2 | packet_3 | <
-----------------------------------------------------------------
|segmentation (logically only)
v
packet_1 (5 segments) packet_2 (4 segs) p_3 (2 segs)
------------------------------ -------------------- ------------
.. |seg_1|seg_2|seg_3|seg_4|s_5 | |seg_1|seg_2|seg_3|| |seg_1|s_2 | ..
------------------------------ -------------------- ------------
| page encapsulation
v...
2003 Feb 13
2
Changes to Ogg format IETF I-D
...--------------
> | packet_1 | packet_2 | packet_3 | <
-----------------------------------------------------------------
|segmentation (logically only)
v
packet_1 (5 segments) packet_2 (4 segs) p_3 (2 segs)
------------------------------ -------------------- ------------
.. |seg_1|seg_2|seg_3|seg_4|s_5 | |seg_1|seg_2|seg_3|| |seg_1|s_2 | ..
------------------------------ -------------------- ------------
| page encapsulation
v...
2003 Feb 13
2
Changes to Ogg format IETF I-D
...--------------
> | packet_1 | packet_2 | packet_3 | <
-----------------------------------------------------------------
|segmentation (logically only)
v
packet_1 (5 segments) packet_2 (4 segs) p_3 (2 segs)
------------------------------ -------------------- ------------
.. |seg_1|seg_2|seg_3|seg_4|s_5 | |seg_1|seg_2|seg_3|| |seg_1|s_2 | ..
------------------------------ -------------------- ------------
| page encapsulation
v...