Antilog and AntilogE (Float functions): Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 8: | Line 8: | ||
{{Template:Float:Antilog syntax}} | {{Template:Float:Antilog syntax}} | ||
{{Template:Float:AntilogE syntax}} | {{Template:Float:AntilogE syntax}} | ||
===Syntax terms=== | ===Syntax terms=== | ||
<table class="syntaxTable"> | <table class="syntaxTable"> | ||
<tr><th>%number </th> | <tr><th>%number </th> | ||
<td>A numeric variable to receive the | <td>A numeric variable to receive the antilog of the method object. </td></tr> | ||
<tr><th>float </th> | <tr><th>float </th> | ||
<td>A <var>Float</var> value.</td></tr> | <td>A <var>Float</var> value.</td></tr> | ||
| Line 18: | Line 19: | ||
==Usage notes== | ==Usage notes== | ||
<ul><li>Although you might expect <code>%x:log:antilog</code> to return the value in <code>%x</code>, the good fit techniques used by the <var>[[Log_(Float_function)|Log]]</var> and AntiLog methods make the result not quite exact, as shown in the following example: | <ul><li>Although you might expect <code>%x:log:antilog</code> to return the value in <code>%x</code>, the good fit techniques used by the <var>[[Log_(Float_function)|Log]]</var> and AntiLog methods make the result not quite exact, as shown in the following example: | ||
<p class="code"> | <p class="code">2:log:antilog = 2.00000000023047 | ||
3:log:antilog = 3.00000000017113 | |||
4:log:antilog = 4.00000000047426 | |||
5:log:antilog = 5.00000000057644 | |||
6:log:antilog = 6.00000000069796 | |||
7:log:antilog = 7.00000000056701 | |||
8:log:antilog = 8.00000000047046 | |||
9:log:antilog = 9.0000000010268 | |||
10:log:antilog = 10.0000000005553</p> | |||
<li><var>AntiLog</var> | <li><var>AntiLog</var> and <var>AntiLogE</var> are object-oriented versions of the <var>[[$Exp]]</var> function. | ||
<li>Available as of <var class="product"> | <li>Available as of <var class="product">Sirius Mods</var> Version 7.3.</ul> | ||
==Examples== | ==Examples== | ||
The following statement returns <code>1:antilog = 2.71828182845905</code>. | |||
<p class="code">[[PrintText statement|printText]] {~} = {1:antilog}</p | <p class="code">[[PrintText statement|printText]] {~} = {1:antilog}</p> | ||
==See also== | ==See also== | ||
{{Template:Float:Antilog and AntilogE footer}} | {{Template:Float:Antilog and AntilogE footer}} | ||
Revision as of 01:56, 24 February 2012
Antilog base e of a number (Float class)
The AntiLog and AntiLogE intrinsic functions return a number that is the natural anti-logarithm (or exponential) of the method object value. The result is the natural logarithmic base (ℯ) raised to the power of the method object value.
AntiLog and AntiLogE are synonyms.
Syntax
%number = float:Antilog
%number = float:AntilogE
Syntax terms
| %number | A numeric variable to receive the antilog of the method object. |
|---|---|
| float | A Float value. |
Usage notes
- Although you might expect
%x:log:antilogto return the value in%x, the good fit techniques used by the Log and AntiLog methods make the result not quite exact, as shown in the following example:2:log:antilog = 2.00000000023047 3:log:antilog = 3.00000000017113 4:log:antilog = 4.00000000047426 5:log:antilog = 5.00000000057644 6:log:antilog = 6.00000000069796 7:log:antilog = 7.00000000056701 8:log:antilog = 8.00000000047046 9:log:antilog = 9.0000000010268 10:log:antilog = 10.0000000005553
- AntiLog and AntiLogE are object-oriented versions of the $Exp function.
- Available as of Sirius Mods Version 7.3.
Examples
The following statement returns 1:antilog = 2.71828182845905.
printText {~} = {1:antilog}