Displaying 20 results from an estimated 12224 matches for "equalize".
Did you mean:
equalizer
2013 Apr 16
1
testInstalledBasic / testInstalledPackages
Hi,
I installed R 3.0.0 on a Windows 2008 Server.
When I submitted the following code in R64,
library(tools)
testInstalledBasic(scope="devel")
I get the following message in the R Console:
> library(tools)
> testInstalledBasic(scope="devel")
running tests of consistency of as/is.*
creating ?isas-tests.R?
running code in ?isas-tests.R?
comparing ?isas-tests.Rout? to
2014 Sep 21
1
Bug in new behaviour for all.equal and environments?
Hi R-devel,
The following code:
all.equal(baseenv(), baseenv())
gives the error when run in a clean R session with latest R-devel (r66650):
kevin:~$ R --vanilla --slave -e "all.equal(baseenv(), baseenv())"
Error in all.equal.envRefClass(target[[i]], current[[i]],
check.attributes = check.attributes, :
attempt to apply non-function
Calls: all.equal ...
2009 Mar 09
10
Cucumber - RSpec matcher
I must be missing something obvious here but I cannot seem to see it.
I have this step definition:
When /entity named "(.*)" has a legal name "(.*)"/ do |name, legal|
myentity = Entity.find_by_entity_common_name!(name.hll_keycase)
myentity.entity_legal_name.should equal legal.hll_keycase
end
Which fails with this:
And the entity named "Myuser" has a legal
2005 Jun 26
2
is.all.equal
Hi,
The description of all.equal states "is.all.equal should be used for
programming, typically in if expressions. It is a simple wrapper using
identical as shown in the documentation there.", but is.all.equal is
not explicitly defined there (although there is a hint in the comments
that is.all.equal <- function(x,y) isTRUE(all.equal(x,y))).
Could the documentation be corrected? (or
1998 May 14
0
all.equal - cut two, test.equal
Below is a second cut at all.equal and also a generic function test.equal which
is intended to return a T/F value. The default method uses all.equal, which is
the reason I was looking for all.equal in the first place. Prompted by Thomas
Lumley's observation that a T/F result makes more sense I thought it would be
worthwhile to indicate what I'm really doing.
I have been using test.equal
2008 Nov 09
1
attr.all.equal() and all.equal(attributes(), attributes())
Dear All!
If I try to compare the attributes of two
objects, I find a surprising behaviour of
attr.all.equal(). With identical attributes I
receive the answert NULL. If the attributes
differ, the answer is as expecxted and differences are shown.
all.equal(attributes(), attributes()) instead
returns TRUE, if attributes are equal.
See example:
v <- 1:5
attr(v, 'testattribute')
2019 Apr 05
6
all.equal failure
This arose in testing [.terms and has me confused.
data(esoph)?? # use a standard data set
t0x <- terms(model.frame( ~ tobgp, data=esoph))
t1 <-? terms(model.frame(ncases ~ agegp + tobgp, data=esoph))
t1x <- (delete.response(t1))[-1]
> all.equal(t0x, t1x)
[1] TRUE
# the above is wrong, because they actually are not the same
> all.equal(attr(t0x, 'dataClasses'),
2004 Dec 27
4
PDC + LDAP
I'm trying to set up my LDAP in preparation to configure my Samba PDC.
In the Official Samba-3 HOWTO and Reference Guide it give instructions
on howto setup slapd.conf (section 10.4.4.3) After modifying the file
it instructs to run /sbin/splapindex -f /splapd.conf When I run this I
get the following error:
/etc/openldap/schema/samba.schema: line 423: AttributeType not found:
2019 Apr 05
3
[EXTERNAL] Re: Re: all.equal failure
>>>>> Duncan Murdoch
>>>>> on Fri, 5 Apr 2019 11:12:48 -0400 writes:
> On 05/04/2019 10:46 a.m., Therneau, Terry M., Ph.D. wrote:
>>
>>
>> On 4/5/19 9:39 AM, Duncan Murdoch wrote:
>>> On 05/04/2019 10:19 a.m., Therneau, Terry M., Ph.D. wrote:
>>>> Duncan,
>>>> ?? I should have
2012 Sep 01
1
Vectorial analogue of all.equal()?
Greetings All.
Once again, I am probably missing something fairly accessible,
but since I can't find it I'd welcome advice!
I have a dataframe derived from a text file of data in tabular
format. For one of the variables, say X, I want to select the
subsets which in which X equals a particular value.
Such values are given in the text file like: 2.3978953, and each
such value will occurr
2005 Oct 09
0
all.equal() improvements (PR#8191)
--k1lZvvs/B4yU6o8G
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
The attached patch against R 2.2.0 makes the following improvements to
the all.equal() function:
1. Check names! Stock R all.equal() (unlike S-Plus) ignores names
completely on some objects. I consider this wrong - if the names
are different, the object is NOT "the same".
2. When a
2011 Nov 24
2
understanding all.equal() output: "Mean relative difference"
Dear all
How should one parse all.equal() output? I'm specifically referring to
the 'mean relative difference' messages. For example,
> all.equal(pi, 355/113)
[1] "Mean relative difference: 8.491368e-08"
But I'm not sure how to understand these messages. When they're close
to 0 (or 1xe-16), then it's intuitive. But when they're big,
> all.equal(1, 4)
2003 May 28
2
Numbers that look equal, should be equal, but if() doesn'tsee as equal (repost with code included)
Try the following function (the name is supposed to be a joke, by the
way),
which will also do the right thing with NAs and characters. Use it as
if(equal.enough(x,y)) rather than if(x==y), e.g.
> equal.enough(0.1+0.2, 0.3)
[1] TRUE
My default of 15 significant figures may be overkill in many
applications; be
prepared to reduce this.
Simon Fear
"equal.enough" <- function(x, y,
2004 Jun 06
2
LDAP authentication problem
Hi
I have a little problem with my ldap authorization of samba against Novel LDAP server.
This is the log output from the Novel Ldap server:
----------------------------------------------------------------------------------------------------
New TCP connection 0xcb1e3980, monitor = 0x1bf, index = 2
(0xcb1e3980:0x0001:0x60) DoBind on connection 0xcb1e3980
(0xcb1e3980:0x0001:0x60) DoBind: name =
2011 Apr 06
4
problem with all/all.equal
Hi!
In a function, I may have an instance in which all elements are equal.
> x <- rep(1,5)
>
> x
[1] 1 1 1 1 1
> identical(x)
Error in .Internal(identical(x, y, num.eq, single.NA, attrib.as.set)) :
'y' is missing
> all.equal(x)
Error in is.expression(x) : 'x' is missing
>
I don't care what particular value it is, I just want to know if they are
all
2004 Oct 01
3
same test statistic for t-test with and without equal variance assumption
Could some kindly tell me if I am supposed to be getting the same test
statistic value with var.equal=TRUE and var.equal=FALSE in t.test ?
set.seed(1066)
x1 <- rnorm(50)
x2 <- rnorm(50)
t.test(x1, x2, var.equal=FALSE)$statistic # 0.5989774
t.test(x1, x2, var.equal=TRUE)$statistic # 0.5989774 ???
Here are my own calculations that shows that perhaps the result when
var.equal=TRUE is
2010 Feb 12
2
[LLVMdev] [PATCH] Fix off-by-one errors in the doxygen documentation
Some doxygen annotations are attached to the wrong entry, which can be
misleading. This patch fixes the mistake everywhere I could find it.
---
include/llvm/InstrTypes.h | 54 ++++++++++++++++++++--------------------
include/llvm/MC/MCDirectives.h | 42 +++++++++++++++---------------
include/llvm/Pass.h | 10 +++---
3 files changed, 53 insertions(+), 53 deletions(-)
diff
1998 May 21
1
all.equal - cut three
Below is a third cut at all.equal and the generic function test.equal which
is intended to return a T/F value. There was a suggestion that "is.equal" rather
than "test.equal" might be considered as a name. I have mixed feelings about
this. I associate the "is" functions with inheritance rather than comparisons,
but the "equal" part of the name makes it
2011 Aug 07
1
all.equal doesn't work for POSIXlt objects
Hi all,
following sample code illustrates the problem :
Date1 <- Date2 <-
as.POSIXlt(seq.Date(as.Date("2010-04-01"),as.Date("2011-04-01"),by='day'))
identical(Date1,Date2)
all.equal(Date1,Date2)
identical() gives the correct answer. As there is no all.equal method
for POSIXlt objects, all.equal.list is used instead. Subsetting using
[[]] doesn't work
2007 Jan 19
2
2.6.17 kernels and equalize patch
...----|Client Router ( Destiantion Net DNET)
|----eth0.41------ | | /27 subnet
------
I just want to balance the load of bandwidth per packet based between the
two vlan interfaces to Client Destination network
What i have done is :
//////////
bash#/sbin/ip route add equalize $DNET scope global nexthop via
$IP1 dev eth0.40 weight 1 nexthop via $IP2 dev eth0.41
weight 1
/////////
bash#ip route show $DNET
$DNET equalize
nexthop via $IP1 dev eth0.40 weight 1
nexthop via $IP2 dev eth0.41 weight 1
But the traffic towards the $DNET does not seem equalized...