search for: evaluates

Hi, I have a rather complex xml document that I am attempting to parse based on attributes: <Manifest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <!-- eName : name of the element. eValue : value of the element. --> <OutputFilePath>D:\CN_data\Agilent\Results\</OutputFilePath> <FilesList> <File>

Hi. I have a small problem with the custom type I am working on. I define method ''evaluate'' which is called after all data is been collected. Here it is: module Puppet newtype(:test) do newparam(:name) do end newparam(:listen) do defaultto "silent" end def evaluate puts "evaluating..." return super.evaluate end

Hi. On 12/30/06, Bhanu Kalyan.K <kalyansikha at yahoo.com> wrote: > Dear Mr.Bengtsson, > > The steps you have suggested are working for single lines of matlab > statements. But, as i mentioned earlier, If i want to see the output of an > entire matlab code (say swissroll.m) then you suggested me to do > res <- evaluate(matlab, "swissroll"). > When i did

Hello, struggling with the very basic needs... :( any help appreciated. #using the package doBY #who drinks how much beer per day and therefor cannot calculate rowise maxvals evaluation=data.frame(date=c(1,2,3,4,5,6,7,8,9), name=c("Michael","Steve","Bob", "Michael","Steve","Bob","Michael","Steve","Bob"),

Hello, and sorry if this is already explained somewhere. I couldn't find anything. R (2.3.1, Windows) seems to perform some kind of lazy evaluation when evaluating defaults in function calls that, at least for me, leads to unexpected results. Consider the following, seemingly equivalent functions: > foo1 <- function(x, y=x) { + x <- 0 + y + } > foo1(1) [1] 0 > foo2

Hi all, I am using R-3.0.1 under Linux platform to embed R into my C++ code. I am facing an error while executing more than 1 R-expressions parallelly. I am executing round(X) and abs(X) parallelly on a set of 50 input rows which resulted in segmentation fault after getting the following errors. Error: unprotect_ptr: pointer not found Error: argument to 'findVar' is not an environment

I ran into a problem recently trying to update a package which uses S4 methods using a recent beta of R. I think I can reproduce it with a simple example. I have package called `testpkg' in directory testpkg/. In the R/ subdirectory of testpkg/ I have a file called testpkg.R which contains the following two lines: setClass("testpkg", representation(pts = "list"))

After many hours of debugging code, I came to the conclusion that I have a fundamental misunderstanding regarding eval, and hope that someone here can explain to me, why the following code acts as it does: foo <- function(expr) { eval(substitute(expr), envir=list(a=5), enclos=parent.frame()) } bar <- function(er) { foo(er) } > foo(a) [1] 5 > bar(a) Error in eval(expr,

Hello R experts, I plan to develop a tool for dynamic analysis of R programs. I would like to trace function calls at runtime, capturing argument and return values. Following a suggestion made some time ago on this list, my high-level implementation strategy is to rewrite the AST, augmenting call expressions with pre-call and post-call shims to capture the arguments and return value,

Dear R Help folks -- I have been trying to put together a list of the steps or stages of R function evaluation, with particular focus on those that have "standard" or "nonstandard" forms. This is both for my own edification and also because I am thinking of joining the world of R bloggers and have been trying to put together some draft posting that might be useful. I seem to

...9.33) Hi, I like to use optimize() to optimize functions whose evaluation is costly in terms of computation time. The Brent algorithm which is implemented in optimize was designed to optimize a function with as few function evaluations as possible. Therefore it bothers me that optimize() always evaluates the function twice at the optimal value. This can be seen for example by saying: square <- function(x) { print(x) x*x } opt <- optimize(square, c(-5,1), tol=0.1) Looking at the code of optimize(), I see that the extra function evaluation comes when optimize returns list(minimum = val,...

I'm not sure if this is a known peculiarity or a bug, but I stumbled across what I think is very odd behavior from delayedAssign. In the below example x switches values the first two times it is evaluated. > delayedAssign("x", {x <- 2; x+3}) > x==x [1] FALSE > delayedAssign("x", {x <- 2; x+3}) > x [1] 5 > x [1] 2 The ?delayedAssign documentation says

Hi everybody, I'm mirroring some websites with rsync (daemon on the source), and I noticed in the destination host some error messages 'send_files failed to open filenames', Actually, the concerned files are deleted on the source host, but I would like to ask : * why does rsync say these (in which phase) ? * is these messages harmful or not ? Here below my rsync command and some

Hi all, I have evaluated new weighting schemes along with their existing counterparts in Xapian to compare and see which one does better job. Also, I have put together all the results files for easy access here: https://github.com/ivmarkp/xapian-evaluation/tree/evaluation/run and a README for getting started with xapian-evaluation module. Hopefully, it might be of help to those who are new to

Hi - I?m running the OpenSCAP STIG profile on a new CentOS 7.1611 installation, and I get a few failures that look like this (output from openscap scan ?verbosity INFO). I suspect this is because the openscap module is not accepting CentOS 7 as RHEL 7 for rules purposes, despite an early check for "Community Enterprise Operating System 7? which succeeds. 1. Am I correct in why it?s

Full_Name: W.B.Kloke Version: 1.8.0 OS: FreeBSD-4.7 Submission from: (NULL) (195.253.22.63) I found a parameter evaluation inconsistency in NLME package. I tried to use gls() inside a function, and I wanted use gls() for different subsets of a data frame: prgls <- function(name){ gls( log10(Y)~(cond-1)+(cond-1):t ,pr,subset=subject==name)} Applying this function with a string as parameter

..._grp_whr_cls_data[sbgrp_no,1]=="") evaluated to FALSE So if (sub_grp_whr_cls_data[sbgrp_no,1]=="NULL" ||sub_grp_whr_cls_data[sbgrp_no,1]=="") is If (FALSE) ,control goes to the else part. This is exactly what is expected of the program. *QUERY:-- **If the condition evaluates to FALSE when a where condition is available why doesn’t it evaluate to TRUE when a where condition available is NULL or no where condition is available.* Here I have taken the example of two databases where I tried to get the where clause for subgroup 1.In case of Database1 it was not available...

I've meant to ask the following for several years now. I understand why: > foo <- function(x, dim=dim) { dim } > foo(1) Error in foo(1) : promise already under evaluation: recursive default argument reference or earlier problems? gives an error, but why wouldn't/couldn't the following work? > foo <- function(x, dim=dim(x)) { dim } > foo(1) Error in foo(1) :

Hi, I have the following on a view <% for evaluation in @evaluations %> <td><%=h evaluation[0].name %></td> <td><%=evaluation[1].object_id %></td> <td><%= link_to( "Start", :action =>''evaluatie'', :id => evaluation[1].object_id) %></td> <%end%> When I click on the link, I can see that

Hello all, We''re using Puppet/Puppetmaster 2.6.4 (2.6.4-2ubuntu2 on Ubuntu 11.04 to be precise), and after enabling pluginsync on the agents to make our custom facts available, all puppet runs start with the output: info: Retrieving plugin err: /File[/var/lib/puppet/lib/puppet/parser/functions/basename.rb]: Could not evaluate: Not a directory - /var/lib/puppet/lib/puppet/