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


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

Re: NMinimize problem: fct minimized uses FindRoot

Started byW Craig Carter <ccarter@mit.edu>
First post2011-12-16 10:56 +0000
Last post2011-12-16 10:56 +0000
Articles 1 — 1 participant

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: NMinimize problem: fct minimized uses FindRoot W Craig Carter <ccarter@mit.edu> - 2011-12-16 10:56 +0000

#7259 — Re: NMinimize problem: fct minimized uses FindRoot

FromW Craig Carter <ccarter@mit.edu>
Date2011-12-16 10:56 +0000
SubjectRe: NMinimize problem: fct minimized uses FindRoot
Message-ID<jcf840$6rs$1@smc.vnet.net>
Hello,
I didn't understand the rationale for the "do not use Return" maxim, so 
I constructed a little experiment:

(****** snip start *******)
(*list of lists of random lengths*)
temp = RandomInteger[{0, 100}, #] & /@ RandomInteger[{1, 100}, 
100000];

(*artificial examples of using Throw or Return*)

returnExample[x_] := Module[
  {max, min},
  If[Total[x] < 100, Return[0]];
  {max, min} = {Max[x], Min[x]};
  max^min
  ]

throwExample[x_] := Module[
  {max, min},
  If[Total[x] < 100, Throw[0]];
  {max, min} = {Max[x], Min[x]};
  max^min
  ]

(*timings*)
Timing[returnExample /@ temp;]
(*I get: {1.08535, Null}*)

Timing[Catch[throwExample[#]] & /@ temp;]

(*I get: {1.20134, Null}*)

(*******snip end********)

OK, this is artificial, but how do I understand why Return is eschewed 
when it appears to be faster and its construction is simpler?

Thanks, Craig


W Craig Carter
Professor of Materials Science, MIT



On Dec 14, 2011, at Wed, Dec 14, 11 ---6:00 AM, DrMajorBob wrote:

> There's a large gap between "explained and justified" versus "worth 
the 
> trouble" or even "sensible".
>
> Do not use Return. It isn't worth the spit you'll need to polish it.
>
> Bobby
>
> On Tue, 13 Dec 2011 04:39:04 -0600, Andrzej Kozlowski 
<akoz@mimuw.edu.pl> 
> wrote:
>
>>
>> On 12 Dec 2011, at 12:43, Oleksandr Rasputinov wrote:
>>
>>> For example, the erroneous usage:
>>>
>>> Block[{a = 1, b = 2}, Return[a]; Return[b]]
>>>
>>> gives:
>>>
>>> Return[1]
>>>
>>> but a correct usage:
>>>
>>> Do[Block[{a = 1, b = 2}, Return[a]; Return[b]], {1}]
>>>
>>> gives (because of the enclosing Do):
>>>
>>> 1
>>
>> This is not quite the whole story. For example, while the above use 
of 
>> Return in Block does not work, this one (in a function call) does:
>>
>> f[] := Block[{a = 1, b = 2}, Return[a]; Return[b]]
>>
>> f[]
>>
>> 1
>>
>> Moreover, if you replace the Do loop in your example with a While 
loop, 
>> you will get:
>>
>> n = 1; While[n < 10, Block[{a = 1, b = 2}, Return[a]; 
Return[b]]]
>>
>> Return[1]
>>
>> All of this is purposeful design and can be explained and justified 
but 
>> I don't think it's worth the bother since Mathematica has far 
superior 
>> means of flow control than this clumsy and arcane construct.
>>
>> Andrzej
>>
>>
>
>
> --
> DrMajorBob@yahoo.com
>

[toc] | [standalone]


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


csiph-web