This makes, for example, zeta(-7/2) return a result in terms of
zeta(9/2), and when you numerically evaluate it, you get the same
answer as you would get for zeta(-3.5).
This is nicer than just returning zeta(-7/2).
Add a couple of tests to rtest_zeta to verify the result.
elliptic_e(5*%pi/4,1) was returning 2-1/sqrt(2), but
elliptic_e(5*%pi/4,1),numer returned 2.707... or basically
2+1/sqrt(2).
This happens because we were simplifying elliptic_e(5*%pi/4,1) to
sin(5*%pi/4) = -1/sqrt(2). But we need to reduce the arg 5*%pi/4 by
%pi so we get sin(%pi/4) = 1/sqrt(2).
Add a test for this and that the symbolic and numerical values are
consistent.
Also needed to update the test for elliptic_e(x,1) to include the
reduction of the arg for the sin part.
I tweaked it slightly in the case of computing the eigenvectors so
that we print out the eigenvalues and the eigenvectors separately so
that we can see the column vectors more clearly.
Just add some docstrings to make it easier to understand what the
function does without having to read the code. Just to lower to
burden of understanding code.
This is an ancient bug that was present in Macsyma.
SETUP-MULTIVAR-DISREP gives genvars that are associated with multivars
the DISREP property so they disrep to 1. These genvars raised to powers
could be visible as unsimplified 1s raised to powers in output:
Prior to commit 38d4b2fd the internal genvars themselves could be made
visible by using taytorat:
(%i1) taylor(x^a,[x],0,1);
(%o1) +1^2*x^a
(%i2) taytorat(%);
(%o2) (g137^a)^2*x^a
Now we add to PDISREP! the knowledge that 1^x is equal to 1 for any x,
which prevents the construction of factors like 1^2 above. (PDISREP!
already knows that x^0 is equal to 1 and x^1 is equal to x for any x.)
No problems with the test suite or share test suite. New tests have
been added to rtest_taylor.
Corrected the permissions for the documentation images in the tmp_html folder
If the example images for the documentation are copied using "cp" if the source tree is write-protected
the images will be, too, and cannot be deleted afterwards due to being write-protected.
the "make distcheck" target tests if all temporary files can be deleted, though, and works on a
write-protected source tree.
On my computer this would repair the "make dist" target if there were no test failures.
