Michael Gleicher
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Sensing Proposal Notes - mid-July [![hackmd-github-sync-badge](https://hackmd.io/4l4HXXawSiuuRhGtNtGGiA/badge)](https://hackmd.io/4l4HXXawSiuuRhGtNtGGiA) Sensing involves tradeoffs. A robot system designer must balance requirements such as power, size, weight, precision, resolution, robustness, cost, latency, and computation. WEIRD SENSORS is an emerging sensor design strategy that provides an intriguing new point in the tradeoff space: they provide benefits in terms of simplicity, and therefore power, size, cost, robustness, latency and computation needs, in trade for providing data in an non-standard format with WEIRD properties. For example, a sensor might provide a histogram of scene depth values (Sec), rather than a per-pixel depth map, or it might provide bounds on scene motion, rather than a more standard flow map (Sec). The benefit of these sensors for robotics applications is that they can provide extremely favorable properties. The problem of these sensors is that in order to use them, we must devise new approaches that make use of their unusual data types. Robotics applications often require making extreme sensor tradeoffs. For example, small and robust depths sensors would allow creating an "active skin" around an arm or snake that would allow it to navigate in an unknown confined environment; low power and computation, but high speed sensors could help a micro-drone localize; or a very low latency motion detector could help a robot safely avoid dynamic obstacles in a dangerous scenario. WEIRD SENSORS offer the potential to enable new robotics applications, however, we first must develop methods that allow robots to make use of the WEIRD DATA they provide in order to address the core challenges of robotics. In this project we will develop approaches that enable WEIRD SENSORS for robotics applications. We will use currently available sensors and common robotics problems to drive our exploration, devising not only specific solutions but also general tools that will generalize to future sensors and robotics needs. <s>Our key idea is to make use of the DATA directly, rather than trying to convert it to a more standard representation</s>. (*make the three core ideas to be "an idea"*) Project Strategy: New sensing modalities continue to appear. This includes new sensor types that will provide other kinds of WIERD DATA. Therefore, we need to develop a thorough understanding of WEIRD DATA SENSORS and how they may be used in robotics to appreciate the potential and tradeoffs these devices provide. We therefore seek to develop both solutions for current sensors, but also common strategies that may apply across sensing modalities. We seek to address both some current specific robotics needs, but also to develop common strategies that will apply in future cases where extreme sensing is necessary. In this project, we propose to explore a few initial examples using current sensors and applications and to use our results in these cases to develop more generalized approaches that will transfer to future problems and sensors. WEIRD SENSORS offer a great synergy with robotics. On one hand, they offer properies that are desirable in robot sensing, including low power, low computation and communication demands, small size, and low cost. Conversely, robotics can address some of the shortcomings of the approach by being able to move the sensors in known ways, to integrate multiple sensors, and to have flexibility in the required representations. Develop three core ideas that enable robots to make use of WEIRD SENSORS: 1. A robot is able to **move the sensor**, often in known/controlled ways. By collecting measurements over time with motion, the observations may be improved and disambiguated. 2. A robot system is able to have **multiple sensors** and sources of information. A robot may use a collection of WEIRD sensors, couple these observations with data from other sensors or robots, or even prior knowledge of what is being sensed. Effectively using this information together can allow for WIERD DATA to be used despite its incompleteness and ambiguities. 3. A robot may be able to **act given imperfect data**. A robot may not need a complete detailed geometric model (the traditional representation constructed by sensing) in order to achieve its tasks. This will give new capabilities to robots... and we will demonstrate that Core capabilities/ideas: - geometric calibration - differential analysis - differential representations - signature matching - fusing multiple sensors (super-res, better localization) - robot "fear" (be conservative - stay away from bad things so they don't have all of a sudden) ## Existing sensors Emphasis: we see common challenges across the class, these "existing examples" give us something to work with now. Attractive for robots, but the big payoff is knowing how to work with these sensors 1. Depth Histograms 2. Speckle (motion magnitude detection) 3. Spots (fast position estimation) 4. **others?** Common properties: 1. ambiguity in some dimension in trade for details in another 2. **what else?** ## Core Questions: 1. How do we interpret the observations from WEIRD sensors? Inherrent ambiguity. But, it might be resolved through geometric reasoning or making multiple observations (which we can do because we have a robot). Or, we might be able to interpret things in useful ways despite the ambiguity (see #3) but only if we understand it. 2. How do we bring together observations from multiple sources? May have many WEIRD SENSORS (use as a distributed sensor), or some other sensor (high quality sensor giving a map). How do we use them together? 3. How can we act given incomplete information? Typical robotics approach is to build a detailed representation (map) of the environment. But this may be overkill. What do we really need? What can we do with the limited things that we can get? ## Robotics things: - maps for planning - depth checks for trajectory optimization - real-time movement synthesis - localization in a known map - checking of a known map (is there something that seems out of place) - exploration (incremental map construction) - tele-operation - don't need a whole map, just need to be responsive (to user and obstacles) - SPLAM - use what ever information we have to update the model (map and position), use to fill gaps in the model (if you know what is in half of a scene) - affordance identification (can we identify things with certain signatures - flat surfaces, clear places on the floor to drive on, grasp points) Three apps that align with cores? (*problems really use all core technologies*) 1. Sensitive skin that enables a robot to be reactive/teleoperated in a cluttered environment. 2. Signature matching that allows a mobile robot to localize itself and be sensitive to environment dynamics. <s>(could this be based on speckle?)</s> drone flies by and detects changes 3. SPLAM (robot tries to plan to goal - without a pre-build map, obtaining information incrementally - locally moving around but remembering where it ran into things) ## Plan Two parallel threads (1 RA for each): 1. Develop the core techniques (using sensor motion, combining sensors, applying incomplete representations) 2. Build specific robotics applications that address specific existing problems with currently available sensors ## Literature Search in abstracts viewer: planning localization and mapping

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully