search for: overshoot

Hi, In the Sweave output for summary for several types of model objects and also for the comparison of models with anova, I find that that the display of the call(s) or formula does not obey the width option, even with keep.source=TRUE set, so that a long formula will overshoot the margins in the document. I would like to know if there is a good way to correct that. Looking at the print.summary methods for lm, glm and several others, I see that a construct like deparse(obj$call) is used to generate the text. The deparse function takes a "width.cutoff" argumen...

...d this format, some or all of this message may not be legible. ------_=_NextPart_001_01C00241.18831EF0 Content-Type: text/plain; charset="iso-8859-1" Anyone ever tried to plot(c(1.0,0,2),c(1.0,0,2)); symbols(c(1.0),c(1.0),circles=(c(1.0)),inch=FALSE,add=TRUE); #? Why does the circle overshoot ? The problem is the same on all devices (even with my pictex, which needs a lot of refurbishing), so I'd think it's something upstream to the devices code. Thanks, Valerio. (R-1.1.0 on Linux) --- Valerio Aimale Scientist direct: 505.992.6741 Bios Group LP...

...d this format, some or all of this message may not be legible. ------_=_NextPart_001_01C00241.18831EF0 Content-Type: text/plain; charset="iso-8859-1" Anyone ever tried to plot(c(1.0,0,2),c(1.0,0,2)); symbols(c(1.0),c(1.0),circles=(c(1.0)),inch=FALSE,add=TRUE); #? Why does the circle overshoot ? The problem is the same on all devices (even with my pictex, which needs a lot of refurbishing), so I'd think it's something upstream to the devices code. Thanks, Valerio. (R-1.1.0 on Linux) --- Valerio Aimale Scientist direct: 505.992.6741 Bios Group LP...

Hi, I am capturing 16 bit mono sound samples using some Win32 API function calls. These function calls return the sound samples in an array of characters. My assumption is that this array of characters represents pairs of bytes that make up a short integer. I'm using the following code to convert the samples: LPTSTR *lpSaveBuffer; ...... for(j=0;j<nBytes;++J) { BYTE a =

I''m CCing zfs-discuss at opensolaris.org, as this doesn''t look like FreeBSD-specific problem. It looks there is a problem with block allocation(?) when we are near quota limit. tank/foo dataset has quota set to 10m: Without quota: FreeBSD: # dd if=/dev/zero of=/tank/test bs=512 count=20480 time: 0.7s Solaris: # dd if=/dev/zero of=/tank/test bs=512 count=20480 time: 4.5s

...example that I constructed, axis(2) does exactly the expected thing. What I want to do next, though, with the least effort, is to add another function in a manner that the added function is scaled, not according to the first function (plot), but to fit into the plotting area. (The example above overshoots the range). Plus, how can I subsequently add the axis suitable to the most recent function? That is, how can I render axis(4) to displaying the scale for the second graph, created with 'curve'? Thanks in advance, Uwe

...tand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C00240.001284B0 Content-Type: text/plain; charset="iso-8859-1" Anyone ever tried to plot(c(1.0,0,2),c(1.0,0,2)); symbols(c(1.0),c(1.0),circles=(c(1.0)),inch=FALSE,add=TRUE); Why does the circle overshoot ? The problem is the same on all devices (even with my pictex, which needs a lot of refurbishing), so I'd think it's something upstream to the devices code. Thanks, Valerio. (R-1.1.0 on Linux) --- Valerio Aimale Scientist direct: 505.992.6741 Bios Group LP...

...s that stat is indeed reporting allocated size caused by the filesystem pre-emptively over-allocating based on access patterns (more so when creating the first file, especially when reopening the file; less so when copying as the source file size is now stabilized so the copy has less reason to overshoot). But since the real crux of the test is whether we managed to punch holes, would it be sufficient to take note of the original sizes, and merely check that the resulting size has either shrunk (where the file should now be sparser) or remained unchanged? I'll push a patch along those line...

...r quality feel. What I'm talking about is mostly the movement it uses. As I've come to understand, it uses velocity and direction, and a target point. This means that it updates it velocity and direction every X seconds (timestep), and gives it the possibility to be unaccuarte, like overshoot its goal and wobble a little. What my issue is though, is that even though you set timestep very low, it still is a little wobble present. What I would love would be another movement, like the one that is used in the animation plugin, where timestep is just how many times to redraw the an...

