-
Notifications
You must be signed in to change notification settings - Fork 227
Make Turing.jl 0.6 compatible #293
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
Comments
When is this planned for? |
@ChrisRackauckas This is already planed in 0.3.1, which we plan to fix the adaption issue (#324) and Julia 0.6 compatibility. |
Closed the duplicate issue #330 |
* Initial support for infix ~ (#173). * seperate model wrapper call in sample.jl test * update ForwardDiff.Dual signature * sample.jl test passed * fix some tests for Julia 0.6 * remove typealias for 0.6 * make some functions 0.6-ish * make abstract 0.6-ish * change some decpreated functions * Update .travis.yml * Update appveyor.yml * Update appveyor.yml * fix test * Deprecations on package loading fixed * fix deprecations * implement callbacks for inner function * fix model type bug * Fix type * update Dual in benchmark * update Dual constructor * Bump up required Julia version to 0.6 * Disable depreciated warning messages for `consume/produce`. * Remove duplicate definition of produce. * fix floor, tanh, abs, log * fix logpdf warning and bug * fix vec assume init * Travis: Allow `Benchmarking` test to fail.
cc @xukai92 @emilemathieu @ae-foster @ChrisRackauckas We have fixed all known compatibility issues of Turing with Julia 0.6. The master branch of Turing now supports (requires) Julia 0.6. |
Great thanks! When do you plan on tagging? |
There are some remaining issues with the NUTS sampler, mostly related to robust adaption (see https://github.com/yebai/Turing.jl/milestone/5). I planned to fix those issues altogether in 0.3.1. But perhaps we can move these issues to 0.3.2 and make a new tagging now. What do you think? cc @xukai92 |
I would prefer a quicker tag, and more can always be added later of course. Reviewing tags in METADATA is easier when you have less per tag. |
I see - will do. |
* Initial support for infix ~ (#173). * seperate model wrapper call in sample.jl test * update ForwardDiff.Dual signature * sample.jl test passed * fix some tests for Julia 0.6 * remove typealias for 0.6 * make some functions 0.6-ish * make abstract 0.6-ish * change some decpreated functions * Update .travis.yml * Update appveyor.yml * Update appveyor.yml * fix test * Deprecations on package loading fixed * fix deprecations * implement callbacks for inner function * fix model type bug * Fix type * update Dual in benchmark * update Dual constructor * Bump up required Julia version to 0.6 * Disable depreciated warning messages for `consume/produce`. * Remove duplicate definition of produce. * fix floor, tanh, abs, log * fix logpdf warning and bug * fix vec assume init * Travis: Allow `Benchmarking` test to fail.
Would it maybe be an idea to add 0.6 to the travis tracker on the readme.md now this works? |
I've added the badge of 0.6 though I think the compilation doesn't pass because of the Stan dependency. For this reason I added a News sections explicitly saying that Turing.jl is 0.6 compatible. |
* Initial support for infix ~ (#173). * seperate model wrapper call in sample.jl test * update ForwardDiff.Dual signature * sample.jl test passed * fix some tests for Julia 0.6 * remove typealias for 0.6 * make some functions 0.6-ish * make abstract 0.6-ish * change some decpreated functions * Update .travis.yml * Update appveyor.yml * Update appveyor.yml * fix test * Deprecations on package loading fixed * fix deprecations * implement callbacks for inner function * fix model type bug * Fix type * update Dual in benchmark * update Dual constructor * Bump up required Julia version to 0.6 * Disable depreciated warning messages for `consume/produce`. * Remove duplicate definition of produce. * fix floor, tanh, abs, log * fix logpdf warning and bug * fix vec assume init * Travis: Allow `Benchmarking` test to fail.
Typing system is kind of changed - would need some refactors.
Related issue: #173
I would suggest that we fix #177 and also put 0.6 support in our 0.3 release?
The text was updated successfully, but these errors were encountered: