-
Notifications
You must be signed in to change notification settings - Fork 20
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
autoinit vs setValKDE #124
Comments
Thanks, this is useful information -- I will get this fixed! |
function manual_init(fgl::FactorGraph, sym::Symbol, usefct::Symbol)
# developed when autoinit was not working properly -- should be used with care
warn("manual_init being used as a workaround for temporary autoinit issues.")
pts = IIF.approxConv(fgl, usefct, sym)
X2pre = KDE.kde!(pts)
IIF.setValKDE!(fgl, sym, X2pre)
getData(fgl, sym).initialized = true
nothing
end
|
dehann
added a commit
that referenced
this issue
Dec 9, 2018
also see, eg. |
partially related to tree based initialization. |
mostly resolved through tree initialization introduced during v0.6.x |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This initialization procedure with setValKDE appears to take into account tight GPS priors correctly, whereas doautoinit appears to initialize around (0,0) only.
See: PropFac/examples/testBackwards.jl
The text was updated successfully, but these errors were encountered: