| #!/usr/bin/env python | |
| ''' | |
| Simple and functional REST server for Python (2.7) using no dependencies beyond the Python standard library. | |
| Features: | |
| * Map URI patterns using regular expressions | |
| * Map any/all the HTTP VERBS (GET, PUT, DELETE, POST) | |
| * All responses and payloads are converted to/from JSON for you |
| //The source texture that will be transformed | |
| uniform sampler2D tex0; | |
| //The texture coordinate passed in from the vertex shader (the default luxe vertex shader is suffice) | |
| varying vec2 tcoord; | |
| //x: width of the texture divided by the radius that represents the top of the image (normally screen width / radius) | |
| //y: height of the texture divided by the radius representing the top of the image (normally screen height / radius) | |
| uniform vec2 sizeOverRadius; |
This document is research for the selection of a communication platform for robot-net.
The purpose of this component is to enable rapid, reliable, and elegant communication between the various nodes of the network, including controllers, sensors, and actuators (robot drivers). It will act as the core of robot-net to create a standardized infrastructure for robot control.
Requirements:
Unlike your typical computer where you usually shutdown properly, I cannot rely on this during the use of my Raspberry Pi. If the Raspberry Pi is improperly shutdown too many times, data corruption in the file system leading to unbootable SD card may result. So we should use a read-only file system.
Full instructions and explanations are obtained from this link but you can run these commands directly. I modified some of the instructions for personal convenience.
Login with default username: alarm, password: alarm
#Optionally enable root over SSH. The rest of these instructions assume u are in root.
| _____________ /\ ____________ | |
| /\_ _ __ ___ \ \/ / __ _ _ __ / |_ | |
| / /_)/ '__/ _ \ \ / / _` | '_ \| __| | |
| / ___/| | | (_) \ \/ / (_| | | | | |_ | |
| \/ |_| \___/ \__/ \__,_|_| |_|\__| |
Simple way to setup an arm chroot for building packages for your arm devices. This is an alternative to cross-compiling where you are limited to only linking against the libs in your toolchain.
You can store the chroot wherever you like. I choose to store it in a disk-image which I mount to my filesystem.
| git clean -xfd | |
| git submodule foreach --recursive git clean -xfd | |
| git reset --hard | |
| git submodule foreach --recursive git reset --hard | |
| git submodule update --init --recursive |
| // This file is hereby released into the public domain. | |
| // This code contains a skeleton for Keypoint Object Matching with SURF/BRISK | |
| // It was extracted from the code of an unreleased demo - https://www.youtube.com/watch?v=-r9J1eO4qg4 | |
| // It will not compile as-is, but may function as a starting point. | |
| #include <set> | |
| #include <string> | |
| #include <opencv2/core/core.hpp> | |
| #include <opencv2/imgproc/imgproc.hpp> | |
| #include "Freenect.hpp" |
People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
A lot of math grad school is reading books and papers and trying to understand what's going on. The difficulty is that reading math is not like reading a mystery thriller, and it's not even like reading a history book or a New York Times article.
The main issue is that, by the time you get to the frontiers of math, the words to describe the concepts don't really exist yet. Communicating these ideas is a bit like trying to explain a vacuum cleaner to someone who has never seen one, except you're only allowed to use words that are four letters long or shorter.
What can you say?