search for: monthi

Greetings all, Every now and then, as we engage in serious discourse, it seems appropriate to throw something into the mix that might digress and brighten the day. So, what is a Strouhal Number? "For an animal or insect in flight, the Strouhal number is determined by the frequency (f) of wing strokes, multiplied by the amplitude (A) of the wing, divided by the animal?s forward speed (U)

Is there any way to give a "decent" title after I plot something generated by decompose? For example: # generate something with period 12 x <- rnorm(600) + sin(2 * pi * (1:600) / 12) # transform to a monthy time series y <- ts(x, frequency=12, start=c(1950,1)) # decompose z <- decompose(y) # plot plot(z) Now, the title is the ugly "Decomposition of additive time

Hello R users It's some time I am playing with a dataset to do some cluster analysis. The data set consists of 14 columns being geographical coordinates and monthly temperatures in annual files latitutde - longitude - temperature 1 -..... - temperature 12 I have some missing values in some cases, maybe there are 8 monthly valid values at some points with four non valid. I don't want to

Dear R Users, I am trying to get plot.zoo to place monthy tickmarks/labels for a time series which spans daily data going back a bit over a year. Right now, I am getting only one tick mark on the x-axis for the beginning of 2008. How can I force plot.zoo to place more regular x-axis tick marks on a monthly basis ? Thanks in advance, Tolga Generally, this communication is for informational

hi everyone! I have a 40-year monthy streamflow record. And i want to fit a neural network. I already fitted an autoregressive model and found out that an AR(3) model fits my time series (time.series) the best. I am currently having problems on how to express the argument "formula" for my neural network.. I am aware that my model should be Q(t) ~ Q(t-1) + Q(t-2) + Q(t-3). But I

Hallo all, for some (long) time, Monthy added telemetry debuging to theora. And (only) now gstreamer use it in upstream. http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=ab52e15e3d9ebc2c5a784aa8cc8a4bc15a40edca http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=a044b62cf5763240d5243b9326d886ed34379dab Regards, Alexey.

Hal Finkel <hfinkel at anl.gov> writes: >> I would like that very much. It's a resource issue, not a technical >> one. > > I think that it might be useful to think about changing the parameters > of this optimization problem. Could you release enough of the testing > system so that others could help? I can't make that decision and I very much doubt we

All, After months of intensive development, we're finally coming to a stopping point in our rewrite of the libtheora reference implementation. All major features for the 1.1 are in, so it's down to bug fixing now. Please try this first beta and give us feedback. Most notable is that the encoder's rate control is much more configurable, and more capable in each configuration than

All, After months of intensive development, we're finally coming to a stopping point in our rewrite of the libtheora reference implementation. All major features for the 1.1 are in, so it's down to bug fixing now. Please try this first beta and give us feedback. Most notable is that the encoder's rate control is much more configurable, and more capable in each configuration than

Hi everyone, We finally made it! Opus is now standardized by the IETF as RFC 6716 (http://tools.ietf.org/html/rfc6716). See the announcements at: https://hacks.mozilla.org/2012/09/its-opus-it-rocks-and-now-its-an-audio-codec-standard/ http://www.xiph.org/press/2012/rfc-6716/ Feel free to spread those around :-) We're also releasing both 1.0.0 (same code as the RFC) and 1.0.1, which is a

Hi everyone, We finally made it! Opus is now standardized by the IETF as RFC 6716 (http://tools.ietf.org/html/rfc6716). See the announcements at: https://hacks.mozilla.org/2012/09/its-opus-it-rocks-and-now-its-an-audio-codec-standard/ http://www.xiph.org/press/2012/rfc-6716/ Feel free to spread those around :-) We're also releasing both 1.0.0 (same code as the RFC) and 1.0.1, which is a

Hi All, I am now working on a plan of what to backup from various servers that I have running I run Apache, so httpd.conf and /var/www/html I run Zimbra currently, so /opt/zimbra/store, /opt/zimbra/my.cnf and /opt/zimbra/db/ I run MySQL, so /etc/my.cnf and /var/lib/mysql Can I simply write a bash script to tar.gz these areas, scp them and put it in a cron job? Is there anything special that

Hi, I have 6 Red FXO with TDM2400p in my PC. I have install asterisk and dahdi driver. Scenario is jitsi-----> asterisk server-----> analog PBX ----> landline phone I configured this scenario as follow in chan_dahdi.conf file ; General options [channels] usecallerid=yes hidecallerid=no callwaiting=yes threewaycalling=yes transfer=yes

On Thu, 10 May 2012 11:24:12 -0500 <dag at cray.com> wrote: > Hal Finkel <hfinkel at anl.gov> writes: > > > Out of curiosity, can your frontend be configured to produce LLVM IR > > that could be fed though the trunk backend passes, or is a tighter > > integration required? > > Yes, we have this capability. > > > If it is possible to produce

On Thu, 10 May 2012 14:58:41 -0500 <dag at cray.com> wrote: > Hal Finkel <hfinkel at anl.gov> writes: > > >> I would like that very much. It's a resource issue, not a > >> technical one. > > > > I think that it might be useful to think about changing the > > parameters of this optimization problem. Could you release enough > > of

Hal Finkel <hfinkel at anl.gov> writes: > Out of curiosity, can your frontend be configured to produce LLVM IR > that could be fed though the trunk backend passes, or is a tighter > integration required? Yes, we have this capability. > If it is possible to produce LLVM IR, then it might be possible to > test a lot, although not all, of the upstream changes using your >

I came across the tidbit that ZFS has a contract guarantee that the data read back will either be correct (the checksum computed over the data read from the disk matches the checksum stored on disk), or you get an I/O error. Obviously, this greatly reduces the probability that the data is invalid. (Particularly when taken in combination with the disk firmware''s own ECC and checksumming.)