Stan v2.6.1 tagged

20 views
Skip to first unread message

Daniel Lee

unread,
Mar 3, 2015, 12:01:40 PM3/3/15
to stan...@googlegroups.com

Daniel Lee

unread,
Mar 3, 2015, 12:44:59 PM3/3/15
to stan...@googlegroups.com
I forgot to add the release notes to that branch. I'll update the file in Stan, but it won't be tagged until the next release.


Daniel


On Tue, Mar 3, 2015 at 12:01 PM, Daniel Lee <bea...@alum.mit.edu> wrote:

Ben Goodrich

unread,
Mar 3, 2015, 1:10:42 PM3/3/15
to stan...@googlegroups.com
Bob, how do you build the parser now? Before in rstan, we had a bunch of things like

#include <stan/gm/compiler.hpp>

but now gm/ is gone and appears to be replaced by lang/ Is that all that needs to be switched?

Ben

Daniel Lee

unread,
Mar 3, 2015, 1:14:45 PM3/3/15
to stan...@googlegroups.com
Yes. That should work.
--
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.

Ben Goodrich

unread,
Mar 3, 2015, 1:16:48 PM3/3/15
to stan...@googlegroups.com
Also, what replaces this now non-existent file

#include <stan/common/do_print.hpp>

Ben

Jiqiang Guo

unread,
Mar 3, 2015, 1:22:22 PM3/3/15
to stan...@googlegroups.com
Ben, I have a branch (debug/test_grad_crash) that has a lot of changes due to this folder/namespace renaming.  I will merge it to develop.  

Jiqiang 

Ben Goodrich

unread,
Mar 3, 2015, 1:25:20 PM3/3/15
to stan...@googlegroups.com
Great.
To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+unsubscribe@googlegroups.com.

Ben Goodrich

unread,
Mar 3, 2015, 1:31:21 PM3/3/15
to stan...@googlegroups.com
I already have a local commit that updated StanHeaders/inst/include/upstream to the new master before I discovered that we need to make changes on the rstan side too. I think there will be no conflict if you also go into StanHeaders/inst/include/upstream and do git pull origin master but there might be a merge conflict if you set the HEAD to v.2.6.1 . I think master would be the better choice.

Ben

Jiqiang Guo

unread,
Mar 3, 2015, 1:42:52 PM3/3/15
to stan...@googlegroups.com
It is ok.  I never update the submodule now to github as I don't know how they it works exactly.  But now on travis-ci, it points to stan's develop branch via the configuration in .travis.yml (so it can also be changed to master or any other branch easily). 

Jiqiang 

To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages