Repository navigation
elementwise versions of unary functions #347
Description
Activity
- added this to the milestone
on Aug 14, 2016 See #202, which was only partially completed.
This was blocked before due to ambiguous functions. It's fixed with a judicious application of namespace qualifications and Boost
enable_ifanddisable_ifqualifications. Now that I havelog1pworking I should be able to knock off the rest in no time. It will not require reverse-mode specializations as suggested in #272 and #271 (now closed).- modified the milestones: ,
on Aug 28, 2016 - changed the title
[-]vectorizing remaining unary functions[/-][+]elementwise versions of unary functions[/+]on Aug 29, 2016 - modified the milestones: ,
on Sep 7, 2016 Stan manual v2.17 says
powis not vectorized yet. Do you have a plan?- Yes, but it's going slowly. We should just vectorize that function (and the ^ syntax to go with it) rather than trying the general solution which Rayleigh Lei is working on.Reacted by Kentaro Matsuura
Summary:
There are functions like
log2()andlog1p()that are still not vectorized for elementwise application to containers.Description:
All of our unary functions should be vectorized. Review the index of the manual and make sure every unary function is vectorized. Here are the ones for this issue:
acoshasinhatanhexp2log1m_inv_logitlog1plog2log_inv_logitlogitPhi_approxtrigammatruncCurrent Version:
v2.11.0