search for: underlie

Friends I have a data frame, df that I want to extract some rows from Here is a sample of the data > head(df) TDate Expiry Underlie Strike CSettle PSettle Futures ExDate TTE 1 20080102 200801 200803 0.840 0.0000 0 0.9207 20080104 0.005479452 2 20080102 200801 200803 0.850 0.0000 0 0.9207 20080104 0.005479452 Rate Disc 1 0.0457 0.9997496 2 0.0457 0.9997496 I want all rows where TTE is equal to 0...

...OS & with my time zone. Regardless of the exact number, unlisting a time class converts it to a numeric. - upon converting to a numeric, it seems there is an underlying, assumed origin of "1970-01-01 00:00:00". However, this same assumption does not underlie the conversion *back* to a POSIX time, e.g., through as.POSIXct() function. Therefore, whenever a time is "accidentally" converted to a numeric, I have to force it back to a time through as.POSIXct(), *providing my own details* as to the origin. There...

...OS & with my time zone. Regardless of the exact number, unlisting a time class converts it to a numeric. - upon converting to a numeric, it seems there is an underlying, assumed origin of "1970-01-01 00:00:00". However, this same assumption does not underlie the conversion *back* to a POSIX time, e.g., through as.POSIXct() function. Therefore, whenever a time is "accidentally" converted to a numeric, I have to force it back to a time through as.POSIXct(), *providing my own details* as to the origin. There...

...er than a blind "sorry you can't build anymore". > So those comments (esp. the one on commit f306e231d294) at least confirm > that the difference is intentional. I still don't know the reason for > the difference. And now I wonder: does the same (unexplained) reason > underlie the "sentinel" attribute's absence too, in libnbd? > > If there is a common reason for avoiding both "cleanup" and "sentinel" > in libnbd, we should probably not start using "sentinel" now. If, on the > other hand, "sentinel" is not...

WinXP, R-2.9.1 LS., I have been trying to solve a (for me) tricky issue. No matter what I've tried, I just can't find a way to do this. This is the issue: I have a text file (ansi text) "titles.txt" with lines of text; here is an example of such a file: >>>>> a brief history of polio vaccines anti-vaccination movements and their interpretations early warning

Hi, I'm running this for a simulation study, so many combinations of parameter produce many predictions that I need to correlate with data. The problem ---------------- I'm using rating data with 3 to 5 categories (e.g., too low, correct, too high). The underlying continuous scales should be normal, so I chose the polychoric correlation. I'm using library(polychor) in its

