similar to: Input to variables - help please

Hello, I have an r function that creates the following dataframe tresults2. Notice that column 1 does not have a column heading. Tresults2: [,1] estparam 18.00000 nullval 20.00000 . . . ciWidth 2.04622 HalfInterval 1.02311 pertinent code: results<-cbind( estparam, nullval, t, pv_left, pv_right, pv_two_t, estse, df, cc, tbox, llim, ulim, ciWidth,

How well dose theora handle varaiable frame rate? I looking a using a rolling frame rate that move up and down from 1 frame per 60 second (no montion) to 100 frames per second (very fast montion eg: lightning) tom_a_sparks Light travels faster then sound, which is why some people appear bright, until you hear them speak

Hello! I'm trying my hand at lattice representations; I would like to represent a continuous varaiable as function of 2 factors and therefore use the following: bwplot(x ~f1| f2) which works fine except that it plots black points at the value of the median. How can I remove them? Thanks Anne [[alternative HTML version deleted]]

Dear list I have quite a small data set in which I need to have the following values ignored - not used when performing an analysis but they need to be included later in the report that I write. Can anyone help with a suggestion as to how this can be accomplished Values to be ignored 0 - zero and 1 this is in addition to NA (null) The reason is that I need to use the log10 of the values

Shankar and I discussed input file handling, and we came up with a design that may greatly simplify the input file handling, while giving more flexibility to developer to support complicated options, such as --{start,end}-group, -z rescan or -z rescan-now. It'd worth pursuing, so here's the idea: 1. We wouldn't probably want to let Resolver to handle the input graph directly, for we

Dear list I am trying to re-scale a histogram and using hist() but can not seem to create a reduced scale where the upper values are not plotted. What I have is about 100 of which 80 or so are between a value of 0 and 40 , one or two in the hundreds and an outlier around 2000. What I would like to do is create an x-scale that shows 5 bins between 0-100 and then 3/4 bins between 100 and 2000

On Sep 20, 2013, at 3:37 PM, Rui Ueyama <ruiu at google.com> wrote: > On Fri, Sep 20, 2013 at 3:29 PM, Nick Kledzik <kledzik at apple.com> wrote: > Rui, > > I like this in general, but have a few questions. > > On Sep 20, 2013, at 2:30 PM, Rui Ueyama <ruiu at google.com> wrote: > >> 2. We would instead add a new method nextFile() to LinkingContext,

Hi Nick, On 9/20/2013 5:59 PM, Nick Kledzik wrote: > On Sep 20, 2013, at 3:42 PM, Shankar Easwaran > <shankare at codeaurora.org> wrote: >> nextFile could pass the current resolver state at the time when its called, the linkingcontext can return the next file to be processed as below :- >> >> nextFile(currentResolverState) :- >> >> a) Returns the next

Shankar, I think your proposal and mine are pretty much the same. The difference is passing back info to the InputGraph as a parameter in nextFile() vs as a separate method call. My original draft email had a parameter in nextFile(), but it seemed a little confusing because the information was referring to the previous file. That is, if the current resolver state has newDefinedAtoms, that

My email client spoilt the whole email, will create a pdf and send it. On 9/20/2013 7:00 PM, Shankar Easwaran wrote: > Hi Nick, > > On 9/20/2013 5:59 PM, Nick Kledzik wrote: >> On Sep 20, 2013, at 3:42 PM, Shankar Easwaran >> <shankare at codeaurora.org> wrote: >>> nextFile could pass the current resolver state at the time when its >>> called, the

Hi, Attached is the pdf of the operation to make things easier to read. Thanks Shankar Easwaran On 9/20/2013 7:04 PM, Shankar Easwaran wrote: > My email client spoilt the whole email, will create a pdf and send it. > > On 9/20/2013 7:00 PM, Shankar Easwaran wrote: >> Hi Nick, >> >> On 9/20/2013 5:59 PM, Nick Kledzik wrote: >>> On Sep 20, 2013, at 3:42 PM,

Hi Nick, Read this along with this example extract: ld -flavor gnu main.o thread.o --start-group libc.a libpthread.a --end-group function.o main.o has atoms ------------------------ main (defined) printf(undefined) fn(undefined) thread.o has atoms ----------------------------- pthread_create (undefined) libc.a(printf.o) has atoms ------------------------------------ printf(defined)

Rui, I like this in general, but have a few questions. On Sep 20, 2013, at 2:30 PM, Rui Ueyama <ruiu at google.com> wrote: > 2. We would instead add a new method nextFile() to LinkingContext, which returns a new file from which Resolver should try to resolve undefined symbols. Resolver wouldn't handle the input graph at all. Instead, Resolver calls nextFile() repeatedly to link

Hi Nick, On 9/20/2013 5:29 PM, Nick Kledzik wrote: > Rui, > > I like this in general, but have a few questions. > > On Sep 20, 2013, at 2:30 PM, Rui Ueyama <ruiu at google.com> wrote: > >> 2. We would instead add a new method nextFile() to LinkingContext, which returns a new file from which Resolver should try to resolve undefined symbols. Resolver wouldn't

Description: Split the Strings in `x' into substrings according to the presence of substring `split' within them. -------------------- > strsplit("acbdefgSPLIThigkilmnSpPqrst","SPLIT") [[1]] [1] "acbdefg" "higkilmn" "p" "qrst" -------------------- Apparently, it will Split the Strings in `x' into

On Fri, Sep 20, 2013 at 3:59 PM, Nick Kledzik <kledzik at apple.com> wrote: > > On Sep 20, 2013, at 3:37 PM, Rui Ueyama <ruiu at google.com> wrote: > > On Fri, Sep 20, 2013 at 3:29 PM, Nick Kledzik <kledzik at apple.com> wrote: > >> Rui, >> >> I like this in general, but have a few questions. >> >> On Sep 20, 2013, at 2:30 PM, Rui

Hi! Im making a small research about IMAP servers and it's features. As the subject suggests, I want make a shared mailbox, with per user \seen flag to work like a mailin-list works. The reason to use 1 shared folder is simple: Imagine 12k users sending 1KB messages each week, it will be 12+ MB of useless information. Many people told me that IMAP could do this, but now seem that it is a

On Fri, Sep 20, 2013 at 04:39:04PM -0700, Rui Ueyama wrote: > I don't want to make Resolver to have a reference to input graph. The point > of this proposal is to separate input graph handling from Resolver and > instead making Linker Context to do that task. That was the part of the original proposal I didn't agree with and I still don't do. While the resolver shouldn't

Hi everyone, I am new to R, but it's really great and helped me a lot! But now I have 2 questions. It would be great, if someone can help me: 1. I want to integrate a normal distribution, given a median and sd. The integrate function works great BUT the first argument has to be a function so I do integrate(dnorm,0,1) and it works with standard m. and sd. But I have the m and sd given.

Hi all, The PowerPC ELF backend of LLD is not in a particularly good state. It supports one relocation, has one test, and it does not seem to have received any commits other than tree-wide refactors since it was initially committed. It is also structured slightly differently to the other backends which means that refactoring patches that touch all the backends are made more difficult. Is anyone