search for: _far_

Displaying 13 results from an estimated 13 matches for "_far_".

Did you mean: _far
2004 Mar 31
11
Zero Index Origin?
...ex origin, the ordinality of indexes starts with 0 instead of 1. Is it possible to effect that in R without a lot of difficulty? I come here today from the world of DSP research and development where Matlab has a near hegemony. I see no reason whatsoever that R couldn't replace it with a _far_ better and _far_ less idiosyncratic framework. I'd be interested in working on a Matlab equivalent DSP package for R (if that isn't being done by someone) and one of the things most criticized about Matlab from the standpoint of the DSP programmer is its insistence on 1 origin indexin...
2013 Mar 20
0
[LLVMdev] ARM NEON VMUL.f32 issue
...that shouldn't be expecting values below FLT_MIN, or | * is it a bug in the lowering, that should only be lowering to NEON's VMUL when unsafe-math is on, or | * neither, and people should disable that when they want correctness? Note that if you go for the second option, IMO unsafe-math is _far_ too "aggressive" an option to control this whether multiplies should be allowed produce denormals. I can imagine plenty of cases where I wouldn't care about denormals, but wouldn't want some of the other fast-math semantics applied. Does llvm/clang have any option like strict-iee7...
2011 Feb 11
1
Passing function arguments
Hi All, Im looking for some help passing function arguments and referencing them, I've made a replica, less complicated function to show my problem, and how i've made a work around for this. However i suspect there is a _FAR_ better way of doing this. If i do: BuildDecayModel <- function(x = "this", y = "that", data = model.data) { model <- nls(y ~ SSexp(x, y0, b), data = model.data) return(model) } ... "Error in lm.fit(x, y, offset = offset, singular.ok = singular.ok, ...) : 0 (no...
2013 Mar 19
4
[LLVMdev] ARM NEON VMUL.f32 issue
Hi folks, I just "fixed" a bug on ARM LNT regarding lowering of a VMUL.f32 as NEON and not VFP. The former is not IEEE 754 compliant, while the latter is, and that was failing TSVC. The question is: * is this a problem with the test, that shouldn't be expecting values below FLT_MIN, or * is it a bug in the lowering, that should only be lowering to NEON's VMUL when unsafe-math
2006 Oct 16
3
Why is this happening?
In my IAX config file I have: [general] bindport = 4569 ; Port to bind to (IAX is 4569) bindaddr = 0.0.0.0 ; Address to bind to (all addresses on machine) delayreject=yes disallow=all allow=ulaw allow=gsm jitterbuffer=yes forcejitterbuffer=yes mailboxdetail=yes dropcount=3 minexcessbuffer=80 jittershrinkrate=1 notransfer=yes allanrobertson- 209.23.224.97 (D) 255.255.255.255
2007 Oct 09
1
Echo Problems with IAXy
From what I have found the IAXy doesn't handle echo very well. About half of the analog phones I try on the adapter create an echo on the far end. The person I am talking to can hear themselves. I am using Asterisk 1.4 and have tried it with 1.2 as well with the same results. Is there is anything I can do in Asterisk to help solve the echo problem? Thanks, Sean Dennis
2010 Nov 09
1
randomForest parameters for image classification
I am implementing an image classification algorithm using the randomForest package. The training data consists of 31000+ training cases over 26 variables, plus one factor predictor variable (the training class). The main issue I am encountering is very low overall classification accuracy (a lot of confusion between classes). However, I know from other classifications (including a regular decision
2010 Jul 13
4
SIGWINCH
Hi, I followed the procedure to replace a running unicorn. Works fine, except for one thing: after I decide to back out, ie I send a HUP to the old master followed by a QUIT to the new master, then: 1. the new master does die, and the old master does work again 2. the "old" master keeps running with a process name of "master (old)" 3. the "old" master keeps
2006 Jun 08
3
Re-binning histogram data
Hi, Short Version: Is there a function to re-bin a histogram to new, broader bins? Long version: I'm trying to create a histogram, however my input-data is itself in the form of a fine-grained histogram, i.e. numbers of counts in regular one-second bins. I want to produce a histogram of, say, 10-minute bins (though possibly irregular bins also). I suppose I could re-create a data set as
2007 Aug 20
3
[PATCH 2/4] Introduce a new fields "gtime" and "cgtime" in task_struct and signal_struct
[PATCH 2/4] like for cpustat, introduce the "gtime" (guest time of the task= ) and "cgtime" (guest time of the task children) fields for the tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to dis= play these new fields. Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net> -- = ------------- Laurent.Vivier@bull.net --------------
2007 Aug 20
3
[PATCH 2/4] Introduce a new fields "gtime" and "cgtime" in task_struct and signal_struct
[PATCH 2/4] like for cpustat, introduce the "gtime" (guest time of the task= ) and "cgtime" (guest time of the task children) fields for the tasks. Modify signal_struct and task_struct. Modify /proc/<pid>/stat to dis= play these new fields. Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net> -- = ------------- Laurent.Vivier@bull.net --------------
2019 Oct 01
2
Adding support for vscale
On Tue, Oct 1, 2019 at 11:08 AM Graham Hunter <Graham.Hunter at arm.com> wrote: > Hi Luke, hi graham, thanks for responding in such an informative fashion. > > On 1 Oct 2019, at 09:21, Luke Kenneth Casson Leighton via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > typedef vec4 float[4]; // SEW=32,LMUL=4 probably > > static vec4 globalvec[1024]; // vscale ==
2013 Jun 13
43
[Hackathon Minutes] Xen 4.4 Planning
This took me a while to post, but given that we are not starting 4.4 just yet, this may be appropriate now. I may have misrepresented some stuff as it has been 4 weeks since I wrote these. Cheers Lars = Purpose of Roadmap = * Set a vision for interesting features * Track items * Help consumers of Xen with their planning = Release Models that work well = There was a brief discussion on two