goldbattle

From Hans Kumar to Everyone: 10:13 AM Hi Great Talk! I always have trouble picking the delta parameter for the RPE metric. Any intuition on how to pick this?

• Normally this is tied to what you want “to look at”. For example, a short length of a meter might be enough if you just care about odometry accuracy while longer lengths can evaluate the long-term performance. Generally speaking the max length should be much smaller than the total trajectory length since one would want to get multiple samples of the same length over the whole trajectory.
• Generally, what one cares about is the “trend” in the RPE. Is the algorithm always better at all lengths? For loop-closure methods is the RPE the same over all segment lengths? What is the expected accuracy if the robot travels a given distance?

---

From Ran Cheng to Everyone: 10:14 AM can we use deep nets on vison to do initialization and complementary of the missing Do for of imu. for example we can always estimate the opposite of gravity direction by a rgb

goldbattle

<launch>


    <!-- MASTER NODE! -->
    <node name="run_serial_msckf" pkg="ov_msckf" type="run_serial_msckf" output="screen" clear_params="true" required="true">

        <!-- bag topics -->
        <param name="topic_imu"      type="string" value="/uav1/vio/imu" />
        <param name="topic_camera0"  type="string" value="/uav1/vio/camera/image_raw" />

goldbattle

<launch>

    <!-- mono or stereo and what ros bag to play -->
    <arg name="max_cameras" default="2" />
    <arg name="use_stereo"  default="true" />

    <!-- imu starting thresholds -->
    <arg name="init_window_time"  default="0.5" />
    <arg name="init_imu_thresh"   default="0.5" />

goldbattle

<launch>

    <!-- mono or stereo and what ros bag to play -->
    <arg name="max_cameras" default="2" />
    <arg name="use_stereo"  default="true" />

    <!-- imu starting thresholds -->
    <arg name="init_window_time"  default="0.75" />
    <arg name="init_imu_thresh"   default="0.75" />

goldbattle

# Universal rule for GX3/4/5 devices
#SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{product}=="Lord Inertial Sensor", SYMLINK="microstrain", MODE="0666"

# Vendor/Product-locked rules for GX3/4/5 devices
#SUBSYSTEM=="tty", ATTRS{idVendor}=="199b", ATTRS{idProduct}=="3065", SYMLINK="microstrain", MODE="0666"
#SUBSYSTEM=="tty", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5740", SYMLINK="microstrain", MODE="0666"

# Uncomment these rules if you'd like the serial number to appear in the symlink.  Useful if you have multiple devices.
SUBSYSTEM=="tty", ATTRS{idVendor}=="199b", ATTRS{idProduct}=="3065", SYMLINK+="microstrain_%s{serial}", MODE="0666"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5740", SYMLINK+="microstrain_%s{serial}", MODE="0666"

goldbattle

D = sym('D',[3,3])
d = sym('d',[3,1])
lambda = sym('lambda');
g = sym('g');

assume(D,'real')
assume(d,'real')
assume(lambda,'real')
assume(g,'real')

goldbattle

// ==UserScript==
// @name         HN Favicons
// @namespace    https://campital.xyz/
// @version      0.3.1
// @license MIT
// @description  Favicons for Hacker News
// @match        https://*.ycombinator.com/*
// @grant        GM.addElement
// ==/UserScript==

goldbattle

from igraph import *

# Create graph
g = Graph(directed=True)

# Add 5 vertices
g.add_vertices(5)

# Add ids and labels to vertices
for i in range(len(g.vs)):

goldbattle

"""
Drawers for various edge styles in graph plots.
"""

__all__ = (
    "AbstractEdgeDrawer",
    "AlphaVaryingEdgeDrawer",
    "ArrowEdgeDrawer",
    "DarkToLightEdgeDrawer",
    "LightToDarkEdgeDrawer",

goldbattle

#!/usr/bin/bash


# Tailscale install on comma3
# https://discord.com/channels/469524606043160576/524594418628558878/946342467307974658

# tested over comma serial, might need sudo otherwise...
sudo mount -o remount,rw /
curl -fsSL https://tailscale.com/install.sh | sh
sudo sed -i 's/--state=\/var\/lib\/tailscale\/tailscaled\.state --socket=\/run\/tailscale\/tailscaled\.sock /--state=\/data\/tailscaled.state /g' /lib/systemd/system/tailscaled.service