profile
viewpoint
Alexis Paques AlexisTM The Kobi Company @TheKobiCompany Brussels, Belgium alexistm.github.io IoT lover & Robotics Engineer

AlexisTM/aero-optical-flow-ros 5

Optical flow for the aero on ROS to publish the images as well

AlexisTM/avoidance 2

PX4 avoidance ROS node for obstacle detection and avoidance.

AlexisTM/catkin_tools 1

Command line tools for working with catkin

AlexisTM/3d-game-shaders-for-beginners 0

🎮 A step-by-step guide on how to implement SSAO, depth of field, lighting, normal mapping, and more for your 3D game.

AlexisTM/alexistm.github.io 0

Personal website source

AlexisTM/allennlp 0

An open-source NLP research library, built on PyTorch.

AlexisTM/animate.css 0

A cross-browser library of CSS animations. As easy to use as an easy thing.

AlexisTM/aprilslam 0

Mapping and Pose Estimation from AprilTags under ROS

startedclearpathrobotics/ros_computer_setup

started time in 2 days

startedclearpathrobotics/spot_ros

started time in 2 days

startedzajo/synapse

started time in 4 days

push eventTheKobiThirdParty/PX4Firmware

Daniel Agar

commit sha f19a20dc43d184f772b75072aa59a57b855c092a

commander: preflight power check ignore module count if USB connected - this check isn't relevent during bench testing

view details

Daniel Agar

commit sha 942eb8318455f36c165842001f261ddee225dee1

sensors: keep legacy params active (BAT_V_DIV/BAT_A_PER_V) for QGC SITL - fixes https://github.com/PX4/Firmware/issues/15505

view details

Daniel Agar

commit sha 6937dbc5fdd80f16f28032fb62f16b5003e29aff

boards: add CUAV Nora support

view details

Thies Lennart Alff

commit sha d7d8aa9b64635cc3d3781dec1c882e348da2df6b

uuv_att_control: removed redundant code, switched to new uORB API

view details

Daniel Agar

commit sha 0bb5f2c2af829dce275522b059a0f1babcea44eb

uavcan: libuavcan submodule remove redundant libuavcan_drivers

view details

Beat Küng

commit sha ba5d7773f8eed5be0d74fd2406d87113c5dadd63

