Re: Re: Guessing "exact" values

• To: mathgroup at smc.vnet.net
• Subject: [mg76288] Re: [mg76228] Re: Guessing "exact" values
• From: Murray Eisenberg <murray at math.umass.edu>
• Date: Sat, 19 May 2007 04:33:44 -0400 (EDT)
• Organization: Mathematics & Statistics, Univ. of Mass./Amherst
• References: <200705181009.GAA12917@smc.vnet.net>

```When I run that code and click the link, my browser shows a "File not
found!" error page.

Dana DeLouis wrote:
> Hi.  This is not the best solution, but here's one idea I use.
> It's not the best solution, because I can't find a way to make Mathematica's
> is locked in stone.
> Maybe an expert can jump in and make this dynamic.
>
> A number we know nothing about...(??)
> n = 6.283185307179586
>
> Set the variable to something you would like to use.  For me...
> NumberToSearch = n;
>
> Re-Enter this equation (Shift Enter), and then click the link.
>
>    StringReplace["http://bootes.math.uqam.ca/cgi-bin/ipcgi/lookup.\
>   pl?Submit=GO+&number=#&lookup_type=simple",
>      "#" :> ToString[Evaluate[NumberToSearch], InputForm,
>          NumberMarks -> False]]]
>
> The above click shows it might be 2 Pi.
>
> For your example, I took the full value:
> n=10.92477796076938
>
> This number didn't work.  Sometimes it won't work if the number is large.
> I don't know what "large" means, but the program really works with
> fractions.
>
> I decided to divided the number by 3.
>
> NumberToSearch = 10.92477796076938/3
> 3.641592653589793
>
> If I re-enter the Hyperlink, and click the link, the solution is Pi+1/2.
> Multiply by 3 to get your equation.
>
> Reference:  http://pi.lacim.uqam.ca/eng/

--
Murray Eisenberg                     murray at math.umass.edu
Mathematics & Statistics Dept.
Lederle Graduate Research Tower      phone 413 549-1020 (H)
University of Massachusetts                413 545-2859 (W)
710 North Pleasant Street            fax   413 545-1801
Amherst, MA 01003-9305

```

• Prev by Date: Re: Re: how save newly created palette?
• Next by Date: Re: A harmless and amusing bug
• Previous by thread: Re: Guessing "exact" values
• Next by thread: Re: Guessing "exact" values