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

Absolutely love the work you guys are doing and I firmly believe that javascript is the way to go with everything. I want to make a Chrome App using cylon.js and therefore stumbled upon this repo from this blog post. Looking through the README, it's documented that we have to write our code in the script.js file for instance and bundle it using Browserify like so:

 ./node_modules/.bin/brows

Hello,

I'm currently working on safety of PX4. And there are some gaps between documentation and PX4 stack. Especially there is only one mention about what is the scenario when 2 failsafe actions come up.

**If a failsafe occurs while the vehicle is responding to another failsafe (e.g. Low battery while in Return mode due to RC Loss), the specified failsafe action for the second trigger is

There seems to be some issues with the landing function in ./software/px4_mavros_scripts/1_px4_mavros_offboard_controller/commander.py.

To do:

1. Test the land function and report if it works well.
2. Fix if there is an issue.

The airframes in the TUDelft folder are a bit difficult to navigate, some have quite redundant info with little documentation. We need to update this.

Describe the new feature you'd like
We should write up a quick doc page that describes where Holodeck logs are kept. It might also be nice to have a holodeck.util.where_are_the_logs() helper function or something that would print out the full path to the log directory, so users can find their logs without thinking too hard.

We should then link to this page in the issue template for openi

Basic needs:

• Upgrade/flash instructions (probably need multiple for each module type) (see #109)
• Build instructions
• Usage walk through

Would be good:

• How to change the logo
• Overview of architecture, how to add stuff, etc

Maybe these could be separate tickets?

Can we set up a wiki so we can start to add LibrePilot content.

Initial content suggestion:

• How to contribute to the code using the GitHub development cycle (as opposed to Antlassian)
• Key points for building on each platform

There is also a link to the wiki in the makefile which needs updating.

We should not try to reconnect to the FC when msc or dfu commands are given since the FC will not respond for sure

Here, the Transfer ID timeout is set to be 1 second:

https://github.com/UAVCAN/libuavcan/blob/f99907251859d7e8dee54f71a19bd80c9b0c64c9/libuavcan/include/uavcan/transport/transfer_receiver.hpp#L24

The spec (both v0 and v1) says it should be 2 seconds by default, although it also could be changed by the application if necessary. We should change it to 2 seconds and possibly add a method to mak

Let's update the documentation to capture that the library can be installed as a module. We should include an explanation of the pip install -e . or python setup.py develop syntax to capture that many developers may want to install in place so they can continue to update and develop the library code.

Mag calibration no longer working on v11 upgrade.

If I switch back to v10 all is fine.

Also, is there a place you have all the parameters listed on git or in documentation somewhere? It’s difficult to have to open the cli if trying to amend things when not connected and it isn’t the easiest to read.

You should specify the labeling format. If it is <class_id> , the bounding boxes are completely broken.