Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AISTATS camera-ready plan #424

Closed
6 of 12 tasks
xukai92 opened this issue Feb 24, 2018 · 5 comments
Closed
6 of 12 tasks

AISTATS camera-ready plan #424

xukai92 opened this issue Feb 24, 2018 · 5 comments

Comments

@xukai92
Copy link
Member

xukai92 commented Feb 24, 2018

@xukai92
Copy link
Member Author

xukai92 commented Feb 24, 2018

Note: for testing we need to test both with ReverseDiff.jl and ForwardDiff.jl as backend. Also I have set a flag to use ReverseDiff.jl either "safely" or `unsafely". "safely" means Turing.jl force to re-compile the tape each time it get gradient - it is much slower but can handle dynamic model.

  • a68e9af passes all tests except gibbs.jl/gibbs2jl for unsafe reverse diff. I didn't figure out why.

@yebai
Copy link
Member

yebai commented Feb 26, 2018

Here is the CrossCat model I mentioned - http://probcomp.csail.mit.edu/crosscat/. This model is not super urgent, let's focus on existing models for now. When we are done, we can consider the following two models

@ChrisRackauckas
Copy link
Collaborator

ChrisRackauckas commented Feb 27, 2018

If you need more realish benchmarks you can use ours from DiffEqBayes.jl. Some of them we have Turing.jl omitted because of SciML/DiffEqBayes.jl#30 , but for what works it seems to work well according to the benchmarks in https://github.com/JuliaDiffEq/DiffEqBenchmarks.jl/

There's a question of how to address time and accuracy at the same time that is being worked on by @Vaibhavdixit02. If you have any pointers that would be helpful.

@xukai92
Copy link
Member Author

xukai92 commented Mar 4, 2018

Thanks! I checked the benchmark results. Just FYI the benchmark results actually indicates Turing.jl is slower than Stan as the sampling algorithm used is different. E.g. https://github.com/JuliaDiffEq/DiffEqBenchmarks.jl/blob/master/ParameterEstimation/DiffEqBayesFitzHughNagumo.ipynb shows Stan uses 93.0s and Turing.jl uses 30.9s, however, Stan takes 79*600 evaluations of the model but Turing.jl only takes 4*500, which together says Stan is 7.65 times faster.

I managed to make Turing.jl faster on high dimensional problem by adapting ReverseDiff.jl (branch not merged yet) but it seems that another main slowness of Turing.jl comes from things mentioned in #400, which I don't have yet a very clear approach about how to improve.

@yebai yebai closed this as completed Apr 2, 2018
@xukai92
Copy link
Member Author

xukai92 commented Apr 3, 2018

Benchmark models are added in PR #424

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants