search for: outvar

...eq(Lower[j], Upper[j])] <- i }} testRow$reduced <- paste(Text[!is.na(Keep)], collapse=" ") } testRow length(Text) length(Text[!is.na(Keep)]) #### Function for selecting words within specified range of a target term #### nearTerms <- function(df, text, target, before, after, outvar){ Text <- with(df, strsplit(text, " ")) Target <- grep(target, Text) if (length(Target) == 0) {df$reduced <- ""} else{ Length <- length(Text) Keep <- rep(NA, Length) Lower <- ifelse(Target - before > 0, Target - before, 1) Upper &lt...

...ist, I am trying to plot the local variance in a moving window on a dataset. The function that I am trying to use for this is wapply from gtools. However, from the lattice panel function code: <snip> cat(x) cat(y) wapply(x,y,method="range",width=1/10,fun=sd,na.rm=TRUE) -> outvar </snip> I get: <snip> 109 109 109 109 109 109 116 116 116 116 119 119 123 123 123 123 127 127 133 133 133 133 133 138 138 138 138 138 138 138 138138 138 138 142 142 142 142 142 142 142 147 147 147 147 147 158 158 158 158 158 158 158 158 158 158 158 158 158 20.234 28.431 10.762 45.613...

On Tue, Jan 27, 2015 at 10:02 AM, Mueller-Roemer, Johannes Sebastian <Johannes.Sebastian.Mueller-Roemer at igd.fraunhofer.de> wrote: > Adding -D__MSVCRT_VERSION__=0x900 (or higher) to CMAKE_CXX_FLAGS and > -lmsvcr90 (or higher) to CMAKE_CXX_STANDARD_LIBRARIES appears to work. > -lmsvcrt80 does not work, contrary to the comment on the MinGW bug tracker. > However, if you do not

...eck expressions [2]. I'm not particularly happy with this syntax since it is quite verbose (but then again we don't need it that often so it doesn't really matter). It also doesn't allow saving the expression result so it needs to be repeated everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't really had the need for that yet. > > We currently need the following two features: > > - Simple arithmetic with multiple operations. Example: > `cld $gp, $zero, [[@EXPR 2 * $CAP_SIZE - 8]]($c11)` > > - Conversion to hex (upper and lower case sinc...

...eck expressions [2]. I'm not particularly happy with this syntax since it is quite verbose (but then again we don't need it that often so it doesn't really matter). It also doesn't allow saving the expression result so it needs to be repeated everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't really had the need for that yet. >> > >> > We currently need the following two features: >> > >> > - Simple arithmetic with multiple operations. Example: >> > `cld $gp, $zero, [[@EXPR 2 * $CAP_SIZE - 8]]($c11)` >> &g...

To be clear, I do not intend to add support for hex specifier in the current patch, I just want to make sure the syntax we choose is going to allow it later. My immediate use case is decimal integer and I intend to write the code so that it's easy to extend to more type of numeric variables and expressions later. This way we'll only add specifier that are actually required by actual

...eck expressions [2]. I'm not particularly happy with this syntax since it is quite verbose (but then again we don't need it that often so it doesn't really matter). It also doesn't allow saving the expression result so it needs to be repeated everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't really had the need for that yet. >> >> > >> >> > We currently need the following two features: >> >> > >> >> > - Simple arithmetic with multiple operations. Example: >> >> > `cld $gp, $zero, [...

...eck expressions [2]. I'm not particularly happy with this syntax since it is quite verbose (but then again we don't need it that often so it doesn't really matter). It also doesn't allow saving the expression result so it needs to be repeated everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't really had the need for that yet. >> >> > >> >> > We currently need the following two features: >> >> > >> >> > - Simple arithmetic with multiple operations. Example: >> >> > `cld $gp, $zero, [...

...; not particularly happy with this syntax since it is quite verbose (but then >> again we don't need it that often so it doesn't really matter). It also >> doesn't allow saving the expression result so it needs to be repeated >> everywhere. I could probably use [[@EXPR:OUTVAR INVAR + 42]] but I haven't >> really had the need for that yet. >> >> >> > >> >> >> > We currently need the following two features: >> >> >> > >> >> >> > - Simple arithmetic with multiple operations. Examp...