search for: drifting

Hello everybody! I have a problem when I try to perform a forecast of an ARIMA model produced by an auto.arima function. Here is what I'm doing: c<-auto.arima(fil[[1]],start.p=0,start.q=0,start.P=0,start.Q=0,stepwise=TRUE,stationary=FALSE,trace=TRUE) # fil[[1]] is time series of monthly data ARIMA(0,0,0)(0,1,0)[12] with drift : 1725.272 ARIMA(0,0,0)(0,1,0)[12] with drift

Hello everyone! I been observing some peculiar time drift on my Xen domains (dom0 and domUs). The time (as returned by timeofday) on my domains drifts at an almost steady rate from the real time ( as read from the time stamp counter ). The drift is so constant that it makes me think there should be some simple explanation for it in the way Xen keeps time. Some info about my set up: guest OS:

The time appears to be perfect inside dom0, however all the domU''s tend to have a slightly faster date which gets further out of sync every day. I''m currently using Xen 3.0.3 with Gentoo Linux, under 3.0.2 I had no problems with domU clocks. Are there any known issues which could cause this? I''d strongly prefer not to run ntpd in every domU, having all domU clocks in

Hi, I've noticed that one of my new servers (new mobo) if drifting slowly backwards in time (in aprox. 24 hours, system time drifts back 5 minutes). I have an ntpd process which is supposed to sync with a lan time server but it's not quite working. So I'm launching a manual ntpdate or ntp-client once an hour and that seems to work. However, suppose I upd...

Hi On 5.3 i have a situation where some boxes have been 3 or 4 seconds out and restarting ntpd has fixed the issue. What i dont understand is why the clocks did not drift to the correct time when the config seems correct in that restarting ntp did correct the time. Is there something 'special' i need to do in order for the drift to work? $ cat /etc/ntp.conf restrict default

In reading the Xen list there are frequent postings regarding NTP time drift issues for virtualized guests, correct configurations, etc. We have a solution (no cost) for monitoring time drift of hosts for anyone needing to do so or to determine whether their environment is maintaining time synchronization. For etiquette I am not publishing the information to the list mailing. If interested,

...Designing Software AEC on Personal Computers) is a good paper. But some critical details were omitted. Let me have a summary. 1. The paper points out two phenomena which break the synchronization/alignment of far-end signal and near-end signal. They are glitch (caused by loss of samples) and clock drifting (caused by different clock generators). 2. It introduces a concept of Relative Sample Offset (RSO, d[i]). It indicates the time drifting of relevant samples in far-end signal and near-end signal. If no glitch and clock drifting, RSO (d[i]) will be constant. Glitch will make it change suddenly wher...

1. Shouldn''t the GPLPV drivers take care of the (bad) clock drift I''m experiencing in my Windows XP HVM? Or is there some other way around this problem that I haven''t been able to find on Google? How can I tell if the GPLPV drivers are active? I''ve added the /gplpv switch to the boot.ini file and the virtual NIC is definitely using the GPLPV version but other

Dear R-Users, I have the following problem to solve and I wonder if there are means in R that can help me. At irregular time intervals I observe a random walk process, Y, with time-varying drift. I assume that the drift, D, is a (linear) function of some parameter X. The goal is to estimate D(X). I could regress Y_{t+dt} - Y_{t} ~ X, but it's probably not appropriate since Var(Y_{t+dt} -

You might find this useful ... TSC and Power Management Events on AMD Processors - Nov 2, 2005 - Rich Brunner, AMD Fellow Current AMD Opteron(tm) and Athlon(tm)64 processors provide power management mechanisms that independently adjust the performance state ("P-state") and power state ("C-state") of the processor[1][2]; these state changes can affect a

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.

...on all hosts are set to tsc * Clocksource on all guests are set to kvm-clock * CPUs on the hosts are Intel Xeons, all have these related flags: tsc, constant_tsc, nonstop_tsc. One host has tsc_deadline_timer as an extra, because it's a newer Xeon, but it doesn't seem to make a difference in drifting. * Most guests complain about "Clocksource tsc unstable" in dmesg after boot (even when set to clocksource=kvm-clock) * The hosts don't drift at all, we only see the issue in guests * We don't use CPU pinning for KVM guests * We run OpenNTPD 5.7p4 on both the hosts and the guests...

...on all hosts are set to tsc * Clocksource on all guests are set to kvm-clock * CPUs on the hosts are Intel Xeons, all have these related flags: tsc, constant_tsc, nonstop_tsc. One host has tsc_deadline_timer as an extra, because it's a newer Xeon, but it doesn't seem to make a difference in drifting. * Most guests complain about "Clocksource tsc unstable" in dmesg after boot (even when set to clocksource=kvm-clock) * The hosts don't drift at all, we only see the issue in guests * We don't use CPU pinning for KVM guests * We run OpenNTPD 5.7p4 on both the hosts and the guests...

Hi All, Sorry again to bother you with this but there is really something I don't fully understand about client/server clock syncs. If I connect to the stream with a fresh browser, I can measure between 5-10 secs latency. I keep listening to it for while, and the delay between server and client grows as listening is going on. As pointed out Philipp yesterday to me, it's approximately a 5%

Dear R-helpers. Would appreciate if someone can explain the warning messages below, after auto.arima. I couldn't find any clue in the archived help. Also, how do I retrieve the AICs of each tried model in auto.arima? The purposes are (1) to output to a text file, and (2) to find the 2nd best model by finding 2nd lowest AIC instead of eyeballing thru the value at the console

Dear R-helpers, I would appreicate if someone can help me on the transfer parameter in ARIMAX and also see what I am doing is correct. I am using ARIMAX with 2 Exogeneous Variables and 10 years data are as follows: DepVar Period, depVar, IndepVar1 Period, indepVar1, IndepVar2 Period, indepVar2 Jan 1998,708,Jan 1998,495,Jan 1998,245.490 Feb 1998,670,Feb 1998,421.25,Feb 1998,288.170 Mar

Hello, I have a question on unit root test with urca toolbox. First, to run a unit root test with lags selected by BIC, I type: > CPILD4UR<-ur.df(x1$CPILD4[5:nr1], type ="drift", lags=12, selectlags ="BIC") > summary(CPILD4UR) The results indicate that the optimal lags selected by BIC is 4. Then I run the same unit root test with drift and 4 lags:

We have a local time server and all of our machines are pointed at it for the time. How can the clock drift by a day and a half? [root at devserver21 ~]# date Fri Aug 13 14:43:29 EDT 2010 [root at devserver21 ~]# rdate -s 192.168.1.67 [root at devserver21 ~]# date Thu Aug 12 07:02:39 EDT 2010 [root at devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ restrict default nomodify notrap

...Designing Software AEC on Personal Computers) is a good paper. But some critical details were omitted. Let me have a summary. 1. The paper points out two phenomena which break the synchronization/alignment of far-end signal and near-end signal. They are glitch (caused by loss of samples) and clock drifting (caused by different clock generators). 2. It introduces a concept of Relative Sample Offset (RSO, d[i]). It indicates the time drifting of relevant samples in far-end signal and near-end signal. If no glitch and clock drifting, RSO (d[i]) will be constant. Glitch will make it change suddenly wher...

Hi, I'm a new user of R. My background is Electrical Engineering, so please bear with me if this is a silly question. I'm trying to assess whether the results of an experiment satisfy the hypothesis of homoscedasticity (my ultimate goal is to use ANOVA). The result of the experiment is mean delay (dT), which depends on three factors, topology, drift, and lambda. The first two factors are