Jiho Choi JihoChoi

This gist lets you keep IPython notebooks in git repositories. It tells git to ignore prompt numbers and program outputs when checking that a file has changed.

To use the script, follow the instructions given in the script's docstring.

For further details, read this blogpost.

The procedure outlined here is inspired by this answer on Stack Overflow.

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

Markdown License badges

Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.

Notes

The badges do not fully replace the license informations for your projects, they are only emblems for the README, that the user can see the License at first glance.

Translations: (No guarantee that the translations are up-to-date)

🇫🇷 Cette liste en français

Commit Message Guidelines

In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.

This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.

Goals
Proposal
- Commit Message Format

Allowed ``

The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.

The correct way of creating a private frok by duplicating the repo is documented here.

For this assignment the commands are:

Create a bare clone of the repository. (This is temporary and will be removed so just do it wherever.)

git clone --bare [email protected]:usi-systems/easytrace.git

	import sys
	import numpy as np
	import networkx as nx
	import matplotlib.pyplot as plt

	def plot(data,filename,degreetype):
	""" Plot Distribution """
	plt.plot(range(len(data)),data,'bo')
	plt.yscale('log')
	plt.xscale('log')

	from igraph import *
	import numpy as np

	# Create the graph
	vertices = [i for i in range(7)]
	edges = [(0,2),(0,1),(0,3),(1,0),(1,2),(1,3),(2,0),(2,1),(2,3),(3,0),(3,1),(3,2),(2,4),(4,5),(4,6),(5,4),(5,6),(6,4),(6,5)]

	g = Graph(vertex_attrs={"label":vertices}, edges=edges, directed=True)

	visual_style = {}

	1. Go to Sublime Text to: Tools -> Build System -> New Build System
	and put the next lines:

	{
	"cmd": ["python3", "-i", "-u", "$file"],
	"file_regex": "^[ ]File \"(...?)\", line ([0-9]*)",
	"selector": "source.python"
	}

	Then save it with a meaningful name like: python3.sublime-build

	<!DOCTYPE HTML>
	<html lang="en">
	<head>
	<title>Record WebGL to WebM (Chrome only)</title>
	<meta charset="utf-8">
	<link rel="stylesheet" href="styles.css" charset="utf-8">
	</head>
	<body>

	<div class="buttons">

	#!/usr/bin/env python
	'''
	Permission is hereby granted, free of charge, to any person obtaining a
	copy of this software and associated documentation files (the "Software"),
	to deal in the Software without restriction, including without limitation
	the rights to use, copy, modify, merge, publish, distribute, sublicense,
	and/or sell copies of the Software, and to permit persons to whom the
	Software is furnished to do so, subject to the following conditions:

	The above copyright notice and this permission notice shall be included in