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

MLE/MAP with start values gives ambiguity #1298

Closed
karajan9 opened this issue May 27, 2020 · 0 comments · Fixed by #1299
Closed

MLE/MAP with start values gives ambiguity #1298

karajan9 opened this issue May 27, 2020 · 0 comments · Fixed by #1299

Comments

@karajan9
Copy link
Contributor

Using MLE/MAP with a start values (to help conversion) results in the following ambiguity error:

julia> optimize(m, MLE(), [178.0, 25.0])
ERROR: MethodError: optimize(::DynamicPPL.Model{var"###evaluator#316",(:heights,),Tuple{Array{Float64,1}},(),DynamicPPL.ModelGen{var"###generator#317",(:heights,),(),Tuple{}}}, ::MLE, ::Array{Float64,1}) is ambiguous. Candidates:
  optimize(model::DynamicPPL.Model, ::MLE, args...; kwargs...) in Turing at C:\Users\Jens.Adam\.julia\packages\Turing\GMBTf\src\modes\ModeEstimation.jl:258
  optimize(f, g, initial_x::AbstractArray; inplace, autodiff, kwargs...) in Optim at C:\Users\Jens.Adam\.julia\packages\Optim\L5T76\src\multivariate\optimize\interface.jl:68
Possible fix, define
  optimize(::DynamicPPL.Model, ::MLE, ::AbstractArray)

I hope this is the right place for this issue.

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 a pull request may close this issue.

1 participant