Note that the formula is of the type A/(1+B*exp(C*x))+D so when x=0
the coefficient C disappears.
As for determining the inflection point of the regression equation:
solve will try all sorts of manipulations in order to get an exact
solution before resorting to numerical methods. In complex and
transcendental equations (things with trigonometric functions,
exponentials, logarithms in some sort of non trivial combination) and
especially with decimal numbers, which is the case, solve can take a
very long period of time and still fail to return a solution. In such
cases press ON on the handheld or Pause/Break on the computer (PC) to
interrupt the calculation (what's the key on Mac?)
Instead of using solve, which is not, by far, the correct tool for the
job, use nsolve(equation, var [=value] )
In this case and if your equation is stored as f1,
nSolve(d^2(f1(x))/dx^2=0,x) will give you the correct answer
(x=4.86806, given that we had to increase all x-values by 1 unit)
almost immediately.
As a general rule of thumb: If an exact symbolic solution isn't
expected OR the equation is highly complex and, of course, has only
one unknown, use nsolve instead of solve. Solve should be used in
equations where, in principle, a human being could do the same job
(only doesn't because it's long/tedious/hard/requires too many
techniques/all of the above)
About nsolve: it searches for ONE solution numerically. In case your
equation has more than one solution, nsolve will find only one. And
(and this is a sad but universal and unavoidable truth), in some cases
a solution cannot be found. nsolve employs a variety of numerical
algorithms to try to find a solution (bissection, newton, fixed point,
some combination of these?) and while in most cases (meaning, most
cases we're usually interested in) the algorithms are powerful enough
and converge quickly, in others they fail to converge quickly enough,
to attain the desired precision or to find a specific solution. If a
warning message is displayed (namely, questionable accuracy), check
your solution by replacing it in the equation.
It helps a lot to provide an initial guess if the solution isn't good
enough or the algorithms fail to converge to the solution you're
interested in. For example, by entering nSolve(d^2(f1(x))/dx^2=0,x=4)
will make nsolve use x=4 as initial value of the iterative algorithm.
A good initial value can increase dramatically the speed of the
calculation and "guide" the algorithm to converge to a specific
solution. What I usually do (if I'm dealing with a particularly nasty
equation) is plot the function graphically, then try to estimate a
zero of the function and use two initial values, one above and another
below that estimate, to determine its exact value. In most cases the
algorithms will converge to the nearest solution (there are others,
however, where a specific solution is an "unstable" point and no
matter how close to it is our initial guess, the algorithms will
always drift away from it.
Finally, beware that different numerical algorithms have different
error margins, but they all have error margins; one shouldn't expect,
just because an answer is displayed using 12 digits, to have a
precision of the magnitude of 10^-12. For the most part I think we can
say with some confidence that the returned value should be around
10^-5 or 10^-6 from the exact solution. Hoping for more is a bit
optimistic.
Attached file: the way I did it (I used the Nspire CAS but in order to
use nsolve you don't need it, it can be done on the numeric Nspire).
Nelson
> To unsubscribe send email to tinspire+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com.au/group/tinspire?hl=en-GB?hl=en-GB
> The tns documents shared by group members are archived at
> http://lafacroft.com/archive/nspire.php
>
> --
> To post to this group, send email to tins...@googlegroups.com
> To unsubscribe send email to tinspire+u...@googlegroups.com