The following guide describes how to setup Raspberry Pi to connect to Wifi. It was tested on the following environment:
- Raspberry Pi Model B
- Edimax EW-7811Un USB Wifi dongle
- OS: Raspbian Jessie
Here are the overview of the steps:
| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd" /> | |
| <html> | |
| <head> | |
| <title>LIGO CIT Journal Club</title> | |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15" /> | |
| </head> | |
| <body> | |
| <h1><a href="https://wiki-40m.ligo.caltech.edu/Journal_Club">LIGO CIT Journal Club</a></h1> | |
| <h2>Upcoming presenters:</h2> |
| #!/bin/bash | |
| # This gist contains pre-commit hooks to prevent you from commiting bad code or to the wrong branch. | |
| # There are six variants that I have built: | |
| # - pre-commit: stops commits to master/main/develop branches. | |
| # - pre-commit-2: also includes a core.whitespace check. | |
| # - pre-commit-3: the core.whitespace check and an EOF-newline-check. | |
| # - pre-commit-4: only the core.whitespace check. | |
| # - pre-commit-5: elixir formatting check. | |
| # - pre-commit-6: prettier formatting check. | |
| # Set the desired version like this before proceeding: |
| " Use Vim settings, rather then Vi settings (much better!). | |
| " This must be first, because it changes other options as a side effect. | |
| set nocompatible | |
| " ================ General Config ==================== | |
| set number "Line numbers are good | |
| set backspace=indent,eol,start "Allow backspace in insert mode | |
| set history=1000 "Store lots of :cmdline history | |
| set showcmd "Show incomplete cmds down the bottom |
| """ | |
| Usage: python remove_output.py notebook.ipynb [ > without_output.ipynb ] | |
| Modified from remove_output by Minrk | |
| """ | |
| import sys | |
| import io | |
| import os | |
| from IPython.nbformat.current import read, write |
| -- DESCRIPTION -- | |
| If you accidentally commit a huge file, you have a problem. Sure, you can remove it from the working tree and commit, | |
| but the file is still reachable from your history and therefore causes every clone to be as huge as the commented | |
| binary file. | |
| Fixing this can be very ugly, time consuming and might not even work as you wish. Luckily, this script can protect | |
| you from committing such monsters in the first place. | |
| It looks through the staged files (the ones that are added with the "git add"-command) and checks for their file-size. | |
| If they are larger then the given size, the commit is aborted and you get a message telling you what file takes so |