There seems to be conflicting data on what the "OriginGeopoint" is. In the documentation it's referenced as the location of the PlayerStart while in code it's commented as the coordinates of Unreal level at the coordinates 0,0,0.

Code:
https://github.com/microsoft/AirSim/blob/e24a11d5985c1d6f573735f28a3844bc634559db/AirLib/include/common/AirSimSettings.hpp#L350

Documentation:
https://micro

In the CI automated generated docs of the control repo, we can add documentation generated automatically showing classes usage in different nodes.

Should we have a list of packages that implement models (e.g. https://github.com/JuliaPOMDP/RockSample.jl) on the README? Or should they be listed in another place?

In Jupyter and Juno we can display systems in a prettier way than we are currently doing. Instructions on displaying LaTeX is given here
http://docs.junolab.org/latest/man/info_developer.html

Essentially, one has to define (pseudo code)

function Base.show(io::IO, ::MIME"text/html", G::TransferFunction)
    "\$\\dfrac{$(G.num)}{$(G.den)}"
end

Current docstring contents are not sufficient. Every function, regardless of trivialness, require at least one usage example.

I tried doing a TuLiP installation from scratch on a wiped out Mac. I found the following poitns a bit confusing in installation instructions (this could be because of the strange access rights on Mac).

• User access rights are not clear in installation instructions. Is it assumed that everything is done in sudo? We might want to clarify this.
• I started getting pip and installed it

The documentation of post operators (continuous and discrete) is lacking or misplaced (eg. BFFPSV18 docs is dispersed in ReachSets.jl and reach_blocks.jl). See also this comment.

One place to document what the algorithms are doing is the algorithm's struct. Also all the available options admitted by the algori