search for: parenthet

R-helpers, I have a vector of character strings in which I would like to replace each parenthetical phrase with a single space, " ". For example if I start with x, I would like to end up with y. x <- c("My toast=bog(keep=3 no=4) and eggs(er34)omit=32", "dogs have ears", "cats have tails (and ears, too!)") y <- c("My toast=bog and eggs omi...

> On Sep 4, 2020, at 2:40 PM, Neil Nelson via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> If fptosi takes 0.9 -> 0, then that is not 'rounding' in any sense I'm aware of (IEEE754 or otherwise). >> Rounding (in the IEE754 sense) determines how a number is converted when it is halfway between two >> candidate results. (see round(), ceil(),

Hi WizaRds, In MATLAB you can do x=1:10 and then specify x(2:end) to get 2 3 4 5 6 7 8 9 10 or whatever (note that in MATLAB the parenthetic index notation is used, not brackets as in R). The point is that 'end' allows you to refer to the final index point of the array. Obviously there isn't much gain in syntax when the variable name is x, but when it's something like hereIsABigVariableName(j:end-i) it makes things...

Dear Speex developers, I think I found a typo in libspeex/preprocess.c (that still in the SVN version too). Please correct me if I would be wrong. Patch is attached. (Yours :parenthetically &dezzy) -------------- next part -------------- A non-text attachment was scrubbed... Name: noise_var.patch Type: text/x-patch Size: 518 bytes Desc: not available Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20060805/584ca4d2/noise_var.bin

...> Logical values are sent as 0 (FALSE), 1 (TRUE) or INT_MIN = > > > -2147483648 (NA, but only if NAOK is true), and the compiled code > > > should return one of these three values. (Non-zero values other > > > than INT_MIN are mapped to TRUE.) > > > > The parenthetical seems to suggest that something like 'LOGICAL(x)[0] > > = 2;' will be treated as TRUE, which it sometimes is, and sometimes > > isn't: > > From: Martyn Plummer <plummerm at iarc.fr> > The title of Section 5.2 is "Interface functions .C and .Fortran&...

...he length (as defined in len). > lenplusstate [1] "1:328" "1:154" "4:135" [4] "NA:147" "3:30" "2:50" [7] "NA:252" "NA:45" "NA;" "tree" is a string that gives the specific relationship (via parenthetical notation) among the different items. Note that the lengths are included in this tree (following the colon), and the name of each item (1-5) precedes a colon. However, not every colon is preceded with a name (because there are internal nodes in the tree structure). > tree [1] "(*1*:328,...

Ladies and Gentlemen, As Johan Lindberg points out, the documentation for handling dendrograms is sparse....Does anyone know who is responsible for or working on development of tree methods and objects? I've written a couple of scripts for my own use to translate between parenthetical (A(B(CD))) or binary A00 B10 C11 D11 tree formats and cluster objects in R, but as an inexperienced programmer have had difficulty integrating them with the existing framework--I'm trying to write some resampling routines and sensitivity tests for tree objects. Perhaps this question s...

...han NA, 0, and 1 in LGLSXPs.? I'm thinking of this passage: > Logical values are sent as 0 (FALSE), 1 (TRUE) or INT_MIN = -2147483648 (NA, but only if NAOK is true), and the compiled code should return one of these three values. (Non-zero values other than INT_MIN are mapped to TRUE.) The parenthetical seems to suggest that something like 'LOGICAL(x)[0] = 2;' will be treated as TRUE, which it sometimes is, and sometimes isn't: not.true <- inline::cfunction(body=' ? SEXP res = allocVector(LGLSXP, 1); ? LOGICAL(res)[0] = 2; ? return res;' )() not.true ## [1] TRUE not.tru...

...kages don't work. Page 14 of Writing R Extensions says: "There are optional arguments specified as \link[pkg]{foo} and \link[pkg:bar]{foo} to link to the package pkg with topic (file?) foo and bar respectively." I thought that I understood this passage (with the exception of the parenthetical question, which is in the original text), but, for example, \link[base]{hist} fails to create a link to the documentation for hist in the base package. I've screwed around with this for a while with no success. Any help would be appreciated. Thanks, John ____________________________...

...e with other core functionality. Usage of refObjects as parent.env is also probably precluded in the similar way (don't have a patched R, so can not test yet). Would it be possible, some day, to use refObjects as parent.env or function's environment without "loosing the class"? Parenthetically, the attributes of an object (including S3 classes) are not lost: > env <- structure(new.env(), a1 = "fdsf", class = "old_class") > tf <- function(x)x > environment(tf) <- env > environment(tf) <environment: 056570a0> attr(,"a1") [1] &...

Hi, I'd like to add, say, the sample size for every group in a bwplot as a parenthetical annotation to the axis. Here's a sketch: --8<---------------cut here---------------start------------->8--- require(Hmisc) age <- sample(1:100, 1000, replace = TRUE) sex <- gl(2, 8, 1000, c("Male", "Female")) grp <- gl(4, 6, 1000, letters[1:4]) bwplot(gr...

...gt; and two arm configs enable it at all. > > So, IMHO, /sys/firmware/memmap/ is definitely not the way to go. I think that's a policy decision and policy decisions do not belong in the kernel. Give the tooling the opportunity to decide whether System RAM stays that way over a kexec. The parenthetical reference otherwise looks out of place to me in the /proc/iomem output. What makes it "driver managed" is how the kernel handles it, not how the kernel names it.

...gt; and two arm configs enable it at all. > > So, IMHO, /sys/firmware/memmap/ is definitely not the way to go. I think that's a policy decision and policy decisions do not belong in the kernel. Give the tooling the opportunity to decide whether System RAM stays that way over a kexec. The parenthetical reference otherwise looks out of place to me in the /proc/iomem output. What makes it "driver managed" is how the kernel handles it, not how the kernel names it.

...ata type. Elsewhere, it seems like a data.frame can be a collection of arbitrary variables. 2. environment --------------- Refman p122: "Environments consist of a frame, or collection of named objects, and a pointer to an enclosing environment." Is the "or" here explaining parenthetically that a frame is a collection of named objects, or is separating too alternative structures for an environment? If the former, does this imply that a frame can contain arbitrary variables? And "pointer"? Is that a type of thing in R? 3. R search path; attach() -----------------...

...... CC=gcc CFLAGS=-g -O2 -fPIC -shared The C<CFLAGS> parameter overrides the built-in flags completely. The C<EXTRA_CFLAGS> parameter adds extra flags to the built-in flags. Since we already mention EXTRA_CFLAGS below the example, I'm not sure if my addition of a parenthetical about EXTRA_CFLAGS above is worthwhile, or just adds noise. > diff --git a/configure.ac b/configure.ac > index afc5ddab..e5e261c8 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -820,6 +820,15 @@ AC_ARG_ENABLE([plugins], > [disable all bundled plugi...

Hello, I have a date in the format Year-Month Name (e.g. 1990-January) and R classes it as a character. I want to convert this character into a date format, but when I try as.Date(1990-January, "%Y-%B"), I get back NA. The function strptime also gives me NA back. Thanks. [[alternative HTML version deleted]]

...gt; >>> So, IMHO, /sys/firmware/memmap/ is definitely not the way to go. >> >> I think that's a policy decision and policy decisions do not belong in >> the kernel. Give the tooling the opportunity to decide whether System >> RAM stays that way over a kexec. The parenthetical reference otherwise >> looks out of place to me in the /proc/iomem output. What makes it >> "driver managed" is how the kernel handles it, not how the kernel >> names it. > > At least, virtio-mem is different. It really *has to be handled* by the > driver....

...gt; >>> So, IMHO, /sys/firmware/memmap/ is definitely not the way to go. >> >> I think that's a policy decision and policy decisions do not belong in >> the kernel. Give the tooling the opportunity to decide whether System >> RAM stays that way over a kexec. The parenthetical reference otherwise >> looks out of place to me in the /proc/iomem output. What makes it >> "driver managed" is how the kernel handles it, not how the kernel >> names it. > > At least, virtio-mem is different. It really *has to be handled* by the > driver....

Is there a way to express a multiple pipeline itinerary using the current scheme (maybe some trick with setting NextCycles = 0)? Specifically, consider a case where a floating-point load simultaneously uses units from a floating-point pipeline and a load/store pipeline. Thanks in advance, Hal -- Hal Finkel Postdoctoral Appointee Leadership Computing Facility Argonne National Laboratory

...an R package for "analyses of phylogenetics and evolution". The first version (0.1) has been released on 27 August 2002 and is available on CRAN. >From the 'Description' file of version 0.1: Ape provides functions for reading, and plotting phylogenetic trees in parenthetic format (standard Newick format), analyses of comparative data in a phylogenetic framework, analyses of diversification and macroevolution, computing distances from allelic and nucleotide data, reading nucleotide sequences from GenBank via internet, and several t...