search for: evaluated

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

...t; entire matlab code (say swissroll.m) then you suggested me to do > res <- evaluate(matlab, "swissroll"). > When i did this the output looks something like: > > > res <- evaluate(matlab, "swissroll") > > Sending expression on the Matlab server to be evaluated...: 'swissroll' > Received an 'MatlabException' reply (-1) from the Matlab server: 'Undefined > function or variable 'lle'.' > Error in list("evaluate(matlab, "swissroll")" = <environment>, > "evaluate.Matlab(matlab, &quot...

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"),

...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 <- function(x, y=x) { + y <- y + x <- 0 + y + } > foo2(1) [1] 1 Obviously, y is not evaluated until it is used in some way. I would expect it to be evaluated where it is defined. Is this intended behavior? Thanks for clarifying, Uli

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"))

...al environment of bar. 3) foo calls eval. 4) eval starts by evaluating "substitute(expr)" in foo's environment. "substitute" then locates expr in foo's environment, and replaces it with er. So the result of this process is the symbol er, which is what will now be evaluated by eval. 5) eval then creates the environment where this evaluation will take place. It does that by creating an environment containing the frame "a=5", and with enclosing environment the parent frame of foo, which is bar's environment. 6) So, as I understand it, the symbol &quo...

...pre-call and post-call shims to capture the arguments and return value, respectively. I can think of only one fundamental conceptual obstacle to this approach: R functions are not necessarily referentially transparent. The arguments received by a function are not values but promises. They can be evaluated directly ("standard evaluation"), after applying arbitrary syntactic transformations ("non-standard evaluation", aka NSE), or not at all. Therefore, if you peek at the values of function arguments before evaluating the function, you risk altering the semantics of the program, po...

...gned a logical vector showing the ways that it is and is not standard. One thing I think is conceptually or procedurally difficult about this project is that I think ?standardness? should be determined by what a function does, rather than by how it does it, so that a primitive function that takes unevaluated arguments positionally could still have standard matching, scoping, etc., by internal emulation. A related goal is to identify which evaluation steps most often use an alternative form, and perhaps determine if there is more than one such alternative. Finally, an easier short-term goal is simply to...

Full_Name: Jelle Goeman Version: 2.4.0 OS: windows XP Submission from: (NULL) (145.88.209.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

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 that "after [evaluation], the value is fixed and the expression will not be evaluated again." How...

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-ev...

...vior given that CentOS isn?t actually RHEL? Noam I: oscap: Evaluating XCCDF rule 'accounts_password_pam_retry'. I: oscap: Evaluating definition 'oval:org.open-scap.cpe.rhel:def:7': Red Hat Enterprise Linux 7. I: oscap: Definition 'oval:org.open-scap.cpe.rhel:def:7' evaluated as false. I: oscap: Evaluating definition 'oval:org.open-scap.cpe.rhel:def:1007': Community Enterprise Operating System 7. I: oscap: Definition 'oval:org.open-scap.cpe.rhel:def:1007' evaluated as true. I: oscap: Adding external variable oval:ssg-var_password_pam_retry:var:1. I: osca...

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

...condition linked with it. Database1 Where clause was not found for a particular subgroup, sub_grp_whr_cls_data[sbgrp_no,1] value was NULL So the condition (*sub_grp_whr_cls_data[sbgrp_no,1]=="NULL" || sub_grp_whr_cls_data[sbgrp_no,1]==""*) should evaluate to TRUE ,but it evaluated to NA So the if block where I used the the condition threw error If(*sub_grp_whr_cls_data[sbgrp_no,1]=="NULL" || sub_grp_whr_cls_data[sbgrp_no,1]==""*) i.e if(NA) Error:-- Error in if (sub_grp_whr_cls_data[sbgrp_no, 1] == "NULL" || sub_grp_whr_cls_data[sbgrp_no,...

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/