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

Bump AbstractMCMC major version #1579

Merged
merged 4 commits into from
Apr 11, 2021
Merged

Bump AbstractMCMC major version #1579

merged 4 commits into from
Apr 11, 2021

Conversation

torfjelde
Copy link
Member

@torfjelde torfjelde commented Apr 9, 2021

Supersedes #1574 and #1575

Copy link
Member

@devmotion devmotion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just have to make sure that it's actually tested and needs a version bump 👍

@devmotion
Copy link
Member

The same strange errors in the Gibbs MH test. I'm even more surprised that the errors occur on Julia 1.3 🤔

@devmotion
Copy link
Member

The failing tests were added recently in #1557.

@devmotion
Copy link
Member

@cpfiffer Maybe we should just change the test in

MH((, vc_σ)),
? To me it seems, it is likely to fail randomly (even with a small step size) since we use a random walk proposal for the standard deviation that has to be positive (otherwise the model errors)?

@torfjelde
Copy link
Member Author

But it should be linking, no?

@torfjelde
Copy link
Member Author

At least that's the intention:

maybe_link!(vi, spl, spl.alg.proposals)

@torfjelde
Copy link
Member Author

I think I see the issue. https://github.com/TuringLang/Turing.jl/blob/master/src/inference/mh.jl#L404 passes spl.alg.proposals, but in this case the proposals are actually NamedTuple{sym, RandomWalkProposal} and so they hit the maybe_link! which does nothing.

@coveralls
Copy link

coveralls commented Apr 11, 2021

Pull Request Test Coverage Report for Build 736956259

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 78.167%

Totals Coverage Status
Change from base Build 736943876: 0.0%
Covered Lines: 1117
Relevant Lines: 1429

💛 - Coveralls

@codecov
Copy link

codecov bot commented Apr 11, 2021

Codecov Report

Merging #1579 (35ea02b) into master (9104637) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1579   +/-   ##
=======================================
  Coverage   78.16%   78.16%           
=======================================
  Files          23       23           
  Lines        1429     1429           
=======================================
  Hits         1117     1117           
  Misses        312      312           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9104637...35ea02b. Read the comment docs.

@@ -32,7 +32,7 @@ Tracker = "9f7883ad-71c0-57eb-9f7f-b5c9e6d3789c"
ZygoteRules = "700de1a5-db45-46bc-99cf-38207098b444"

[compat]
AbstractMCMC = "2.1"
AbstractMCMC = "2.1, 3"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
AbstractMCMC = "2.1, 3"
AbstractMCMC = "3"

This should cut out AbstractMCMC 2 because the internal API changes.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But this is only relevant for users that use custom callbacks? I.e., for Turing it should be fine to support both versions since we do not depend on these internals, do we?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, I suppose not. IGNORE ME

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, leaving it as is:)

@@ -28,7 +28,7 @@ Tracker = "9f7883ad-71c0-57eb-9f7f-b5c9e6d3789c"
Zygote = "e88e6eb3-aa80-5325-afca-941959d7151f"

[compat]
AbstractMCMC = "2.1"
AbstractMCMC = "2.1, 3"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
AbstractMCMC = "2.1, 3"
AbstractMCMC = "3"

Same here.

@torfjelde torfjelde merged commit be40a19 into master Apr 11, 2021
@delete-merged-branch delete-merged-branch bot deleted the tor/abstractmcmc-v3 branch April 11, 2021 16:08
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

Successfully merging this pull request may close these issues.

4 participants