search for: floored

...;ve pushed a simpler approach to the branch: > > https://github.com/ojwb/xapian/tree/orpositionlist > > Can you give that some real-world testing? It's not real real-world, but I built a contrived set of files on pairs of stemmed words (all 2-word combinations of floor/floors/floored/flooring), and the last commit of the branch works fine, finding all docs for recollish "floor floor"p, which yields a Xapian request of: ((floors OR flooring OR floored OR floor) NEAR 12 (floors OR flooring OR floored OR floor)) But, actually, so does the previous version (commit 389d...

I have two vectors (k.floor and k.ceiling) of integers of the same length, and a function (fpr). b <- 10:40 k.floor <- floor(log(2) * b) k.ceiling <- ceiling(log(2) * b) fpr.floor <- fpr(b, k.floor) fpr.ceiling <- fpr(b, k.ceiling) If R had a element-wise ternary function, I'd like to do something like this: (fpr.floor < fpr.ceiling) ? k.floor :

Dear All, Is this right? > floor((5.05-floor(5))*100) [1] 4 I would expect 5, or am I wrong? Thanks and regards, W --------------------------------- [[alternative HTML version deleted]]

Hello, I am not sure what to write in the subject line, but I would like to take a character string that is a variable in a data frame and apply a function that takes a numeric argument to this character string. Here is a simplified example that would solve my problem. Imagine I have my data stored in a data frame. > x1 <- x2 <- x3 <- x4 <- x5 <- rnorm(20,0,1); > data <-

I have some stub functions that are essentially static, but they cannot be removed. What linkage type should I use in that case. Internal linkage appears to get the functions discarded if they are not referenced under certain optimizations. This is part of the gcc mips16 hack for floating point. For example, a function like floor from the math library will be called with an external

Greetings: I'm running R2.6.2 on a WinXP DELL box with 2 gig RAM. I have created a new glm link function to be used with family = binomial. The function works (although any suggested improvements would be welcome), logit.FC <- function(POD.floor = 0, POD.ceiling =1) { if (POD.floor < 0 | POD.floor > 1) stop ("POD.floor must be between zero and one.") if

Hi all, in my search for a nice binary2decimal method, I received this nice code (thanx to Uwe Ligges): bindec <- function(b) sum(as.integer(unlist(strsplit(b, ""))) * 2^(floor(log10(b)):0)) It fails, however, with: > bindec(1000) [1] 4 Warning message: longer object length is not a multiple of shorter object length in: as.integer(unlist(strsplit(b, "")))

Hi everybody, given a fresh rgui.exe load on winxp OS, I enter (a minimal exaple) n <- 12.357531 Then the following command: n <- (n - floor(n))*10; n gives the following outputs: [1] 3.57531 [1] 5.7531 [1] 7.531 [1] 5.31 [1] 3.1 [1] 1 === still as expected [1] 10 === not expected, count with me: 1 - floor(1) is zero, times 10 gives 0, not 10!!!! [1] 10 === should

I have some data measured with a coarsely-quantized clock. Let's say the real data are q<- sort(rexp(100,.5)) The quantized form is floor(q), so a simple quantile plot of one against the other can be calculated using: plot(q,type="l"); points(floor(q),col="red") which of course shows the characteristic stair-step. I would like to smooth the quantized

The machine hosting all llvm.org services will be down briefly tomorrow morning US Central time for network maintenance. The maintenance is scheduled for 6-8am, but I am told our machine will be one of the first to come back up and could be up by 6:30am. --Vikram Associate Professor, Computer Science University of Illinois at Urbana-Champaign http://llvm.org/~vadve Begin forwarded

Hi, I have a test case would fail due to instruction combine cast from floor to floorf. double d = 1024.0 - 1.0 / 32768.0; extern double floor(double); extern float floorf(float); extern void abort(); int main() { float f1 = (float)floor(d); if ((int)f1 != 1023) abort (); return 0; } My question is: Is the transformation legal for this case? Thanks, Shiva

Hi, Please brace yourselves for some possibly stupid questions. Why are there only 2 codebooks for floors and many more for residue values? What makes the encoding of floor values fundamentally different from encoding residue values? I have a basic understanding of VQ, and looking at the floor decode function, it all makes sense 1) Read the codebook index from the stream 2) Do a

It seems that several intrinsics are missing from this routine. In particular, floor, which was causing problems in the mips16 port. Is there some reason to not add the ones that are missing? For example, adding the following fixed my problem with floor. case Intrinsic::floor: EnsureFPIntrinsicsExist(M, I, "floorf", "floor", "floor");

...? It would throw Xapian::UnimplementedError. > But, actually, so does the previous version (commit 389dfb319a66), which > explains why I had not understood what the limitation was. > > Both versions also work fine with "floor floor floor"p: > > (floors OR flooring OR floored OR floor) NEAR 13 > (floors OR flooring OR floored OR floor) NEAR 13 > (floors OR flooring OR floored OR floor) > > So: me happy but confused... I suspect that at most two of those terms are present in any given document in your database - the limitation was actually on the number of...

Maybe there is some attribute I can add this will not allow the function to be discarded. On 07/24/2013 03:45 PM, reed kotler wrote: > I have some stub functions that are essentially static, but they cannot > be removed. > > What linkage type should I use in that case. Internal linkage appears to > get the functions discarded if they are not referenced under certain >

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

At the risk of being beaten about the face and body, can somebody explain why the middle example: log2(2^3); floor(log2(2^3)) is different than examples 1 and 3? > log2(2^2); floor(log2(2^2)) [1] 2 [1] 2 > log2(2^3); floor(log2(2^3)) [1] 3 [1] 2 > log2(2^4); floor(log2(2^4)) [1] 4 [1] 4 > DrC [[alternative HTML version deleted]]

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

Perhaps somebody could clarify for me if the following is a floating point matter or otherwise, and how am I to correct for it? > floor(100*.1) [1] 10 > 100*(1.0-.9) [1] 10 > floor(100*(1-0.9)) [1] 9 Thanks! Michael _______________________________________________________ Michael Folkes Salmon Stock Assessment Canadian Dept. of Fisheries & Oceans Pacific Biological Station

On Tue, Nov 18, 2014 at 8:54 AM, Roland Scheidegger <sroland at vmware.com> wrote: > Am 18.11.2014 um 05:03 schrieb Ilia Mirkin: >> For values above integer accuracy in floats, val - floor(val) might >> actually produce a value greater than 1. For such large floats, it's >> reasonable to be imprecise, but it's unreasonable for FRC to return a >> value that