...l keep it around for testing purposes.) The only remaining issue is the way that Opus doesn't even come close to respecting the requested bitrate for this sample. For instance, encoding it at 130 gives me a file of 210kbps. Over a wide corpus of music, I've noticed libopus almost invariably overshoots the bitrate, rather than averaging out close to it; only speech is consistently at or below it. Em -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20181105/8cd1cdd6/attachment.html>

...ives for (i in 1:length(y)) { if (y[i]<0) { y[i] <- 0 } } S <- y[1] I <- y[2] R <- y[3] N <- y[4] shat <- (birth*(1-vax)) - (death*S) - (beta*S*I/N) ihat <- (beta*S*I/N) - (death*I) - (recover*I) rhat <- (birth*(vax)) + (recover*I) - (death*R) ## Do we overshoot into negative space, if so shrink derivative to bring state to 0 ## then rescale the components that take the derivative negative if (shat+S<0) { shat_old <- shat shat <- -1*S scaled_transmission <- (shat/shat_old)*(beta*S*I/N) ihat <- scaled_transmission - (death*I) - (re...

...g like this, suitably wrapped: > summary(glm.D93) Call: glm(formula = counts ~ outcome + treatment, family = poisson()) As far as I can recall, print.summary.glm and print.summary.lm are the only times I have seen this behaviour. I found a similar thread posted June 2009 ("overshoot of formula line in summary output of Sweave"); there appeared no resolution in that thread, or after contacting the originator of the post. So my question: * What can I do to ensure my output is not extending too far to the right with print.summary.glm? Thanks as always. P. >...

Dear all, I am using abline(lm ...) to insert a linear trendline through a portion of my data (e.g. dataset[,36:45]). However, I am finding that whilst the trendline is correctly displayed and representative of the data portion I've chosen, the line continues to run beyond this data segment and continues until it intersects the vertical axes at each side of the plot. How do I display the

Hey list I have almost gotten my shaping setup up and running as planned. The last barrier seems to be tcp overshooting availible bandwidth when its starting a transfer, and thereby bursting the line, so ping rises for a moment. At least this is my best guess at the problem :) There is a possibility that its just plain old traffic being bursty for some reason.. I am using bittorrent to test this, as it seems to b...

...> reporting allocated size caused by the filesystem pre-emptively > over-allocating based on access patterns (more so when creating the > first file, especially when reopening the file; less so when copying > as the source file size is now stabilized so the copy has less > reason to overshoot). But since the real crux of the test is whether > we managed to punch holes, would it be sufficient to take note of > the original sizes, and merely check that the resulting size has > either shrunk (where the file should now be sparser) or remained > unchanged? > > I'll pus...

Is "nBytes" what it says -- the number of bytes in the buffer? If so, you're overshooting the buffer by 2x by multiplying by 2 in your array access. You probably want a variable called "nSamples" that represents the number of 16-bit words. Also, if this is a little-endian (Windows on x86?) machine, you're reassembling the word backwards. Not to mention, shifting a BY...

I always assumed that ov_read_float() would get me samples in the range of [-1,1), and anything below or above that can be clamped (or clipped in the final conversion to an integer format.) However, I recently saw this: https://github.com/LaurentGomila/SFML/issues/310#issuecomment-9974550 Apparently, there are Vorbis streams that use float samples with values in the range of [-32768,

...testing purposes.) The only > remaining issue is the way that Opus doesn't even come close to respecting > the requested bitrate for this sample. For instance, encoding it at 130 > gives me a file of 210kbps. Over a wide corpus of music, I've noticed > libopus almost invariably overshoots the bitrate, rather than averaging out > close to it; only speech is consistently at or below it. Maybe there's some bug still undiscovered. Would you agree that Opus should encode a pure sinus tone efficiently? Or would it really prefer to encode white noise? Regards, Ulrich

Dear help-list, I have a problem with timeSequence {timeDate}. When I use it like > timeSequence(from = "2008-01-01", to = "2010-12-13", by = "1 month") GMT [1] [2008-01-01] [2008-02-01] [2008-03-01] [2008-04-01] [2008-05-01] [2008-06-01] [2008-07-01] [2008-08-01] [2008-09-01] [2008-10-01] [2008-11-01] [12] [2008-12-01] [2009-01-01] [2009-02-01] [2009-03-01]

Hi All, What I would like to do is the following: a) fit a probability function to a measured data set. This would be user specified, e.g., normal, lognormal, etc. and then b) take the probability function and plot it with the histogram of the measured data set. This function would be displayed as a smooth curve. This would involve "re-sizing" the probability function to match