search for: retimed

Hi: Is there a way to retime a flow in order to compensate for jitter? For example, RTP has timestamps which would enable retiming. Or you could be simpler and just make the exit interval equal to the average intrance interval. I''m sure there are even better ways that I just haven''t thought of. -- Lawrence MacIntyre 865.574.8696 lpz@ornl.gov Oak

Hi, I used Dr. Harrell's rms package to make a nomogram. Below is my code for nomogram and calculate total points and probability *in original data set* used for building the nomogram. *My question is how I get the formula for calculating the survival probability for this nomogram. Then I can use this formula to do validation by using other data set. * f1 <- cph(Surv(retime,dfs) ~

Hello, I am using Dr. Harrell's rms package to make a nomogram. I was able to make a beautiful one. However, I want to change 5-year survival probability to 5-year failure probability. I couldn?t get hazard rate from Hazard(f1) because I used cph for the model. Here is my code: library(rms) f1 <- cph(Surv(retime,dfs) ~ age+her2+t_stage+n_stage+er+grade+cytcyt+Cyt_PCDK2 , data=data11,

Hello, I am using Dr. Harrell's design package to make a nomogram. I was able to make a beautiful one. However, I want to change 5-year survival probability to 5-year failure probability. I couldn?t get hazard rate from Hazard(f1) because I used cph for the model. Here is my code: f1 <- cph(Surv(retime,dfs) ~ age+her2+t_stage+n_stage+er+grade+cytcyt+Cyt_PCDK2 , data=data11, surv=T,

...ove the code generator to notice and handle this, I added this note to the x86 backend with some details: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090202/073254.html This is a long-known issue, but a great example of it. > Two other points of interest: > > . I just retimed in x64 and could not reproduce the difference so > this only > afflicts x86 and not x64 as I had said previously. Right, this occurs because of the x86-32 ABI. x86-64 should not be affected. > . Pulling the whole benchmark into a single compilation unit changes > the > perfo...

On 2008-11-13, Conrad Parker <conrad at metadecks.org> wrote: > I'm wondering if the Dirac granulepos parsing in liboggz and display > in the oggz tools is currently correct, as I'd like to do a release of > these soon. I believe it is -- although if correct support in the rest of the liboggz tools is required, a little more work may need to happen. > Here's some

Hi, I'm wondering if the Dirac granulepos parsing in liboggz and display in the oggz tools is currently correct, as I'd like to do a release of these soon. A couple of days ago David Schleef mentioned there were some problems. David, is that currently true (ie. since David Flynn's recent updates to support Dirac), and if so could you please explain what the problems are, or point me

Hello everyone, This set will switch the users of pm_runtime_put_autosuspend() to __pm_runtime_put_autosuspend() while the former will soon be re-purposed to include a call to pm_runtime_mark_last_busy(). The two are almost always used together, apart from bugs which are likely common. Going forward, most new users should be using pm_runtime_put_autosuspend(). Once this conversion is done and