git branch -f X origin/X
See : http://stackoverflow.com/questions/5667884/how-to-squash-commits-in-git-after-they-have-been-pushed
/* | |
Written by Peter O. | |
Any copyright to this work is released to the Public Domain. | |
In case this is not possible, this work is also | |
licensed under Creative Commons Zero (CC0): | |
https://creativecommons.org/publicdomain/zero/1.0/ | |
*/ |
git branch -f X origin/X
See : http://stackoverflow.com/questions/5667884/how-to-squash-commits-in-git-after-they-have-been-pushed
NCBI blastp seems to have a bug where it reports different top hits when -max_target_seqs is changed. This is a serious problem because the first 20 hits (for example) should be the same whether -max_target_seqs 100 or -max_target_seqs 500 is used.
The bug is reproducible on the command line when searching NCBI's nr blast database (dated 25-Nov-2015) using NCBI 2.2.28+, 2.2.30+ and 2.2.31+.
At first I thought it was something to do with my local exe/blastdb, but the same problem is also apparent on the NCBI blastp web interface (as of 30-Nov-2015)
/* | |
Tired of scrolling to one of the last photos on the page on Instagram? Let your | |
browser do the scrolling for you! | |
31-05-2017 | |
(c) 2017 - Loran Kloeze - [email protected] | |
Usage | |
- Go to https://www.instagram.com/instagram_handle/ (change instagram_handle in i.e. taylorswift) | |
- Open up the console (F12) (Firefox users: type 'allow pasting' if you haven't done so yet) | |
- Select the contents of this complete file and copy/paste it to the console and hit enter |