...t;>> non-HPC workloads. >>> >>> This is clearly a good question, but thinking about Polly as a >>> set of components, not as a monolithic transformation component, >>> I think that polyhedral analysis and transformations can >>> underlie a lot of the transformations we need for non-HPC code >>> (and, which I'll point out, we need for modern HPC code too). In >>> practice, the loops that we can actually analyze have affine >>> dependencies, and Polly does, or can do, a better job at >&gt...

> >>>>> "PD" == Peter Dalgaard BSA <p.dalgaard at biostat.ku.dk> writes: > > PD> "Venables, Bill (CMIS, Cleveland)" <Bill.Venables at cmis.CSIRO.AU> > PD> writes: > >> The fact that every elementary book on statistics does it this way > >> does not make it correct. To be helpful, a histogram really

...ingly or doubly nested not-so-regular loops which are the norm in > non-HPC workloads. > > > This is clearly a good question, but thinking about Polly as a set of > components, not as a monolithic transformation component, I think that > polyhedral analysis and transformations can underlie a lot of the > transformations we need for non-HPC code (and, which I'll point out, we > need for modern HPC code too). In practice, the loops that we can actually > analyze have affine dependencies, and Polly does, or can do, a better job > at generating runtime predicates and deal...

...e should use it for singly or doubly nested not-so-regular > loops which are the norm in non-HPC workloads. This is clearly a good question, but thinking about Polly as a set of components, not as a monolithic transformation component, I think that polyhedral analysis and transformations can underlie a lot of the transformations we need for non-HPC code (and, which I'll point out, we need for modern HPC code too). In practice, the loops that we can actually analyze have affine dependencies, and Polly does, or can do, a better job at generating runtime predicates and dealing with piecew...

Hi R help list I'm simulating logistic regression data with a specified odds ratio (beta) and have a problem/unexpected behaviour that occurs. The datasets includes a lognormal exposure and diseased and healthy subjects. Here is my loop: ors <- vector() for(i in 1:200){ # First, I create a vector with a lognormally distributed exposure: n <- 10000 # number of study subjects

...ot-so-regular loops which are >> the norm in non-HPC workloads. >> >> >> This is clearly a good question, but thinking about Polly as a set of >> components, not as a monolithic transformation component, I think that >> polyhedral analysis and transformations can underlie a lot of the >> transformations we need for non-HPC code (and, which I'll point out, we >> need for modern HPC code too). In practice, the loops that we can actually >> analyze have affine dependencies, and Polly does, or can do, a better job >> at generating runtime pre...

...t;>>> >>>> This is clearly a good question, but thinking about Polly >>>> as a set of components, not as a monolithic transformation >>>> component, I think that polyhedral analysis and >>>> transformations can underlie a lot of the transformations >>>> we need for non-HPC code (and, which I'll point out, we >>>> need for modern HPC code too). In practice, the loops that >>>> we can actually analyze have affine dependencies, and Polly >>>>...

...should use it for singly or doubly nested not-so-regular loops which are the norm in non-HPC workloads. > > This is clearly a good question, but thinking about Polly as a set of components, not as a monolithic transformation component, I think that polyhedral analysis and transformations can underlie a lot of the transformations we need for non-HPC code (and, which I'll point out, we need for modern HPC code too). In practice, the loops that we can actually analyze have affine dependencies, and Polly does, or can do, a better job at generating runtime predicates and dealing with piecewise-l...

Hello, I carelessly sent this to the unfortunate Mr. Johnson, rather than to the list, so I'm sending it on to the list. Re-reading it after a couple days, I think that it might still be worth sharing. I think I agree with an earlier reply: GUI's are confining, and eventually slow you down, relative to programming. The strong point of a GUI is that it lets you quickly, easily do a new

...>>> not-so-regular loops which are the norm in non-HPC workloads. >> >> This is clearly a good question, but thinking about Polly as a set of >> components, not as a monolithic transformation component, I think >> that polyhedral analysis and transformations can underlie a lot of >> the transformations we need for non-HPC code (and, which I'll point >> out, we need for modern HPC code too). In practice, the loops that we >> can actually analyze have affine dependencies, and Polly does, or can >> do, a better job at generating runtime...

...ingly or doubly nested not-so-regular loops which are the norm in > non-HPC workloads. > > > This is clearly a good question, but thinking about Polly as a set of > components, not as a monolithic transformation component, I think that > polyhedral analysis and transformations can underlie a lot of the > transformations we need for non-HPC code (and, which I'll point out, we > need for modern HPC code too). In practice, the loops that we can actually > analyze have affine dependencies, and Polly does, or can do, a better job > at generating runtime predicates and deal...

Are folks in the Centos community succesfully using device-mapper-multipath? I am looking to deploy it for error handling on our iSCSI setup but there seems to be little traffic about this package on the Centos forums, as far as I can tell, and there seems to be a number of small issues based on my reading the dm-multipath developer lists and related resources. -geoff Geoff Galitz Blankenheim

...t; >>>loops which are the norm in non-HPC workloads. > >> > >>This is clearly a good question, but thinking about Polly as a set of > >>components, not as a monolithic transformation component, I think that > >>polyhedral analysis and transformations can underlie a lot of the > >>transformations we need for non-HPC code (and, which I'll point out, we > >>need for modern HPC code too). In practice, the loops that we can > >>actually analyze have affine dependencies, and Polly does, or can do, a > >>better job at genera...

...d Message Attachment-- From: hadley at rice.edu To: R-help at r-project.org Date: Mon, 23 Aug 2010 10:33:54 -0500 Subject: [R] Recyclable Hi all, Is there a function to determine whether a set of vectors is cleanly recyclable? i.e. is there a common function for detecting the error/warnings that underlie the following two function calls? > 1:3 + 1:2 [1] 2 4 4 Warning message: In 1:3 + 1:2 : longer object length is not a multiple of shorter object length > data.frame(1:3, 1:2) Error in data.frame(1:3, 1:2) : arguments imply differing number of rows: 3, 2 Hadley -- Assistant Professor...