search for: evaluating

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>

...ype 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 end end The problem is that when running puppet I get: err: //default/testz/Test[1]: Failed to retrieve current state of resource: undefined method `evaluate'' for []:Array So, what does evaluate suppose to return? -- Dmitri Priimak

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 <- function(x, y=x) { + y <- y + x <- 0 + y + } > fo...

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

...39;m wrong. 1) bar is called. Its evaluation frame contains the association "er=a". 2) bar calls foo. So foo is called, and its evaluation frame contains the association "expr=er", with enclosing environment the local 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 evalu...

...s 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, possibly fatally. I'm looking for general advice about how to cope with NSE in this context. I also have some specific questions: 1) Is it possible to determine whether a given function (primitive, in R, or external) uses NSE on...

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

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

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

...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 evaluating weighting schemes in Xapian :) Comparing the MAP to access the retrieval effectiveness, some interesting results have emerged as follows: 1. BM25+ : 0.100415 and BM25: 0.101771 BM25 does a slightly better job here. My guess is that BM25+ is falling short because may be we lack very long document...

...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 failing? 2. Is this a bug, or an accepted behavior 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...

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

Hi friends, Please help me with this bug. *Bug in my code:* In this variable sub_grp_whr_cls_data[sbgrp_no,1] I store the where clause.every sub group has a where 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" ||

...is R not "clever" enough to detect this as a special case, but instead goes ahead and tries to evaluate the default expression (=dim(x)) of argument 'dim' in order to get its default value? If so, is there anything preventing R from support this "special case", e.g. by evaluating the default expression without argument/symbol 'dim' itself being in the picture to avoid "it finds itself"? (Sorry if I'm using the incorrect words here). Yes, I understand that I can do: > foo <- function(x, dim=base::dim(x)) { dim } > foo(1) NULL > foo <...

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/