Mani Kumar manid2

travis-local.md

Preconditions:

POSIX or Windows system

Install Docker

A GitHub repo that already builds on Travis

Postcondition:

Debugging Travis CI locally using Docker

This assumes you've got docker-machine installed, running, and can do docker run

1. Get a debug instance running

    docker run --name travis-debug -dit quay.io/travisci/travis-ruby /sbin/init
    docker exec -it travis-debug bash -l

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

Gil Levi and Tal Hassner, Emotion Recognition in the Wild via Convolutional Neural Networks and Mapped Binary Patterns

Convolutional neural networks for emotion classification from facial images as described in the following work:

Gil Levi and Tal Hassner, Emotion Recognition in the Wild via Convolutional Neural Networks and Mapped Binary Patterns, Proc. ACM International Conference on Multimodal Interaction (ICMI), Seattle, Nov. 2015

Project page: http://www.openu.ac.il/home/hassner/projects/cnn_emotions/

If you find our models useful, please add suitable reference to our paper in your work.

Branching

Quick Legend

Description, Instructions, Notes

Instance	Branch

Workflows for long-running feature branches

These examples were created during a discussion with j416 on #github about how best to manage long-running feature branches.

The scenario is this: You have a long-running feature branch, based off master. The feature branch and master both touch the same parts of the same files, so you know that there will be conflicts when you finally merge the feature branch in. What can you do to minimise the conflicts?

	#!/usr/bin/env bash
	#
	# gh-dl-release! It works!
	#
	# This script downloads an asset from latest or specific Github release of a
	# private repo. Feel free to extract more of the variables into command line
	# parameters.
	#
	# PREREQUISITES
	#

	# Ruby is our language as asciidoctor is a ruby gem.
	lang: ruby
	before_install:
	- sudo apt-get install pandoc
	- gem install asciidoctor
	script:
	- make
	after_success:
	- .travis/push.sh
	env:

	# ~/.config/ReText project/ReText.conf

	[General]
	autoSave=true
	restorePreviewState=true
	highlightCurrentLine=true
	tabWidth=2
	styleSheet=github.css
	useWebKit=true
	autoPlainText=false

	<?xml version="1.0" encoding="utf-8"?>
	<layer-list xmlns:android="http://schemas.android.com/apk/res/android" >

	<!-- Drop Shadow Stack -->
	<item>
	<shape>
	<padding
	android:bottom="1dp"
	android:left="1dp"
	android:right="1dp"