Displaying 7 results from an estimated 7 matches for "l530".
Did you mean:
0530
2020 Mar 26
4
unstable corner of parameter space for qbeta?
...e-force uniroot() version, see below
Qbeta0(t,shape1,shape2) ## 0.9262824
The qbeta code is pretty scary to read: the warning "full precision
may not have been achieved" is triggered here:
https://github.com/wch/r-source/blob/f8d4d7d48051860cc695b99db9be9cf439aee743/src/nmath/qbeta.c#L530
Any thoughts? Should I report this on the bug list?
A more general illustration:
http://www.math.mcmaster.ca/bolker/misc/qbeta.png
===
fun <- function(phi,i=0.01,t=0.001, f=qbeta) {
f(t,shape1=i/phi,shape2=(1-i)/phi, lower.tail=FALSE)
}
## brute-force beta quantile function
Qbeta0 <-...
2020 Mar 26
0
unstable corner of parameter space for qbeta?
...ow
> Qbeta0(t,shape1,shape2) ## 0.9262824
> The qbeta code is pretty scary to read: the warning "full precision
> may not have been achieved" is triggered here:
> https://github.com/wch/r-source/blob/f8d4d7d48051860cc695b99db9be9cf439aee743/src/nmath/qbeta.c#L530
> Any thoughts?
Well, qbeta() is mostly based on inverting pbeta() and pbeta()
has *several* "dangerous" corners in its parameter spaces
{in some cases, it makes sense to look at the 4 different cases
log.p = TRUE/FALSE // lower.tail = TRUE/FALSE separately ..}
pbeta() its...
2020 Mar 26
2
unstable corner of parameter space for qbeta?
...e1,shape2) ## 0.9262824
>
> > The qbeta code is pretty scary to read: the warning "full precision
> > may not have been achieved" is triggered here:
>
> > https://github.com/wch/r-source/blob/f8d4d7d48051860cc695b99db9be9cf439aee743/src/nmath/qbeta.c#L530
>
> > Any thoughts?
>
> Well, qbeta() is mostly based on inverting pbeta() and pbeta()
> has *several* "dangerous" corners in its parameter spaces
> {in some cases, it makes sense to look at the 4 different cases
> log.p = TRUE/FALSE // lower.tail = TRUE...
2017 Sep 18
1
Do I need to modify the AddrLoc of LLD for ARC target?
...t;>>> the output of the linker map file to see where it placed the Output
>>>> and Input Sections to see what the answer should be.
>>>
>>> LLD's getOutputSection()->Addr =
>>> https://github.com/llvm-mirror/lld/blob/master/ELF/LinkerScript.cpp#L530
>>>
>>>
>>>
>>>> In summary:
>>>> It looks like there are some Arc specific things that might need to be
>>>> done. Unfortunately I don't have any experience with Arc, and I'm not
>>>> sure the other people that work...
2017 Sep 19
1
Do I need to modify the AddrLoc of LLD for ARC target?
...ee where it placed the Output
>>>>>> and Input Sections to see what the answer should be.
>>>>>
>>>>> LLD's getOutputSection()->Addr =
>>>>>
>>>>> https://github.com/llvm-mirror/lld/blob/master/ELF/LinkerScript.cpp#L530
>>>>>
>>>>>
>>>>>
>>>>>> In summary:
>>>>>> It looks like there are some Arc specific things that might need to be
>>>>>> done. Unfortunately I don't have any experience with Arc, and I'm not...
2017 Sep 14
4
Do I need to modify the AddrLoc of LLD for ARC target?
Hello Leslie,
I think we are going to need to know a bit more about the ELF ABI for
what looks like the ArcCompact before we can help you.
LLD's calculation of P (the place to be relocated) is as it is in the
generic ELF specification. The Rel.Offset corresponds to the ELF
r_offset field. This is covered by: "For a relocatable file, the value
is the byte offset from the beginning of the
2019 May 10
11
[nbdkit PATCH 0/9] RFC: implement NBD_CMD_CACHE
I'm still working my way through the filters before this series will
be complete, but this is enough of a start to at least get some
feedback on the idea of implementing another NBD protocol extension.
Eric Blake (9):
server: Internal hooks for implementing NBD_CMD_CACHE
plugins: Add .cache callback
file, split: Implement .cache with posix_fadvise
nbd: Implement NBD_CMD_CACHE