similar to: Problem applying "outer" to a list of functions

Displaying 20 results from an estimated 10000 matches similar to: "Problem applying "outer" to a list of functions"

2016 Aug 08
2
Trouble applying regex to dialplan variable that contains double-quotes
I am writing a dialplan context under asterisk 11.21.0 to handle SIP message routing between registered SIP peers using chan_sip. I am having trouble with double-quotes when the source peer uses a display name, which appears in quotes before the SIP URI. I want to extract the SIP URI from MESSAGE(from) in order to (conditionally) route a failure message back to the source peer. My test dialplan
2017 Mar 20
0
outer not applying a constant function
>>>>> Gebhardt, Albrecht <Albrecht.Gebhardt at aau.at> >>>>> on Sun, 19 Mar 2017 09:14:56 +0000 writes: > Hi, > the function outer can not apply a constant function as in the last line of the following example: >> xg <- 1:4 >> yg <- 1:4 >> fxyg <- outer(xg, yg, function(x,y) x*y) >> fconstg
2017 Nov 15
1
[nbdkit PATCH] connections: Extract common export flag computation code
No need to duplicate maintenance of export flag computation between old and new style handshakes. Signed-off-by: Eric Blake <eblake@redhat.com> --- src/connections.c | 120 +++++++++++++++++++++--------------------------------- 1 file changed, 47 insertions(+), 73 deletions(-) diff --git a/src/connections.c b/src/connections.c index 8dc1925..f9edea7 100644 --- a/src/connections.c +++
2017 Mar 20
1
outer not applying a constant function
> Or is this a bad idea? I don't like the proposal. I have seen code like the following (in fact, I have written such code, where I had forgotten a function was not vectorized) where the error would have been discovered much later if outer() didn't catch it. > outer(1:3, 11:13, sum) Error in outer(1:3, 11:13, sum) : dims [product 9] do not match the length of object [1]
2017 Mar 19
2
outer not applying a constant function
Hi, the function outer can not apply a constant function as in the last line of the following example: > xg <- 1:4 > yg <- 1:4 > fxyg <- outer(xg, yg, function(x,y) x*y) > fconstg <- outer(xg, yg, function(x,y) 1.0) Error in outer(xg, yg, function(x, y) 1) : dims [product 16] do not match the length of object [1] Of course there are simpler ways to construct a constant
2000 Sep 02
1
[2.2.0p1] patch to get "scp -S prog" to work right + man page fix
Hi. This functionality was just added in 2.2.0p1. The patch is self-explanatory. Charles --- scp.c.orig-2.2.0p1 Tue Aug 29 19:11:30 2000 +++ scp.c Sat Sep 2 15:14:58 2000 @@ -262,7 +262,7 @@ extern int optind; fflag = tflag = 0; - while ((ch = getopt(argc, argv, "dfprtvBCc:i:P:q46S")) != EOF) + while ((ch = getopt(argc, argv, "dfprtvBCc:i:P:q46S:")) != EOF)
2012 Apr 20
1
predictOMatic for regression. Please try and advise me
I'm pasting below a working R file featuring a function I'd like to polish up. I'm teaching regression this semester and every time I come to something that is very difficult to explain in class, I try to simplify it by writing an R function (eventually into my package "rockchalk"). Students have a difficult time with predict and newdata objects, so right now I'm
2016 Sep 26
1
[PATCH] nbdkit: flags are 32 bits for oldstyle connections
# HG changeset patch # User Carl-Daniel Hailfinger <Carl-Daniel.Hailfinger@inf.h-brs.de> # Date 1474903734 -7200 # Mon Sep 26 17:28:54 2016 +0200 # Node ID dbd1ea0a401cedcfa426097a289d852971b14f1e # Parent d7d5078d08c711032837dcac79a4450226ec2ce5 nbdkit: Fix flags in old-style connection diff -r d7d5078d08c7 -r dbd1ea0a401c src/connections.c --- a/src/connections.c Sun Sep 25 05:04:02
2018 Jan 29
2
opus manpages
Dear authors of Opus, currently, the manpages that come with opus-tools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on the
2018 May 18
3
exclude
Hi All, I have a sample of data set show as below. tdat <- read.table(textConnection("stat year Y AL 2003 25 AL 2003 13 AL 2004 21 AL 2006 20 AL 2007 12 AL 2009 16 AL 2010 15 FL 2006 63 FL 2007 14 FL 2007 25 FL 2009 64 FL 2009 47 FL 2010 48 NY 2003 50 NY 2004 51 NY 2006 57 NY 2007 62 NY 2007 36 NY 2009 87 NY 2009 96 NY 2010
2008 Mar 08
1
ks.test troubles
Hi there! I have two little different data. One is a computer test on people, the other is a paper and pencil test. two boxplots show me that the data is almost the same. So now I'd like to know if I could handle all data as one, by testing with ks.test: ==== > ks.test(el$angststoer, fl$angststoer) Two-sample Kolmogorov-Smirnov test data: el$angststoer and fl$angststoer D =
2000 Dec 21
1
Patch to allow DSA as well as RSA identities to be specified on the command line
This patch allows DSA identities to be specified on the command line. Previously, only RSA identities were allowed. ------------------------------------------------------------------------ diff -U2 openssh-2.2.0p1/ssh.0 openssh-2.2.0p1.nigelw/ssh.0 --- openssh-2.2.0p1/ssh.0 Sat Sep 2 10:08:46 2000 +++ openssh-2.2.0p1.nigelw/ssh.0 Thu Dec 21 10:53:07 2000 @@ -224,5 +224,5 @@ -g Allows
2013 Jan 02
4
Define 6.1 and 7.1 channel mappings
I apologize for the terribly long message, but here goes. ------------------------------------------------------------------------------------------------- First, regarding existing tools that I now about. libavcodec and users (e.g. HandBrake): - if there are 6 channels or less, the layout is set by the decoder as per the FLAC specification - if there are more than 6 channels, the layout is
2022 Dec 31
1
rewrite manpages to mdoc(7)
Dear authors of NSD, currently, the manpages that come with NSD are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. See a version of nsd-checkzone.8 below as an example. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters:
2001 Sep 13
4
ssh argv[0] support
Right - I know you've had a discussion about the argv[0] stuff already, but I've written this simple script to simulate the (now missing) support for Debian, and was asked to send it to you... --- ssh-argv0 --- #! /bin/sh -e if [ "${0##*/}" == "ssh-argv0" ] then echo 'ssh-argv0: This script should not be run like this, see ssh-argv0(1) for details'
2018 May 18
0
exclude
... and similar to Jim's suggestion but perhaps slightly simpler (or not!): > cross <- xtabs( Y ~ stat + year, data = tdat) > keep <- apply(cross, 1, all) > keep <- names(keep)[keep] > cross[keep,] year stat 2003 2004 2006 2007 2009 2010 AL 38 21 20 12 16 15 NY 50 51 57 98 183 230 > ## for counts just do: > xtabs( ~ stat + year, data
2023 Oct 18
1
Linux/Windows Domain Controller
Yes I've red this section and the docu is saying no FL above 2008. Might be caused by incompleted docu? So far I understand if we don't use >4.19 we will not be able to use FL 2016 which is necessary since our DC WIN22 is configured as FL2016? On 18.10.23 19:10, Stefan Kania via samba wrote: > If you take a look at: > >
2018 May 18
1
exclude
Thank you Bert and Jim, Jim, FYI , I have an error message generated as Error in allstates : object 'allstates' not found Bert, it is working. However, If I want to chose to include only mos years example, 2003,2004,2007 and continue the analysis as before. Where should I define the years to get as follow. 2003 2004 2007 AL 2 1 1 NY 1 1 2 Thank you
2005 Aug 29
2
Asterisk Compile error - x86_64
Asterisk has this error on compile: flex ast_expr2.fl "ast_expr2.fl", line 50: unrecognized %option: reentrant "ast_expr2.fl", line 51: unrecognized %option: bison-bridge "ast_expr2.fl", line 52: unrecognized %option: bison-locations make: *** [ast_expr2f.c] Error 1 2.6.12-1.1447_FC4smp #1 SMP bison (GNU Bison) 2.0 Written by Robert Corbett and Richard Stallman.
2007 Nov 26
3
Correct syntax for IF()?
Hello I've tried a bunch of things, but still get errors/warnings when using the IF() function: ============== TEST #1 exten => h,n,Set(WAV_FILE=${IF($[ ${STAT(e,/tmp/${CALLTIME}.wav)} ]?${CALLTIME}.wav)}) [Nov 26 21:52:34] WARNING[5074]: func_logic.c:107 acf_if: Syntax IF(<expr>?[<true>][:<false>]) ============== TEST #2 exten =>