| #!/usr/bin/env python3 | |
| # -*- coding: utf-8 -*- | |
| import sys | |
| import math | |
| import numpy as np | |
| sys.path.append('xgboost/wrapper/') | |
| import xgboost as xgb |
LLDB comes with a great set of commands for powerful debugging.
Your starting point for anything. Type help to get a list of all commands, plus any user installed ones. Type 'help for more information on a command. Type help to get help for a specific option in a command too.
Around 2006-2007, it was a bit of a fashion to hook lava lamps up to the build server. Normally, the green lava lamp would be on, but if the build failed, it would turn off and the red lava lamp would turn on.
By coincidence, I've actually met, about that time, (probably) the first person to hook up a lava lamp to a build server. It was Alberto Savoia, who'd founded a testing tools company (that did some very interesting things around generative testing that have basically never been noticed). Alberto had noticed that people did not react with any urgency when the build broke. They'd check in broken code and go off to something else, only reacting to the breakage they'd caused when some other programmer pulled the change and had problems.
| import numpy as np | |
| def crappyhist(a, bins=50, width=140): | |
| h, b = np.histogram(a, bins) | |
| for i in range (0, bins): | |
| print('{:12.5f} | {:{width}s} {}'.format( | |
| b[i], | |
| '#'*int(width*h[i]/np.amax(h)), | |
| h[i], |
| # Author: HJ van Veen <[email protected]> | |
| # Description: Experiment to learn a tSNE transformer for new | |
| # test data with a multi-output GBM | |
| # | |
| # Idea first seen at lvdmaaten.github.io/tsne | |
| # > [...] it is not possible to embed test points in an existing | |
| # > map [...] | |
| # > A potential approach to deal with this would be to train | |
| # > a multivariate regressor to predict the map location from | |
| # > the input data. |
| import cheerio from 'cheerio-without-node-native'; | |
| const convertRequestBodyToFormUrlEncoded = (data) => { | |
| const bodyKeys = Object.keys(data); | |
| const str = []; | |
| for (let i = 0; i < bodyKeys.length; i += 1) { | |
| const thisKey = bodyKeys[i]; | |
| const thisValue = data[thisKey]; | |
| str.push(`${encodeURIComponent(thisKey)}=${encodeURIComponent(thisValue)}`); |
| #!/bin/python3 | |
| # Largely copied from http://www.mathewinkson.com/2015/03/delete-old-tweets-selectively-using-python-and-tweepy | |
| # However, Mathew's script cannot delete tweets older than something like a year (these tweets are not available from the twitter API) | |
| # This script is a complement on first use, to delete old tweets. It uses your twitter archive to find tweets' ids to delete | |
| # How to use it : | |
| # - download and extract your twitter archive (tweet.js will contain all your tweets with dates and ids) | |
| # - put this script in the extracted directory | |
| # - complete the secrets to access twitter's API on your behalf and, possibly, modify days_to_keep | |
| # - delete the few junk characters at the beginning of tweet.js, until the first '[' (it crashed my json parser) | |
| # - review the script !!!! It has not been thoroughly tested, it may have some unexpected behaviors... |
