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


Groups > comp.soft-sys.math.mathematica > #15154 > unrolled thread

inconsistent refinement behavior

Started byAlex Krasnov <akrasnov@cory.eecs.berkeley.edu>
First post2013-07-10 07:22 +0000
Last post2013-07-12 06:29 +0000
Articles 3 — 2 participants

Back to article view | Back to comp.soft-sys.math.mathematica


Contents

  inconsistent refinement behavior Alex Krasnov <akrasnov@cory.eecs.berkeley.edu> - 2013-07-10 07:22 +0000
    Re: inconsistent refinement behavior Helen Read <readhpr@gmail.com> - 2013-07-11 05:57 +0000
    Re: inconsistent refinement behavior Alex Krasnov <akrasnov@cory.eecs.berkeley.edu> - 2013-07-12 06:29 +0000

#15154 — inconsistent refinement behavior

FromAlex Krasnov <akrasnov@cory.eecs.berkeley.edu>
Date2013-07-10 07:22 +0000
Subjectinconsistent refinement behavior
Message-ID<krj23l$1jf$1@smc.vnet.net>
The following behavior appears to be inconsistent:

In:	Assuming[x==0, Refine[Infinity/x]]
Out:	ComplexInfinity

In:	Assuming[x>0, Refine[Infinity/x]]
Out:	Infinity

In:	Assuming[x>=0, Refine[Infinity/x]]
Out:	Infinity

The third example should return unrefined given the first two examples. Is 
there an explanation?

Alex

[toc] | [next] | [standalone]


#15164

FromHelen Read <readhpr@gmail.com>
Date2013-07-11 05:57 +0000
Message-ID<krlhfi$88k$1@smc.vnet.net>
In reply to#15154
There is nothing inconsistent about this. When you include the 
assumption x>0 or x>=0, you are implicitly assuming that x is an element 
of the Reals, so with either of these assumptions the result will be 
Infinity rather than ComplexInfinity.

Recall that there is no ordering in the complex numbers.

On 7/10/2013 3:22 AM, Alex Krasnov wrote:
> The following behavior appears to be inconsistent:
>
> In:	Assuming[x==0, Refine[Infinity/x]]
> Out:	ComplexInfinity
>
> In:	Assuming[x>0, Refine[Infinity/x]]
> Out:	Infinity
>
> In:	Assuming[x>=0, Refine[Infinity/x]]
> Out:	Infinity
>
> The third example should return unrefined given the first two examples. Is
> there an explanation?
>
> Alex
>



[toc] | [prev] | [next] | [standalone]


#15166

FromAlex Krasnov <akrasnov@cory.eecs.berkeley.edu>
Date2013-07-12 06:29 +0000
Message-ID<kro7o8$f19$1@smc.vnet.net>
In reply to#15154
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

Secondly, ComplexInfinity results from the unknown sign of x at 0, not any 
property of complex numbers.

Alex


On Thu, 11 Jul 2013, Helen Read wrote:

> There is nothing inconsistent about this. When you include the
> assumption x>0 or x>=0, you are implicitly assuming that x is an element
> of the Reals, so with either of these assumptions the result will be
> Infinity rather than ComplexInfinity.
>
> Recall that there is no ordering in the complex numbers.
>
> On 7/10/2013 3:22 AM, Alex Krasnov wrote:
>> The following behavior appears to be inconsistent:
>>
>> In:	Assuming[x==0, Refine[Infinity/x]]
>> Out:	ComplexInfinity
>>
>> In:	Assuming[x>0, Refine[Infinity/x]]
>> Out:	Infinity
>>
>> In:	Assuming[x>=0, Refine[Infinity/x]]
>> Out:	Infinity
>>
>> The third example should return unrefined given the first two examples. Is
>> there an explanation?
>>
>> Alex
>>
>
>
>
>

[toc] | [prev] | [standalone]


Back to top | Article view | comp.soft-sys.math.mathematica


csiph-web