mavlink_timesync: print sender comp id for 'RTT too high for timesync' msg (#15539) helps with debugging

view details

Daniel Agar

commit sha 0c91a29c3f401ebe567ff25ba6a21e95c5be507a

wq:attitude_ctrl increase stack

view details

Daniel Agar

commit sha f8241f144cd0ad829f35ff2b4516c64de01dd158

hmc5883: cleanup device interface on destruction

view details

Daniel Agar

commit sha 03efea9d7388ce049b2c3aa519191a5891e4c27a

lis2mdl: cleanup device interface on destruction

view details

Daniel Agar

commit sha 8252fea95b3e50ec3d32440dd1c2001c3323c767

lis3mdl: cleanup device interface on destruction

view details

Daniel Agar

commit sha f1e5b1d28450760973188890aa48a08f194588cd

qmc5883: cleanup device interface on destruction

view details

Daniel Agar

commit sha 877c19704a1da6f893968c2e00d6420cdcf8d329

rm3100: cleanup device interface on destruction

view details

David Sidrane

commit sha 13246bdb2c5f81c6f7ef8919db7cc3f3c7f7532f

common/shutdown:All FMU's not stying in bootloader Fixes bug, wehre reboot -b would not stay in bootloader. Call was passing bit mask (=4) not integer value of 1.

view details

David Sidrane

commit sha 157aa36c1e784a2e62e44dff2cf1ba5d81d379d3

NuttX based bootloader:Track QGC change in sequnsing It appear that QGC is now resyncing between operation. This was causing the bl_state to be reset to STATE_PROTO_GET_SYNC and loosing the state of (STATE_PROTO_GET_SYNC|STATE_PROTO_GET_DEVICE)

view details

David Sidrane

commit sha 22a7bf6ec72b4ecbde9767924e5c33d025b3ab71

px4_fmu-v6x Fix BOARD_TYPE

view details

Daniel Agar

commit sha fe06eaf8d994298947d361b346f736fe728857e0

Tools: Ubuntu setup update arm-none-eabi-gcc to 9-2020-q2-update

view details

Daniel Agar

commit sha d3a1225c98076c626d601e01e1f785066122a5b7

Tools: Ubuntu setup remove "set -e" to prevent grep early exit - the gcc version grep was causing the script to exit early

view details

Daniel Agar

commit sha 65ab7cef2e469834057a3addf9cf70d7d7db7133

boards: cubepilot/cubeyellow small fixes and improvements - fix UART config (GPS1, etc) - TELEM2 enable TX DMA - init simplify (sync with CubeOrange) - amber LED use for armed state - manually start ak09916 (Here2) on I2C2 with proper rotation

view details

Daniel Agar

commit sha 91ad8473ab8791ea963ff214242780231682ede0

boards: cubepilot/cubeorange small fixes and improvements - defconfig UART sync with cube yellow (and other boards) - manually start ak09916 (Here2) on I2C2 with proper rotation

view details

Daniel Agar

commit sha ad3e6ee5ddeb534d04392ae614c7bcfc9c2f8f01

wq:attitude_ctrl increase stack by 16 bytes (again)

view details

push time in 4 days

startedcontinental/rmw_ecal

started time in 4 days

push eventTheKobiThirdParty/cpprest

Alexis Paques

commit sha 2e3795fd76bfb4a9cf306b0ad7217c15edcd11f4

Add thread name for pplx

view details

Alexis Paques

commit sha c76b8fcbe3c9840450118c899bcbc9d527e0efa3

Add thread name for pplx

view details

push time in 5 days

startedgoldsborough/ipc-bench

started time in 8 days

create barnchTheKobiThirdParty/clipper.cpp

branch : kobi

created branch time in 9 days

push eventTheKobiThirdParty/cpprest

Alexis Paques

commit sha de6532f99ad9b4015d945ddd2b7f9091fd7211a7

Flatten repo

view details

Alexis Paques

commit sha 3d25f027aead253a74ed530c3acecb966e13c3b7

Flatten repo

view details

push time in 9 days

push eventTheKobiThirdParty/cpprestsdk

Alexis Paques

commit sha 5bab4665d28dc2cbdd8c0277e44e53588fa23656

Catkinize

view details

push time in 9 days

push eventTheKobiThirdParty/cpprestsdk

Alexis Paques

commit sha c939540c2caf8c9c2231c664f9cdf06848f77724

Overwrite cache

view details

push time in 9 days

push eventTheKobiThirdParty/cpprestsdk

Alexis Paques

commit sha 2798a3bf36455d19ad885c65b1e44639942d9858

Catkinize

view details

push time in 9 days

create barnchTheKobiThirdParty/cpprestsdk

branch : kobi

created branch time in 9 days

startedintel-isl/OpenBot

started time in 9 days

startedmicro-ROS/benchmarking-results

started time in 11 days

startedloentar/ngrest

started time in 11 days

startedlaanwj/k210-sdk-stuff

started time in 11 days

startedembeddedgo/kendryte

started time in 11 days

startednamhyung/uftrace

started time in 12 days

issue commentPX4/Firmware

USB connection is only accessible if connected in a window of few seconds

Using the same cables with other USB-CDC devices, I do not have the issue. (tested with 3 other devices using CDC)

AlexisTM

comment created time in 12 days

issue openedgoogle/orbit

Failed to build due to std::filesystem dependency check in CMake (c++17)

On Ubuntu 18.04, I had to enable C++17 for the clang profiles to find std::filesystem.

The following flag was added to the conan profiles for clang9: compiler.cppstd=17

-- Looking for C++ include filesystem
-- Looking for C++ include filesystem - not found
CMake Error at cmake/FindFilesystem.cmake:228 (message):
  Cannot Compile simple program using std::filesystem
Call Stack (most recent call first):
  CMakeLists.txt:122 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/alexis/tools/orbit/build_clang9_debug/build_clang9_release/CMakeFiles/CMakeOutput.log".
See also "/home/alexis/tools/orbit/build_clang9_debug/build_clang9_release/CMakeFiles/CMakeError.log".
ERROR: conanfile.py (OrbitProfiler/None): Error in build() method, line 154
	cmake.configure()
	ConanException: Error 1 while executing cd '/home/alexis/tools/orbit/build_clang9_debug/build_clang9_release' && cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE="Release" -DCONAN_IN_LOCAL_CACHE="OFF" -DCONAN_COMPILER="clang" -DCONAN_COMPILER_VERSION="9" -DCONAN_CXX_FLAGS="-m64" -DCONAN_SHARED_LINKER_FLAGS="-m64" -DCONAN_C_FLAGS="-m64" -DCONAN_LIBCXX="libstdc++11" -DCMAKE_INSTALL_PREFIX="/home/alexis/tools/orbit/build_clang9_debug/build_clang9_release/package" -DCMAKE_INSTALL_BINDIR="bin" -DCMAKE_INSTALL_SBINDIR="bin" -DCMAKE_INSTALL_LIBEXECDIR="bin" -DCMAKE_INSTALL_LIBDIR="lib" -DCMAKE_INSTALL_INCLUDEDIR="include" -DCMAKE_INSTALL_OLDINCLUDEDIR="include" -DCMAKE_INSTALL_DATAROOTDIR="share" -DCONAN_CMAKE_POSITION_INDEPENDENT_CODE="ON" -DCMAKE_PREFIX_PATH="/home/alexis/tools/orbit/build_clang9_debug/build_clang9_release" -DCMAKE_MODULE_PATH="/home/alexis/tools/orbit/build_clang9_debug/build_clang9_release" -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY="ON" -DCONAN_EXPORTED="1" -DWITH_GUI="ON" -DWITH_ORBITGL="ON" -DWITH_CRASH_HANDLING="ON" -DCRASHDUMP_SERVER="" -Wno-dev '/home/alexis/tools/orbit'

created time in 16 days

startedgoogle/orbit

started time in 16 days

issue commentzulip/zulip

[not yet actionable] Add Hangouts Meet video call API

The free tier was up to 24h meetings, going down to 1h meeting maximum. Always free, but reduced :disappointed:

timabbott

comment created time in 16 days

startedAuburn/FastNoiseSIMD

started time in 18 days

starteduzh-rpg/rpg_information_field

started time in 18 days

startedchegewara/sipeed-maixduino-test-apps

started time in 18 days

issue commentPX4/Firmware

USB connection is only accessible if connected in a window of few seconds

The messages are the typical messages the Pixhawk was supposed to send such as IMU data, position data, ...

Note that I do not have a serial cable as of now and cannot debug further. :disappointed:

Could it be caused by the age of the Pixhawk? It is an old 3DR Pixhawk.

AlexisTM

comment created time in 19 days

startedmeco-group/rtPGM

started time in 20 days

delete branch AlexisTM/modalise.js

delete branch : dependabot/npm_and_yarn/node-sass-4.13.1

delete time in 23 days

push eventAlexisTM/modalise.js

dependabot[bot]

commit sha 163de7cc210b075ffa8f23774fc16698f90ed12f

Bump node-sass from 3.13.1 to 4.13.1 Bumps [node-sass](https://github.com/sass/node-sass) from 3.13.1 to 4.13.1. - [Release notes](https://github.com/sass/node-sass/releases) - [Changelog](https://github.com/sass/node-sass/blob/master/CHANGELOG.md) - [Commits](https://github.com/sass/node-sass/compare/v3.13.1...v4.13.1) Signed-off-by: dependabot[bot] <support@github.com>

view details

Alexis Paques

commit sha 96958e770f9394c0d538b69d54bb5aa5d0398683

Merge pull request #5 from AlexisTM/dependabot/npm_and_yarn/node-sass-4.13.1 Bump node-sass from 3.13.1 to 4.13.1

view details

push time in 23 days

PR merged AlexisTM/modalise.js

Bump node-sass from 3.13.1 to 4.13.1 dependencies

Bumps node-sass from 3.13.1 to 4.13.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sass/node-sass/releases">node-sass's releases</a>.</em></p> <blockquote> <h2>v4.13.1</h2> <h3>Community</h3> <ul> <li>Fix render example syntax (<a href="https://github.com/ZoranPandovski">@ZoranPandovski</a> , <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2787">#2787</a>)</li> <li>Fix <code>sourceMap</code> option inconsistencies (<a href="https://github.com/saper">@saper</a> , <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2394">#2394</a>)</li> <li>Fix possible crash in customer importer (<a href="https://github.com/xzyfer">@xzyfer</a>, <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2816">#2816</a>)</li> </ul> <h2>Supported Environments</h2> <table> <thead> <tr> <th>OS</th> <th>Architecture</th> <th>Node</th> </tr> </thead> <tbody> <tr> <td>Windows</td> <td>x86 & x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13</td> </tr> <tr> <td>OSX</td> <td>x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13</td> </tr> <tr> <td>Linux*</td> <td>x86 & x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^, 13**^</td> </tr> <tr> <td>Alpine Linux</td> <td>x64</td> <td>6, 8, 10, 11, 12, 13</td> </tr> <tr> <td>FreeBSD</td> <td>i386 amd64</td> <td>8, 10, 12, 13</td> </tr> </tbody> </table> <p>Linux support refers to Ubuntu, Debian, and CentOS 5+ ** Not available on CentOS 5 ^ Only available on x64</p> <h2>v4.13.0</h2> <h3>Features</h3> <ul> <li>Node 13 support (<a href="https://github.com/saper">@saper</a>, <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2766">#2766</a> <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2767">#2767</a>)</li> </ul> <h3>Community</h3> <ul> <li>Fix broken link to NodeJS docs in README.md (<a href="https://github.com/schwigri">@schwigri</a>, <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2753">#2753</a>)</li> <li>Assorted typo fixes (<a href="https://github.com/XhmikosR">@XhmikosR</a> , <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2726">#2726</a>)</li> <li>Remove PR template (<a href="https://github.com/nschonni">@nschonni</a>)</li> <li>Remove sudo settings from .travis.yml (<a href="https://github.com/abetomo">@abetomo</a>, <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2673">#2673</a>)</li> <li>Add note in PR template about node-gyp 4.0 (<a href="https://github.com/nschonni">@nschonni</a>)</li> <li>Change note about Node 12 support (<a href="https://github.com/nschonni">@nschonni</a>)</li> </ul> <h3>Dependencies</h3> <ul> <li>lodash@^4.17.15 (<a href="https://github.com/kessenich">@kessenich</a>, <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2574">#2574</a>)</li> </ul> <h2>Supported Environments</h2> <table> <thead> <tr> <th>OS</th> <th>Architecture</th> <th>Node</th> </tr> </thead> <tbody> <tr> <td>Windows</td> <td>x86 & x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13</td> </tr> <tr> <td>OSX</td> <td>x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13</td> </tr> <tr> <td>Linux</td> <td>x86 & x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^, 13**^</td> </tr> <tr> <td>Alpine Linux</td> <td>x64</td> <td>6, 8, 10, 11, 12, 13</td> </tr> <tr> <td>FreeBSD</td> <td>i386 amd64</td> <td>6, 8, 10, 12, 13</td> </tr> </tbody> </table> <p>*Linux support refers to Ubuntu, Debian, and CentOS 5+</p> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/sass/node-sass/blob/master/CHANGELOG.md">node-sass's changelog</a>.</em></p> <blockquote> <h2>v4.13.1</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.13.1">https://github.com/sass/node-sass/releases/tag/v4.13.1</a></p> <h2>v4.13.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.13.0">https://github.com/sass/node-sass/releases/tag/v4.13.0</a></p> <h2>v4.12.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.12.0">https://github.com/sass/node-sass/releases/tag/v4.12.0</a></p> <h2>v4.11.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.11.0">https://github.com/sass/node-sass/releases/tag/v4.11.0</a></p> <h2>v4.10.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.10.0">https://github.com/sass/node-sass/releases/tag/v4.10.0</a></p> <h2>v4.9.4</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.4">https://github.com/sass/node-sass/releases/tag/v4.9.4</a></p> <h2>v4.9.3</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.3">https://github.com/sass/node-sass/releases/tag/v4.9.3</a></p> <h2>v4.9.2</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.2">https://github.com/sass/node-sass/releases/tag/v4.9.2</a></p> <h2>v4.9.1</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.1">https://github.com/sass/node-sass/releases/tag/v4.9.1</a></p> <h2>v4.9.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.0">https://github.com/sass/node-sass/releases/tag/v4.9.0</a></p> <h2>v4.8.3</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.8.3">https://github.com/sass/node-sass/releases/tag/v4.8.3</a></p> <h2>v4.8.2</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.8.2">https://github.com/sass/node-sass/releases/tag/v4.8.2</a></p> <h2>v4.8.1</h2> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sass/node-sass/commit/01db05182b69dccbd43be777e6808045e71af0b5"><code>01db051</code></a> 4.13.1</li> <li><a href="https://github.com/sass/node-sass/commit/338fd7a14d3b8bd374a382336df16f9c6792b884"><code>338fd7a</code></a> Merge pull request from GHSA-f6rp-gv58-9cw3</li> <li><a href="https://github.com/sass/node-sass/commit/c6f2e5a1643dd00105b63a638756dc99fc33c3e4"><code>c6f2e5a</code></a> doc: README example fix (<a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2787">#2787</a>)</li> <li><a href="https://github.com/sass/node-sass/commit/fbc9ff5abc72d9bc22a3b0bc9fa902fc46c980f7"><code>fbc9ff5</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2754">#2754</a> from saper/no-map-if-not-requested</li> <li><a href="https://github.com/sass/node-sass/commit/60fad5f2d92d9978af6a3d9bb29f4b0ff4a70070"><code>60fad5f</code></a> 4.13.0</li> <li><a href="https://github.com/sass/node-sass/commit/43db915c360cdd87ad433990289221879158ffdb"><code>43db915</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2768">#2768</a> from sass/release-4-13</li> <li><a href="https://github.com/sass/node-sass/commit/0c8d308fef78f25fccebe6a6f35f76489e76df04"><code>0c8d308</code></a> Update references for v4.13 release</li> <li><a href="https://github.com/sass/node-sass/commit/f1cc0d37f4b221215ea5f0be7f1c41506a3e4342"><code>f1cc0d3</code></a> Use GCC 6 for Node 12 binaries (<a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2767">#2767</a>)</li> <li><a href="https://github.com/sass/node-sass/commit/3838eae74ff1d4d2d37b80b20b30f8a0f42f3e3c"><code>3838eae</code></a> Use GCC 6 for Node 12 binaries</li> <li><a href="https://github.com/sass/node-sass/commit/e84c6a9f8d62b27174d650c38d18b327c97753ba"><code>e84c6a9</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2766">#2766</a> from saper/node-modules-79</li> <li>Additional commits viewable in <a href="https://github.com/sass/node-sass/compare/v3.13.1...v4.13.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+167 -121

0 comment

2 changed files

dependabot[bot]

pr closed time in 23 days

startedbitworking/CSS3D

started time in 23 days

push eventAlexisTM/flyingros

dependabot[bot]

commit sha 3f59fb98cf8f26c0a39476c3e3d5c6ddb176fbdc

Bump node-sass from 3.13.1 to 4.14.1 in /flyingros_web/www (#5) Bumps [node-sass](https://github.com/sass/node-sass) from 3.13.1 to 4.14.1. - [Release notes](https://github.com/sass/node-sass/releases) - [Changelog](https://github.com/sass/node-sass/blob/master/CHANGELOG.md) - [Commits](https://github.com/sass/node-sass/compare/v3.13.1...v4.14.1) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

push time in 23 days

PR merged AlexisTM/flyingros

Bump node-sass from 3.13.1 to 4.14.1 in /flyingros_web/www dependencies

Bumps node-sass from 3.13.1 to 4.14.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sass/node-sass/releases">node-sass's releases</a>.</em></p> <blockquote> <h2>v4.14.1</h2> <h3>Community</h3> <ul> <li>Add GitHub Actions for Alpine CI (<a href="https://github.com/nschonni">@nschonni</a>, <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2823">#2823</a>)</li> </ul> <h3>Fixes</h3> <ul> <li>Bump sass-graph@2.2.5 (<a href="https://github.com/xzyfer">@xzyfer</a>, <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2912">#2912</a>)</li> </ul> <h2>Supported Environments</h2> <table> <thead> <tr> <th>OS</th> <th>Architecture</th> <th>Node</th> </tr> </thead> <tbody> <tr> <td>Windows</td> <td>x86 & x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14</td> </tr> <tr> <td>OSX</td> <td>x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14</td> </tr> <tr> <td>Linux*</td> <td>x86 & x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^, 13**^, 14**^</td> </tr> <tr> <td>Alpine Linux</td> <td>x64</td> <td>6, 8, 10, 11, 12, 13, 14</td> </tr> <tr> <td>FreeBSD</td> <td>i386 amd64</td> <td>10, 12, 13</td> </tr> </tbody> </table> <p>Linux support refers to Ubuntu, Debian, and CentOS 5+ ** Not available on CentOS 5 ^ Only available on x64</p> <h2>v4.14.0</h2> <h3>Features</h3> <ul> <li>Add Node 14 support (<a href="https://github.com/nschonni">@nschonni</a>, <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2895">#2895</a>)</li> </ul> <h3>Fixes</h3> <ul> <li>Reporting wrong LibSass version (<a href="https://github.com/saper">@saper</a>, <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2621">#2621</a>)</li> </ul> <h2>Supported Environments</h2> <table> <thead> <tr> <th>OS</th> <th>Architecture</th> <th>Node</th> </tr> </thead> <tbody> <tr> <td>Windows</td> <td>x86 & x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14</td> </tr> <tr> <td>OSX</td> <td>x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14</td> </tr> <tr> <td>Linux</td> <td>x86 & x64</td> <td>0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^, 13**^, 14**^</td> </tr> <tr> <td>Alpine Linux</td> <td>x64</td> <td>6, 8, 10, 11, 12, 13, 14</td> </tr> <tr> <td>FreeBSD</td> <td>i386 amd64</td> <td>10, 12, 13</td> </tr> </tbody> </table> <p>*Linux support refers to Ubuntu, Debian, and CentOS 5+ ** Not available on CentOS 5 ^ Only available on x64</p> <h2>v4.13.1</h2> <h3>Community</h3> <ul> <li>Fix render example syntax (<a href="https://github.com/ZoranPandovski">@ZoranPandovski</a> , <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2787">#2787</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/sass/node-sass/blob/master/CHANGELOG.md">node-sass's changelog</a>.</em></p> <blockquote> <h2>v4.14.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.14.0">https://github.com/sass/node-sass/releases/tag/v4.14.0</a></p> <h2>v4.13.1</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.13.1">https://github.com/sass/node-sass/releases/tag/v4.13.1</a></p> <h2>v4.13.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.13.0">https://github.com/sass/node-sass/releases/tag/v4.13.0</a></p> <h2>v4.12.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.12.0">https://github.com/sass/node-sass/releases/tag/v4.12.0</a></p> <h2>v4.11.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.11.0">https://github.com/sass/node-sass/releases/tag/v4.11.0</a></p> <h2>v4.10.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.10.0">https://github.com/sass/node-sass/releases/tag/v4.10.0</a></p> <h2>v4.9.4</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.4">https://github.com/sass/node-sass/releases/tag/v4.9.4</a></p> <h2>v4.9.3</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.3">https://github.com/sass/node-sass/releases/tag/v4.9.3</a></p> <h2>v4.9.2</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.2">https://github.com/sass/node-sass/releases/tag/v4.9.2</a></p> <h2>v4.9.1</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.1">https://github.com/sass/node-sass/releases/tag/v4.9.1</a></p> <h2>v4.9.0</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.9.0">https://github.com/sass/node-sass/releases/tag/v4.9.0</a></p> <h2>v4.8.3</h2> <p><a href="https://github.com/sass/node-sass/releases/tag/v4.8.3">https://github.com/sass/node-sass/releases/tag/v4.8.3</a></p> <h2>v4.8.2</h2> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sass/node-sass/commit/0d6c3cc36a5362e83529d901484b0bbf3e96de81"><code>0d6c3cc</code></a> 4.14.1</li> <li><a href="https://github.com/sass/node-sass/commit/1cc626373196500b288f487e1507926066f3e406"><code>1cc6263</code></a> Bump sass-graph@2.2.5 (<a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2915">#2915</a>)</li> <li><a href="https://github.com/sass/node-sass/commit/aa193f6334e45ae065cc64d67498acfad9fad4d9"><code>aa193f6</code></a> chore: Add GitHub Actions for Alpine CI</li> <li><a href="https://github.com/sass/node-sass/commit/eac343c6cc39abff153b2c8e9cc0d6b8351c8a8f"><code>eac343c</code></a> 4.14.0</li> <li><a href="https://github.com/sass/node-sass/commit/bbeb78cab873b12fc4b98358b62090e6fbc9b400"><code>bbeb78c</code></a> Update changelog</li> <li><a href="https://github.com/sass/node-sass/commit/1210aabc65ed445263dac5041ad735e3a35ae600"><code>1210aab</code></a> Fix <a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2621">#2621</a>: Report libsass version 3.5.5 (<a href="https://github-redirect.dependabot.com/sass/node-sass/issues/2769">#2769</a>)</li> <li><a href="https://github.com/sass/node-sass/commit/5a4a48a4a45f41d66d55e2103496e886ec7ee5f1"><code>5a4a48a</code></a> feat: Add Node 14 support</li> <li><a href="https://github.com/sass/node-sass/commit/b54053a1b50fd97e951eb0311a7fb818683a8e99"><code>b54053a</code></a> Update changelog</li> <li><a href="https://github.com/sass/node-sass/commit/01db05182b69dccbd43be777e6808045e71af0b5"><code>01db051</code></a> 4.13.1</li> <li><a href="https://github.com/sass/node-sass/commit/338fd7a14d3b8bd374a382336df16f9c6792b884"><code>338fd7a</code></a> Merge pull request from GHSA-f6rp-gv58-9cw3</li> <li>Additional commits viewable in <a href="https://github.com/sass/node-sass/compare/v3.13.1...v4.14.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+1 -1

0 comment

1 changed file

dependabot[bot]

pr closed time in 23 days

startedkendryte/kendryte-freertos-sdk

started time in 23 days

startedsipeed/platform-kendryte210

started time in 24 days

startedkendryte/kendryte-gnu-toolchain

started time in 24 days

issue commentPX4/Firmware

Estimation drifting with GPS & Vision Velocity

Maybe you are looking for ecl, the estimation library used for estimation?

nbelanger99

comment created time in 25 days

issue openedPX4/Firmware

USB connection is only accessible if connected in a window of few seconds

Describe the bug

If we do not connect the USB to a consumer right after the bootloader, once the RGB LED starts breathing blue (in a window of few seconds), the Pixhawk is inaccessible, no message can be received or sent anymore, but the TTY ACM driver is still up and running, thinking it can communicate.

I could replicate the exact same behavior going one level down, using libusb1.0 instead of using the kernel usb-cdc-acm driver but the exact same behavior happened. This seems to indicate that the last burst would come from the Pixhawk's buffer and not the tty driver buffer. As the log shows below, if nobody subscribes to the data in /dev/ttyACM0, the USB connection is not initialized.

To Reproduce Steps to reproduce the behavior:

  1. Power the Pixhawk with the USB
  2. Wait for the LED to be blue breathing
  3. Wait an additional 10 seconds
  4. Try to connect Mavros, QGc or cat /dev/ttyACM0
  5. When connecting, few messages are received
  6. The connection hangs: No message can be sent or received

Steps to reproduce the behavior after successful connection:

  1. Power the Pixhawk with the USB
  2. Wait for the LED to be blue breathing
  3. ~Wait an additional 10 seconds~
  4. Try to connect Mavros, QGc or cat /dev/ttyACM0
  5. The connection is successful and can be used for any time you want
  6. Disconnect (stop the node)
  7. Wait 10 seconds
  8. Try to reconnect with the same method
  9. When connecting, few messages are received
  10. The connection hangs: No message can be sent or received

Expected behavior

Steps to reproduce the behavior after successful connection:

  1. Power the Pixhawk with the USB
  2. Wait for the LED to be blue breathing
  3. You can wait any time you want before connecting
  4. Try to connect Mavros, QGc or cat /dev/ttyACM0
  5. The connection is successful and can be used for any time you want

Log Files and Screenshots

sudo apt install vusb-analyzer usbmon

Following a USB log file showing the problem. The Pixhawk in this log is DEV 1018. To view it, download it, rename it to remove the .txt and open it with vusb-analyzer:

usbmon.mon.txt

mv usbmon.mon.txt usbmon.mon # .mon files are not supported on Github
vusb-analyzer usbmon.mon

History of the log:

  • 0.00s: Start the log
  • 6.00s: Connect Pixhawk
  • 12.50s: Pixhawk left the Bootloader (CDC driver advertised)
  • 13.50s: Mavlink node started on /dev/ttyACM0 (showing normal behavior)
  • 21.25s: Mavlink node manually stopped
  • 37.70s: Mavlink node started on /dev/ttyACM0 (showing a stuck behavior)
    • The messages do contain data

Normal start: image

Failing start: image

To reproduce the log:

sudo su
modprobe usbmon
cat /sys/kernel/debug/usb/usbmon/1u > usbmon.mon

Drone:

  • Pixhawk 1 (original 3DR)
  • Firmware: px4_fmuv2_default

created time in 25 days

startedmicro-ROS/micro_ros_setup

started time in a month

issue commentinertialsense/inertial-sense-sdk

Two units with identical configuration gives different results

As I could not get a proper fix, this was without RTK and without compassing (Same condition as the reference).

AlexisTM

comment created time in a month

issue commentinertialsense/inertial-sense-sdk

Two units with identical configuration gives different results

I added the ground planes, which indeed improved the GPS signal.

Yet, I could not get an RTK fix nor robust RTK compassing, with the ambiguity resolution ratio never reaching over 1 or 2. When compassing (baseline of 1m), the measured distance was oscillating from 0.6m to 1.8m.

Here-under, the top plots are from the µINS3 (top left) and EVB-2 (top right). The data comes from DID_INS_1 and is converted to from NED to ENU. The bottom (orange) plot is from our reference.

Comparison of X-Y estimation

Here-under, the GPS_POS_1 position output from the EVB-2 (pink), the µINS3 (purple) and our reference (yellow) for the same track. The graph looks stretched on the x-axis as it is longitude & latitude.

Comparison of Lat-Lon

We can see one big jumps of position in the estimation for the µINS3 and a very very bad estimation for the EVB-2.

It is to note that the yaw (heading) of the EVB-2 was far (20°) from the estimation from both the µINS, our reference and a competitor with at worse almost 30° off. This can easily explain the bad EKF output.

AlexisTM

comment created time in a month

issue commentinertialsense/inertial-sense-sdk

Add the device serial to the USB descriptor

Yes we can work around it, it is mainly for simplicity for the users later on; allowing to connect multiple devices for testing purpose.

AlexisTM

comment created time in a month

issue commentmavlink/MAVSDK

Who should initiate TIMESYNC?

@JonasVautherin I fully agree, this protocol was designed out of necessity for a time synchronization between two devices to allow better control.

I believe it is useless in most of the use-cases and instead will be a problem to the user if multiple endpoints are connected.

TIMESYNC only works if:

  • There are only two devices
  • The synchronization time is computed & filtered in each receiving end (the pixhawk for vision estimation input & the computer for position output)
  • The link should be high speed with low jitter, probably only using hardware serial (USB-Serial has up to 20ms spikes)
JonasVautherin

comment created time in a month

push eventTheKobiThirdParty/robosense

Alexis Paques

commit sha 318362405606d41810ba4c22628b50b9af0333a2

Remove pcap find_package.

view details

push time in a month

push eventTheKobiThirdParty/robosense

Alexis Paques

commit sha bdf181f70ced849fc699dacd41a9f293646dcd4b

Fix the readme

view details

push time in a month

create barnchTheKobiThirdParty/robosense

branch : master

created branch time in a month

created repositoryTheKobiThirdParty/robosense

Robosense rs_driver as a catkin package

created time in a month

issue commentmavlink/MAVSDK

Who should initiate TIMESYNC?

I am personally not using MAVSDK at the moment.

But indeed, it would make sense to have it disabled by default as only experienced users make use offboard control and need Timesync. I would either auto-enable timesync if the user enables advanced functions or give a feedback that timesync is not enabled. (advanced usage would be offboard control or external vision)

JonasVautherin

comment created time in a month

issue commentmavlink/MAVSDK

Who should initiate TIMESYNC?

This is the same implementation as in MAVROS:

For the FCU to sync, the FCU sends a message and waits for the onboard computer to answer. For the onboard computer to sync, it sends a message and waits for the FCU's answer.

This could be in tri-way protocol two-way, where the onboard computer sends a request, FCU replies and the onboard answers to the FCU. The onboard computer will have its sync from the 2 first messages, the FCU from the 3 last messages. This would remove one message but add one time to the TIMESYNC message. I do not know it would improve bandwidth. Mavros implementation:

[Replies] https://github.com/mavlink/mavros/blob/de9f39a719b091b8448214a17d27b3b1c415d0dc/mavros/src/plugins/sys_time.cpp#L308-L321

[Requests] https://github.com/mavlink/mavros/blob/de9f39a719b091b8448214a17d27b3b1c415d0dc/mavros/src/plugins/sys_time.cpp#L334-L346

JonasVautherin

comment created time in a month

startedAuterion/mavlink-fuzz-testing

started time in a month

startedawwbees/BespokeSynth

started time in a month

create barnchTheKobiThirdParty/Firmware

branch : kobi

created branch time in a month

issue commentfacontidavide/PlotJuggler

Segmentation fault in some rare cases

Everywhere I go, I just need to touch it to break it! Brilliant! :laughing:

AlexisTM

comment created time in a month

issue commentfacontidavide/PlotJuggler

Segmentation fault in some rare cases

@facontidavide Yey! Faster than expected, adding tabs & removing tabs helped to reproduce it!

#31   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Gui.so.5", at 0x7fc8c1eaa4e0, in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
#30   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Core.so.5", at 0x7fc8c1b3426a, in QCoreApplication::notifyInternal(QObject*, QEvent*)
#29   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c24b0515, in QApplication::notify(QObject*, QEvent*)
#28   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c24ab05b, in QApplicationPrivate::notify_helper(QObject*, QEvent*)
#27   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c250ab7a, in QDesktopWidget::qt_metacall(QMetaObject::Call, int, void**)
#26   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c250891c, in QDesktopWidget::qt_metacall(QMetaObject::Call, int, void**)
#25   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c24afb31, in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool)
#24   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Core.so.5", at 0x7fc8c1b3426a, in QCoreApplication::notifyInternal(QObject*, QEvent*)
#23   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c24b0c18, in QApplication::notify(QObject*, QEvent*)
#22   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c24ab05b, in QApplicationPrivate::notify_helper(QObject*, QEvent*)
#21   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c2630ab2, in QMenu::event(QEvent*)
#20   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c24edfc7, in QWidget::event(QEvent*)
#19   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c263005f, in QMenu::mouseReleaseEvent(QMouseEvent*)
#18   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c262c0eb, in QMenu::internalDelayedPopup()
#17   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c2625e51, in QMenu::setIcon(QIcon const&)
#16   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c24a3897, in QAction::activate(QAction::ActionEvent)
#15   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Widgets.so.5", at 0x7fc8c24a1411, in QAction::triggered(bool)
#14   Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Core.so.5", at 0x7fc8c1b62a8e, in QMetaObject::activate(QObject*, int, int, void**)
#13 | Source "/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h", line 192, in impl
    | Source "/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h", line 552, in call<QtPrivate::List<>, void>
    | Source "/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h", line 495, in call
      Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/mainwindow.cpp", line 863, in operator() [0x45f64d]
#12   Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/mainwindow.cpp", line 1590, in MainWindow::loadLayoutFromFile(QString) [0x45c70b]
#11   Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/mainwindow.cpp", line 758, in MainWindow::xmlLoadState(QDomDocument) [0x458d01]
#10   Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/tabbedplotwidget.cpp", line 156, in TabbedPlotWidget::xmlLoadState(QDomElement&) [0x49248c]
#9    Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/plotmatrix.cpp", line 329, in PlotMatrix::xmlLoadState(QDomElement&) [0x486b27]
#8    Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/plotwidget.cpp", line 839, in PlotWidget::xmlLoadState(QDomElement&) [0x47f263]
#7    Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/plotwidget.cpp", line 1607, in PlotWidget::convertToXY() [0x478922]
#6    Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/plotwidget.cpp", line 1532, in PlotWidget::zoomOut(bool) [0x478002]
#5    Object "/tmp/.mount_PlotJuyhJzrR/usr/lib/libQt5Core.so.5", at 0x7fc8c1b62a8e, in QMetaObject::activate(QObject*, int, int, void**)
#4    Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/mainwindow.cpp", line 215, in MainWindow::onUndoableChange() [0x44ec2a]
#3    Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/mainwindow.cpp", line 630, in MainWindow::xmlSaveState() const [0x44bd86]
#2    Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/tabbedplotwidget.cpp", line 126, in TabbedPlotWidget::xmlSaveState(QDomDocument&) const [0x4920b9]
#1    Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/plotmatrix.cpp", line 278, in PlotMatrix::xmlSaveState(QDomDocument&) const [0x485a79]
#0    Source "/home/davide/ws_pj/src/PlotJuggler/plotter_gui/plotwidget.cpp", line 808, in PlotWidget::xmlSaveState(QDomDocument&) const [0x476438]
Segmentation fault (Address not mapped to object [0x58])
Segmentation fault
AlexisTM

comment created time in a month

issue commentfacontidavide/PlotJuggler

Segmentation fault in some rare cases

Indeed, such a weak backtrace doesn't help much.

AlexisTM

comment created time in a month

issue openedfacontidavide/PlotJuggler

Segmentation fault in some rare cases

Version: Last Ubuntu 18.04 melodic release: Version: 2.8.3-1bionic.20200801.210347

Description I got a segmentation fault when loading a layout but I cannot reproduce it.

Steps I took

  • Load data
  • Create a layout [Multiple tabs, both x-time and xy graphs with multiple graphs per page]
  • Save the layout
  • Modify the layout
  • Load the layout


#31   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6baf383b, in QApplicationPrivate::notify_helper(QObject*, QEvent*)
#30   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bc766fa, in QMenu::event(QEvent*)
#29   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bb32047, in QWidget::event(QEvent*)
#28   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bc74275, in QMenu::mouseReleaseEvent(QMouseEvent*)
#27   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bc7401f, in QMenu::leaveEvent(QEvent*)
#26   Object "/usr/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7f3e6ad758d7, in QCoreApplication::notifyInternal2(QObject*, QEvent*)
#25   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bafb65e, in QApplication::notify(QObject*, QEvent*)
#24   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6baf383b, in QApplicationPrivate::notify_helper(QObject*, QEvent*)
#23   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bc766fa, in QMenu::event(QEvent*)
#22   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bb32047, in QWidget::event(QEvent*)
#21   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bc743d2, in QMenu::mouseReleaseEvent(QMouseEvent*)
#20   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bc735aa, in QMenu::leaveEvent(QEvent*)
#19   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6bc6c0fb, in QMenu::setIcon(QIcon const&)
#18   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6baef80b, in QAction::activate(QAction::ActionEvent)
#17   Object "/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7f3e6baed121, in QAction::triggered(bool)
#16   Object "/usr/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7f3e6ada4618, in QMetaObject::activate(QObject*, int, int, void**)
#15   Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a3349a48, in main
#14   Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a3348053, in main
#13   Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a32f0153, in main
#12   Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a32ececf, in main
#11   Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a32e9aa8, in main
#10   Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a331f3ce, in main
#9    Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a33141b6, in main
#8    Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a330d4a9, in main
#7    Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a3306ed2, in main
#6    Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a33069b3, in main
#5    Object "/usr/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7f3e6ada466e, in QMetaObject::activate(QObject*, int, int, void**)
#4    Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a32e11be, in main
#3    Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a32dd8df, in main
#2    Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a331f070, in main
#1    Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a33131ba, in main
#0    Object "/opt/ros/melodic/lib/plotjuggler/PlotJuggler", at 0x55f2a3304f1d, in main
Segmentation fault (Address not mapped to object [0x58])
Segmentation fault

Note: Rename the files to .xml and .bag, they were renamed to be sharable on Github directly.

gps_review(fix_inertialsense_rev_latlon).xml.txt

turnaround_inplace.bag.txt

created time in a month

issue commentinertialsense/inertial-sense-sdk

Add the device serial to the USB descriptor

@waltjohnson I believe the best would be the serial field, accessible in the udev rule with: ATTRS{serial}=="40840"

AlexisTM

comment created time in a month

issue openedinertialsense/inertial-sense-sdk

Add the device serial to the USB descriptor

Hi,

I would like to differentiate between two devices using UDEV rules to prevent having to open the device to get information.

In the ideal case, it would be great to have the serial attribute of the device forwarded to uniquely identify them to allow symlinks such as /dev/inertialsense/40756 and /dev/inertialsense/40840, without opening the serial port.

This is useful in the case where we want to run different software over two devices where each device. The only method as of now is to open both serial devices, try to connect and get a serial and close them. When starting the second node, it will impact the first node which is already connected.

Of course, in production, if the case happens, this would be handled by a single software which can then do the discovery safely.

As of now, I am unlocked thanks to the urbnum which is respectively 6 and 9 for the EVB and µINS. The following udev rule creates a device /dev/ttyIsUins and /dev/ttyIsEvb.

SUBSYSTEMS=="usb", KERNEL=="ttyACM[0-9]*", ACTION=="add", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="6124", ATTRS{urbnum}=="9", MODE="666", SYMLINK+="ttyIsUins", GROUP="dialout"
SUBSYSTEMS=="usb", KERNEL=="ttyACM[0-9]*", ACTION=="add", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="6124", ATTRS{urbnum}=="6", MODE="666", SYMLINK+="ttyIsEvb", GROUP="dialout"

created time in a month

startedpriseborough/InertialNav

started time in a month

issue commentinertialsense/inertial-sense-sdk

Two units with identical configuration gives different results

I am not currently using a ground plane, I will add one on each antenna.

The distance between antennas is 1m for both.

AlexisTM

comment created time in 2 months

delete branch TheKobiThirdParty/InertialSenseSDK

delete branch : fix/python_log_reader_build

delete time in 2 months

PR opened inertialsense/inertial-sense-sdk

Fix the Python build by using find_package for pybind11 & fixing the paths

This allows building the Pybind11 package without the internal folder structure.

+4 -7

0 comment

1 changed file

pr created time in 2 months

create barnchTheKobiThirdParty/InertialSenseSDK

branch : fix/python_log_reader_build

created branch time in 2 months

issue commentinertialsense/inertial-sense-sdk

Two units with identical configuration gives different results

On the last in-field tests, I finally got similar results but the ambiguity resolution ratio never went higher than 2 or so for both units.

AlexisTM

comment created time in 2 months

issue closedinertialsense/inertial-sense-sdk

Where are the Python scripts located?

There are few mentions of 2 python scripts to analyze logs:

  • LogInspector.py
  • LogPlotter.py

Where are these located?

closed time in 2 months

AlexisTM

issue commentinertialsense/inertial-sense-sdk

Where are the Python scripts located?

Thanks!

AlexisTM

comment created time in 2 months

issue openedinertialsense/inertial-sense-sdk

Where are the Python scripts located?

There are few mentions of 2 python scripts to analyze logs:

  • LogInspector.py
  • LogPlotter.py

Where are these located?

created time in 2 months

issue commentinertialsense/inertial-sense-sdk

Two units with identical configuration gives different results

Both the rugged unit and the EVB-2 should be having the same perturbations, yet no received satellite goes into Float/Fix state at all on the rugged unit, even in ideal situation (open-sky, open-field). I go not a single GPS signal to Float/Fix for both compassing and position mode on the rugged unit.

AlexisTM

comment created time in 2 months

issue openedinertialsense/inertial-sense-ros

Is this intended?

https://github.com/inertialsense/inertial-sense-ros/blob/8b4c33f0a0ef4e50e4d1bd172ac4d060ff3e52d2/src/inertial_sense.cpp#L295

created time in 2 months

issue commentinertialsense/inertial-sense-sdk

Two units with identical configuration gives different results

@siddirp The µINS3 is from the µINS Dual GNSS Compass Development Kit

AlexisTM

comment created time in 2 months

issue closedinertialsense/inertial-sense-sdk

Configuration to have RTK position & RTK compassing

Hi,

What happens when we enable both compassing & RTK with an NTRIP input?

  • Compassing with moving baseline with GPS1 & GPS2 & Positioning with GPS1 & NTRIP
  • Or does it do Positioning of both GPS1-NTRIP and GPS2-NTRIP and compassing on the resulting poses
-flashconfig=RTKCfgBits=0x9
RTKCfgBits |= RTK_CFG_BITS_ROVER_MODE_RTK_POSITIONING;
RTKCfgBits |= RTK_CFG_BITS_ROVER_MODE_RTK_COMPASSING;

closed time in 2 months

AlexisTM

issue commentinertialsense/inertial-sense-sdk

Two units with identical configuration gives different results

In this setup, it was either one or the other, the firmware [1.8.2] correctly disabled POSITION if I tried to enabled 0x09.

In this case, the RTKCfgBits are 0x80008

AlexisTM

comment created time in 2 months

issue openedinertialsense/inertial-sense-sdk

Configuration to have RTK position & RTK compassing

Hi,

Is it possible to enable both RTK positioning and compassing at the same time, using an NTRIP server for positioning?

What happens when we enable both?

  • Compassing with moving baseline with GPS1 & GPS2 & Positioning with GPS1 & NTRIP
  • Or does it do Positioning of both GPS1-NTRIP and GPS2-NTRIP and compassing on the resulting poses
-flashconfig=RTKCfgBits=0x9
RTKCfgBits |= RTK_CFG_BITS_ROVER_MODE_RTK_POSITIONING;
RTKCfgBits |= RTK_CFG_BITS_ROVER_MODE_RTK_COMPASSING;

created time in 2 months

create barnchTheKobiThirdParty/pcl

branch : kobi-1.11.0

created branch time in 2 months

push eventTheKobiThirdParty/neo_usboard

Alexis Paques

commit sha 37e6d08733a103fd520c9612c4fdc388cacd705b

Fix missing dependency

view details

push time in 2 months

push eventTheKobiThirdParty/clipper2.cpp

Alexis Paques

commit sha e775fa95693a9e38d3fe625466549f0a2b417f94

Fix extension to *.h*

view details

push time in 2 months

push eventTheKobiThirdParty/clipper.cpp

Alexis Paques

commit sha 0cd43b2a4a8440072bae422318fd5798d7c2d5fb

Fix extension to *.h*

view details

push time in 2 months

startedLinzaer/Ultra-Light-Fast-Generic-Face-Detector-1MB

started time in 2 months

pull request commentPX4/Flow

Image whitening

I personally do not have a PX4 drone here, thus cannot help on it. Yet, we used this firmware quite heavily to allow low light environment.

jlecoeur

comment created time in 2 months

push eventTheKobiThirdParty/clipper.cpp

Alexis Paques

commit sha aef856dc19ed3ad1a9b01e880c511c83fc3c44a4

Fix the clipper namespace comments

view details

push time in 2 months

push eventTheKobiThirdParty/clipper.cpp

Alexis Paques

commit sha f9845d374df457a48b64681ab9116f06a9de3229

Rename ClipperStd to clipper namespace

view details

push time in 2 months

create barnchTheKobiThirdParty/clipper2.cpp

branch : master

created branch time in 2 months

push eventTheKobiThirdParty/clipper.cpp

Alexis Paques

commit sha ca55adc81a83315689c430f8c8e47cee8ee27aef

Rename ClipperLib to clipper

view details

push time in 2 months

created repositoryTheKobiThirdParty/clipper2.cpp

[Mirror] Polygon and line clipping and offsetting library - version2

created time in 2 months

push eventTheKobiThirdParty/Clipper.cpp

Alexis Paques

commit sha 4b1d747038d40eb371b988ba275864e4d79ef0fa

CRLF to LF

view details

push time in 2 months

push eventTheKobiThirdParty/Clipper.cpp

Alexis Paques

commit sha 1b859eaea96a90ccf75e50404432aa7a8f4edc6e

6.4.2, change namespace and fix endlines

view details

push time in 2 months

create barnchTheKobiThirdParty/Clipper.cpp

branch : master

created branch time in 2 months

created repositoryTheKobiThirdParty/Clipper.cpp

[Mirror] Polygon and line clipping and offsetting library

created time in 2 months

push eventAlexisTM/modalise.js

dependabot[bot]

commit sha 4c08c6fec4524d1d5a3274d5fd1022b8cf183051

Bump elliptic from 6.4.1 to 6.5.3 Bumps [elliptic](https://github.com/indutny/elliptic) from 6.4.1 to 6.5.3. - [Release notes](https://github.com/indutny/elliptic/releases) - [Commits](https://github.com/indutny/elliptic/compare/v6.4.1...v6.5.3) Signed-off-by: dependabot[bot] <support@github.com>

view details

Alexis Paques

commit sha e50ec648b7e28960bac203625db09d272194398c

Merge pull request #4 from AlexisTM/dependabot/npm_and_yarn/elliptic-6.5.3 Bump elliptic from 6.4.1 to 6.5.3

view details

push time in 2 months

PR merged AlexisTM/modalise.js

Bump elliptic from 6.4.1 to 6.5.3 dependencies

Bumps elliptic from 6.4.1 to 6.5.3. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/indutny/elliptic/commit/8647803dc3d90506aa03021737f7b061ba959ae1"><code>8647803</code></a> 6.5.3</li> <li><a href="https://github.com/indutny/elliptic/commit/856fe4d99fe7b6200556e6400b3bf585b1721bec"><code>856fe4d</code></a> signature: prevent malleability and overflows</li> <li><a href="https://github.com/indutny/elliptic/commit/60489415e545efdfd3010ae74b9726facbf08ca8"><code>6048941</code></a> 6.5.2</li> <li><a href="https://github.com/indutny/elliptic/commit/9984964457c9f8a63b91b01ea103260417eca237"><code>9984964</code></a> package: bump dependencies</li> <li><a href="https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a"><code>ec735ed</code></a> utils: leak less information in <code>getNAF()</code></li> <li><a href="https://github.com/indutny/elliptic/commit/71e4e8e2f5b8f0bdbfbe106c72cc9fbc746d3d60"><code>71e4e8e</code></a> 6.5.1</li> <li><a href="https://github.com/indutny/elliptic/commit/7ec66ffa255079260126d87b1762a59ea10de5ea"><code>7ec66ff</code></a> short: add infinity check before multiplying</li> <li><a href="https://github.com/indutny/elliptic/commit/ee7970b92f388e981d694be0436c4c8036b5d36c"><code>ee7970b</code></a> travis: really move on</li> <li><a href="https://github.com/indutny/elliptic/commit/637d0216b58de7edee4f3eb5641295ac323acadb"><code>637d021</code></a> travis: move on</li> <li><a href="https://github.com/indutny/elliptic/commit/5ed0babb6467cd8575a9218265473fda926d9d42"><code>5ed0bab</code></a> package: update deps</li> <li>Additional commits viewable in <a href="https://github.com/indutny/elliptic/compare/v6.4.1...v6.5.3">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

dependabot[bot]

pr closed time in 2 months

PR opened onlytailei/CppRobotics

Fix lattice planner segmentation fault

The location of the lookup table likely changed, causing a segmentation fault if we do not fix the path.

+1 -1

0 comment

1 changed file

pr created time in 2 months

fork AlexisTM/CppRobotics

cpp implementation of robotics algorithms including localization, mapping, SLAM, path planning and control

fork in 2 months

startedonlytailei/CppRobotics

started time in 2 months

issue commentflyingzhao/PyEVM

MemoryError

The memory consumption is huge, probably missing some memory?

HefnySco

comment created time in 2 months

startedcvg/Hierarchical-Localization

started time in 2 months

fork AlexisTM/Live-Video-Magnification

An OpenCV/Qt based realtime application for Eulerian Video Magnification / Motion Magnification. Works with multiple videos and cameras at the same time and let's you export the magnified videos.

fork in 2 months

more