Zachary Sunberg

Hi @radioflash , Thanks for your interest in contributing! Yes, I think it is best to add compat entries to the Project.toml > Are pull request for additional filter implementations...

Have not thought through in detail, but another option would be to create a new package that depends on this one with the advanced DD2 filter.

Parameterizing by the `DynamicsModel` and `ObservationModel` types will indeed yield significant performance improvement, but these parameters need not be present in function signatures, for example: ```julia function predict(b0::GaussianBelief, u::AbstractVector, filter::ExtendedKalmanFilter)...

Or... ```julia struct LinearDiscretizer{N, D, E

I don't think there is a built-in way (which is a little frustrating). You can save it to a png and use `imshow()` from Images.jl or save it as an...

I think we implement this ``` show(io::IO, MIME"image/svg+xml", img::WhateverTypeIMGIs) ``` Then users can use whatever display they want, e.g. ``` julia> using ElectronDisplay julia> display(img) ``` We should also probably...

Maybe we should make `BrowserDisplay.jl` that just pops up html-y things in a browser when `display` is called.

Oh, hmm... Yeah, I think implementing either `show` or `display` in this case is [piracy](https://docs.julialang.org/en/v1/manual/style-guide/index.html#Avoid-type-piracy-1). Is that `show` method already implemented for `CairoSurface`? If so, maybe `display` will just work.

Ha, yes ``` julia> using AutomotiveDrivingModels, ElectronDisplay, AutoViz julia> roadway = gen_stadium_roadway(4, length=100.0) ``` just works.

we should add this to the docs