- Lots of red on the index with two login/register buttons and the task box highlight. I'd drop it from the task box, after the first task is added they know it's important.
- I didn't immediately figure out that I put things "In Progress" by dragging them below the marker. Maybe more of a "line" across the column and going through the words "In Progress"
- I thought the arrow ("play button") was going to expand the box to show more details, whups
- Created a task, got "21" in the corner. My thought process: "Eh, what's 21?", double click, "the task number? Who cares about task numbers?"
- Help for task bar should have complete examples. Maybe a light box with a 15 second video, "Just enter XYZ in the task bar and it gets put into X project and assigned to Z"
- What about some way to indicate the ones I've most recently looked at? Most recently added? Thinking about a UI kinda like when you go to System Prefs on Mac OS then enter a term in the search box.
P1 -> propeller(:motor) | |
P2 -> led | |
P3, P4 <-> xbee(:serial) | |
P6 <- button(:button) | |
P7 <- thermometer(:analog) | |
every 100ms do | |
if button.pushed | |
led.off | |
end |
- Whisky notes: http://www.whisky-pages.com/ | |
*** http://weka.wikispaces.com/Use+Weka+in+your+Java+code | |
- http://cran.r-project.org/web/views/Bayesian.html - a metric shit tonne of packages for R | |
- http://www.celiagreen.com/charlesmccreery/statistics/bayestutorial.pdf - Greate illustrated guide to bayesian trees | |
- http://www.cs.waikato.ac.nz/~remco/weka_bn/bayesnet.html | |
- http://en.wikipedia.org/wiki/Chain_rule_(probability) - Chain Rule of probablity | |
- http://aima.cs.berkeley.edu/ - AI a Modern Approach (full HTML online) | |
- http://www.labmedinfo.org/sites/default/files/file/publications/lmi339.pdf - Hierarchical Bayes Clasifiers for Uncertain Data | |
- http://people.csail.mit.edu/jrennie/papers/icml03-nb.pdf - Naieve Bayes Text Classifiers | |
- https://www.cra.com/pdf/bnetbuilderbackground.pdf - |
machine github.com | |
login technoweenie | |
password SECRET | |
machine api.github.com | |
login technoweenie | |
password SECRET |
<?php | |
# Example create project on kanbanpad api using json | |
# Runs on PHP 5.3 with curl and json extension | |
# Note the https, the s is required. | |
$curl = curl_init("https://www.kanbanpad.com/api/v1/projects.json"); | |
curl_setopt($curl, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); | |
curl_setopt($curl, CURLOPT_USERPWD, '[email protected]:e754f5335230f9bad9b5dc90ceb5ab0c76a06604'); | |
curl_setopt($curl, CURLOPT_RETURNTRANSFER, true); | |
curl_setopt($curl, CURLOPT_POST, 1); |
#!/bin/bash | |
# play YUV444 FULL HD file | |
gst-launch-1.0 -v filesrc location=size_1920x1080.yuv ! \ | |
videoparse width=1920 height=1080 framerate=25/1 format=GST_VIDEO_FORMAT_Y444 ! \ | |
videoconvert ! \ | |
autovideosink | |
# play YUV422 FULL HD file | |
gst-launch-1.0 -v filesrc location=size_1920x1080.yuv ! \ |
It is not necessary to use the Eclipse environment in order to compile code for the Intel Edison. Command line compilation is possible on all platforms and is relatively straightforward. For linux and OS/X the simplest method is to download the SDK for the respective platform and setup as described below. Although Intel lists SDKs for both 32 and 64 bit Windows, I find it simpler to setup command line compilation from the integrated IOT platform installation.
All three platforms use the GNU compiler tools (gcc, g++, and friends) and the main differences really come down to differences in the command shell usage. Consequently, the procedures have the following common elements.
- Install the cross compilation tool chain and library file-system.
- Setup the path so that the operating system can find the compilers and other utilities.
- Setup environment variables to simplify the command line and tell the compilers where to find librari
At Vimeo, on the transcoding team, we work a lot with Go, and a lot with C, for various tasks such as media ingest. This means we use CGO quite extensively, and consequently, have run into bits that are perhaps not very well documented, if at all. Below is my effort to document some of the problems we've run into, and how we fixed or worked around them.
Many of these are obviously wrong in retrospect, but hindsight is 20/20, and these problems do exist in many codebases currently.
Some are definitely ugly, and I much welcome better solutions! Tweet me at @daemon404 if you have any, or have your own CGO story/tips, please! I'd love to learn of them.
Table of Contents
""" | |
edges.py: Canny, Prewitt and Sobel Edge detection using opencv | |
""" | |
__author__ = "K.M. Tahsin Hassan Rahit" | |
__email__ = "[email protected]" | |
import cv2 | |
import numpy as np | |
img = cv2.imread('messi5.jpg') |
#!/bin/bash | |
###AUTHOR### | |
#Harry Dove-Robinson 5/8/2017 | |
#[email protected] | |
#https://gist.github.com/hdoverobinson | |
#https://github.com/hdoverobinson | |
###USAGE### | |
#This is a script used to configure u-blox GPS/GNSS modules from a text file generated by u-center. |