Displaying 19 results from an estimated 19 matches for "0.0173".
Did you mean:
0.013
2011 Mar 16
2
Removing Bad Data
I created a couple of timeSeries objects - when I was merging them , I got an
error.
Looking at the data , I see that one of the time series has
06/30/2007 0.0028 0.0183 0.0122 0.0042 0.0095 -
07/31/2007 -0.0111 0.0255 0.0096 -0.0069 -0.0024 0.0043
08/31/2007 -0.0108 -0.0237 -0.0062 -0.0138 -0.0173 -0.0065
09/30/2007
2005 Dec 22
6
Plot problems: xlim
Hi,
Still fresh in R, tried to figure this out, now on my second day running with no luck (and a pile of hair on my desk) so
I have thrown in the towel and would like to ask for some help.
Here is what I am trying to do. I am trying to plot a distribution, I have 99 points, bound in the range
xlim.min: -0.0173
xlim.max: 0.02103
However, I have a value outside this range (0.2454959) which I
2009 Feb 08
0
Initial values of the parameters of a garch-Model
Dear all,
I'm using R 2.8.1 under Windows Vista on a dual core 2,4 GhZ with 4 GB
of RAM.
I'm trying to reproduce a result out of "Analysis of Financial Time
Series" by Ruey Tsay.
In R I'm using the fGarch library.
After fitting a ar(3)-garch(1,1)-model
> model<-garchFit(~arma(3,0)+garch(1,1), analyse)
I'm saving the results via
> result<-model
2014 Aug 15
2
[PATCH net-next] vhost_net: stop rx net polling when possible
After rx vq was enabled, we never stop polling its socket. This is sub optimal
when may lead unnecessary wake-ups after the rx net work has already been
queued. This could be optimized by stopping polling the rx net sock when
processing both rx and tx and restart it afterward. This could save unnecessary
wake-ups and even unnecessary spin locks acquiring with the help of commit
2014 Aug 15
2
[PATCH net-next] vhost_net: stop rx net polling when possible
After rx vq was enabled, we never stop polling its socket. This is sub optimal
when may lead unnecessary wake-ups after the rx net work has already been
queued. This could be optimized by stopping polling the rx net sock when
processing both rx and tx and restart it afterward. This could save unnecessary
wake-ups and even unnecessary spin locks acquiring with the help of commit
2011 Jul 24
2
[LLVMdev] [llvm-testresults] bwilson__llvm-gcc_PROD__i386 nightly tester results
A big compile time regression. Any ideas?
Ciao, Duncan.
On 22/07/11 19:13, llvm-testresults at cs.uiuc.edu wrote:
>
> bwilson__llvm-gcc_PROD__i386 nightly tester results
>
> URL http://llvm.org/perf/db_default/simple/nts/253/
> Nickname bwilson__llvm-gcc_PROD__i386:4
> Name curlew.apple.com
>
> Run ID Order Start Time End Time
> Current 253 0 2011-07-22 16:22:04
2014 Aug 17
0
[PATCH net-next] vhost_net: stop rx net polling when possible
On Fri, Aug 15, 2014 at 11:40:08AM +0800, Jason Wang wrote:
> After rx vq was enabled, we never stop polling its socket. This is sub optimal
> when may lead unnecessary wake-ups after the rx net work has already been
> queued. This could be optimized by stopping polling the rx net sock when
> processing both rx and tx and restart it afterward. This could save unnecessary
> wake-ups
2007 Sep 18
0
[LLVMdev] 2.1 Pre-Release Available (testers needed)
On Fri, Sep 14, 2007 at 11:42:18PM -0700, Tanya Lattner wrote:
> The 2.1 pre-release (version 1) is available for testing:
> http://llvm.org/prereleases/2.1/version1/
>
> [...]
>
> 2) Download llvm-2.1, llvm-test-2.1, and the llvm-gcc4.0 source.
> Compile everything. Run "make check" and the full llvm-test suite
> (make TEST=nightly report).
>
> Send
2011 Jul 24
0
[LLVMdev] [llvm-testresults] bwilson__llvm-gcc_PROD__i386 nightly tester results
On Jul 24, 2011, at 3:02 AM, Duncan Sands wrote:
> A big compile time regression. Any ideas?
>
> Ciao, Duncan.
False alarm. For some reason that I have not yet been able to figure out, these tests run significantly more slowly when I run them during the daytime, which I did for that run. I checked a few of the worst regressions reported here and they all recovered in subsequent
2000 Apr 30
0
Help Need with aov()
Hi there,
I'm using R1.0.1 Windows 98.
This file contains some inputs and an aov function code. Can someone
check it for me? Somehow I got completely different answer when typing
them in R and in Splus.
Splus gives me this:
> summary( Turnip.aov )
Error: Blocks
Df Sum of Sq Mean Sq F Value Pr(F)
Residuals 3 163.7367 54.57891
Error: Plots %in% Blocks
2008 Mar 10
1
ML Estimation Differences with R and SAS
List,
I'm working on fitting a logistic model for a well known dataset (which is
given below in case anyone wants to try to reproduce). I used both R and
SAS to fit the model and have some differences in the parameter estimates.
I'm wondering if R calculates the ML estimates differently. I'm making NO
accusations as to which program is "right or wrong". That is not the
2008 Jul 23
14
[Bug 16815] New: losing fonts in gnome-terminal and other font weirdnesses
http://bugs.freedesktop.org/show_bug.cgi?id=16815
Summary: losing fonts in gnome-terminal and other font
weirdnesses
Product: xorg
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at
2012 Nov 23
2
[LLVMdev] [cfe-dev] costing optimisations
On 23.11.2012, at 15:12, john skaller <skaller at users.sourceforge.net> wrote:
>
> On 23/11/2012, at 5:46 PM, Sean Silva wrote:
>
>> Adding LLVMdev, since this is intimately related to the optimization passes.
>>
>>> I think this is roughly because some function level optimisations are
>>> worse than O(N) in the number of instructions.
>>
2007 Sep 15
22
[LLVMdev] 2.1 Pre-Release Available (testers needed)
LLVMers,
The 2.1 pre-release (version 1) is available for testing:
http://llvm.org/prereleases/2.1/version1/
I'm looking for members of the LLVM community to test the 2.1
release. There are 2 ways you can help:
1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0
binary. Run "make check" and the full llvm-test suite (make
TEST=nightly report).
2) Download
2008 Feb 03
0
[LLVMdev] 2.2 Prerelease available for testing
Target: FreeBSD 6.2-STABLE on i386
autoconf says:
configure:2122: checking build system type
configure:2140: result: i386-unknown-freebsd6.2
[...]
configure:2721: gcc -v >&5
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.4.6 [FreeBSD] 20060305
[...]
objdir != srcdir, for both llvm and gcc.
Release build.
llvm-gcc 4.2 from source.
2008 Jan 24
6
[LLVMdev] 2.2 Prerelease available for testing
LLVMers,
The 2.2 prerelease is now available for testing:
http://llvm.org/prereleases/2.2/
If anyone can help test this release, I ask that you do the following:
1) Build llvm and llvm-gcc (or use a binary). You may build release
(default) or debug. You may pick llvm-gcc-4.0, llvm-gcc-4.2, or both.
2) Run 'make check'.
3) In llvm-test, run 'make TEST=nightly report'.
4) When
2008 Jan 28
0
[LLVMdev] 2.2 Prerelease available for testing
Target: FreeBSD 7.0-RC1 on amd64.
autoconf says:
configure:2122: checking build system type
configure:2140: result: x86_64-unknown-freebsd7.0
[...]
configure:2721: gcc -v >&5
Using built-in specs.
Target: amd64-undermydesk-freebsd
Configured with: FreeBSD/amd64 system compiler
Thread model: posix
gcc version 4.2.1 20070719 [FreeBSD]
[...]
objdir != srcdir, for both llvm and gcc.
Release
2005 Jul 20
1
MMX IDCT for theora-exp
Hello,
I'm attaching IDCT MMX patch. I reused IDCT from theora-a3-MMXd.zip.
It should work on 64bit X86 platform too.
Here is most used functions when playing video with jet aircrafts (gripen)
Ogg logical stream 310b2968 is Theora 720x480 29.97 fps video
Encoded frame content is 720x480 with 0x0 offset
I can play this video with like 200-300 frame drops on Athlon XP 1700+
CPU load (with
2015 Feb 26
5
[LLVMdev] [RFC] AArch64: Should we disable GlobalMerge?
Hi all,
I've started looking at the GlobalMerge pass, enabled by default on
ARM and AArch64. I think we should reconsider that, at least for
AArch64.
As is, the pass just merges all globals together, in groups of 4KB
(AArch64, 128B on ARM).
At the time it was enabled, the general thinking was "it's almost
free, it doesn't affect performance much, we might as well use it".