Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.soft-sys.math.mathematica > #15170

Re: inconsistent refinement behavior

From Alex Krasnov <akrasnov@cory.eecs.berkeley.edu>
Newsgroups comp.soft-sys.math.mathematica
Subject Re: inconsistent refinement behavior
Date 2013-07-16 09:53 +0000
Message-ID <ks357b$755$1@smc.vnet.net> (permalink)
References <20130714054806.AEA91636F@smc.vnet.net>
Organization Time-Warner Telecom

Show all headers | View raw


Refine treats Reals as a subset of Complexes, as expected:

In:	Assuming[Element[x, Reals], Refine[Element[x, Complexes]]]
Out:	True

Of course, the same holds for the other two examples:

In:	Assuming[x>0, Refine[Element[x, Complexes]]]
Out:	True

In:	Assuming[x>=0, Refine[Element[x, Complexes]]]
Out:	True

However, Refine recognizes that the stronger condition Element[x, Reals] 
holds for all three examples.

Alex


On Sun, 14 Jul 2013, Bill Rowe wrote:

> On 7/12/13 at 2:49 AM, akrasnov@cory.eecs.berkeley.edu (Alex Krasnov)
> wrote:
>
>> Firstly, x==0 also implicitly assumes that x is in Reals, since 0 is
>> in Reals, as the following examples demonstrate:
>
>> In:    Assuming[x==0, Refine[Element[x, Reals]]] Out:  True
>
>> In:    Assuming[{Element[x, Reals], x==0}, Refine[Infinity/x]]
>> Out:   ComplexInfinity
>
> No so. Consider
>
> In[1]:= Assuming[x == 0, Refine[Element[x, Complexes]]]
>
> Out[1]= True
>
>

Back to comp.soft-sys.math.mathematica | Previous | Next | Find similar | Unroll thread


Thread

Re: inconsistent refinement behavior Alex Krasnov <akrasnov@cory.eecs.berkeley.edu> - 2013-07-16 09:53 +0000

csiph-web