Stan Math Unit Tests

11 views
Skip to first unread message

Michael Betancourt

unread,
Jul 22, 2015, 12:15:57 PM7/22/15
to stan...@googlegroups.com
So the math library requires boost, but boost is not included
— shouldn’t boost and eigen and gtest be libraries included
in math and then stan and the interfaces get access to them
via their inclusion of the math library?

Anyways, what’s the procedure for running unit tests on the
math library? I gots math to update!

Daniel Lee

unread,
Jul 22, 2015, 12:53:38 PM7/22/15
to stan...@googlegroups.com
Sorry about that. It was in the README, but was pulled out. It's now on a wiki page in Stan Math.

https://github.com/stan-dev/math/wiki

The simplest way is to set a STANAPI_HOME variable in the makefile like:

STANAPI_HOME = ~/stan/



Daniel



--
You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bob Carpenter

unread,
Jul 22, 2015, 2:11:22 PM7/22/15
to stan...@googlegroups.com
I also have a preference for including Boost. We don't
need to distribute it with R, which uses its own Boost,
but I think we should at least make it easy for ourselves.

Or is there a good reason not to I'm not seeing?

- Bob

Ben Goodrich

unread,
Jul 22, 2015, 2:22:56 PM7/22/15
to stan development mailing list, ca...@alias-i.com
On Wednesday, July 22, 2015 at 2:11:22 PM UTC-4, Bob Carpenter wrote:
I also have a preference for including Boost.  We don't
need to distribute it with R, which uses its own Boost,
but I think we should at least make it easy for ourselves.

Or is there a good reason not to I'm not seeing?

I think people would expect us to make Boost a git subrepo at this point. That way, they can have it under lib/ if they want or use their system's Boost.

Ben

Bob Carpenter

unread,
Jul 22, 2015, 2:28:27 PM7/22/15
to stan...@googlegroups.com
I don't want them to use their system's Boost unless it matches
the one true Boost version that we support. Boost's too
unstable release to release to give us much latitude. For instance,
1.56 broke backward compatibility for the parser with 1.55, and I'm
not sure there's a workaround other than 100+ #ifdefs.

- Bob
Reply all
Reply to author
Forward
0 new messages