commit | 77e80aecf736ca0d468155879e8442a8d22a9423 | [log] [tgz] |
---|---|---|
author | Russell Smith <russells@google.com> | Thu Apr 16 19:42:39 2015 -0700 |
committer | Sameer Agarwal <sameeragarwal@google.com> | Wed Apr 29 12:38:04 2015 +0000 |
tree | 57eec3bbd404dc8d12202ee48423bcef22582a9e | |
parent | 2175d025a61089d483dee3cbe8127b17aafbbeb2 [diff] |
Additional special cases in the handling of pow(Jet,Jet). I think this is all of the cases. These cases arise because pow(a,b) is limited to real valued results, if the argument and result were complex valued then these cases would disappear. NOTE: Since there is so much special casing here, it is worth checking to see if cpow() is implemented in terms of pow(), and what might be the consequences of using cpow() on the type std::complex<Jet<double, N> >. It is *possible* that a separate implementation of cpow might be required also. Also some comment fixes. Change-Id: Ia1e38df4cdcb548f778304c2854cacba6e1556ff
Please see ceres-solver.org for more information.
Ceres development happens on Gerrit, including both repository hosting and code reviews. The GitHub Repository is a continuously updated mirror which is primarily meant for issue tracking. Please see our Contributing to Ceres Guide for more details.
The upstream Gerrit repository is
https://ceres-solver.googlesource.com/ceres-solver