<![CDATA[BOL: Related items]]> https://bioinformaticsonline.com/related/32481?offset=1110 https://bioinformaticsonline.com/bookmarks/view/20504/chromevol Sun, 25 Jan 2015 00:33:11 -0600 https://bioinformaticsonline.com/bookmarks/view/20504/chromevol <![CDATA[ChromEvol]]> Chromosome number is a remarkably dynamic feature of eukaryotic evolution. Chromosome numbers can change by a duplication of the whole genome (a process termed polyploidy), or by single chromosome changes (ascending dysploidy via, e.g., chromosome fission or descending dysploidy via, e.g., chromosome fusion).
Of the various mechanisms of chromosome number change, polyploidy has received significant attention because of the impact such an event may have on the organism.
ChromEvol implements a series of likelihood models for the evolution of chromosome numbers. By comparing the fit of the different models to biological data, it may be possible to gain insight regarding the pathways by which the evolution of chromosome number proceeds. For each model, the program estimates the rates for the possible transitions assumed by the model, infers the set of ancestral chromosome numbers, and estimates the location along the tree for which polyploidy events (and other chromosome number changes) occurred. For further methodological details, see the publications and manual on the Downloads page.

http://www.tau.ac.il/~itaymay/cp/chromEvol/about.html

Address of the bookmark: http://www.tau.ac.il/~itaymay/cp/chromEvol/downloads.html

]]> Jit https://bioinformaticsonline.com/blog/view/36525/installing-bandage-on-ubunty Tue, 08 May 2018 08:03:21 -0500 https://bioinformaticsonline.com/blog/view/36525/installing-bandage-on-ubunty <![CDATA[Installing Bandage on Ubunty !]]> The following instructions successfully build Bandage (https://github.com/rrwick/Bandage ) on a fresh installation of Ubuntu 14.04:

  1. Ensure the package lists are up-to-date: sudo apt-get update
  2. Install prerequisite packages: sudo apt-get install build-essential git qtbase5-dev libqt5svg5-dev
  3. Download the Bandage code from GitHub: git clone https://github.com/rrwick/Bandage.git
  4. Open a terminal in the Bandage directory.
  5. Set the environment variable to specify that you will be using Qt 5, not Qt 4: export QT_SELECT=5
  6. Run qmake to generate a Makefile: qmake
  7. Build the program: make
  8. Bandage should now be an executable file.
  9. Optionally, copy the program into /usr/local/bin: sudo make install. The Bandage build directory can then be deleted.

➜ Tools git:(master) ✗ sudo apt-get update
[sudo] password for urbe: 
Hit:1 http://ppa.launchpad.net/webupd8team/atom/ubuntu xenial InRelease
Get:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB] 
Hit:3 http://ppa.launchpad.net/webupd8team/java/ubuntu xenial InRelease 
Hit:4 http://be.archive.ubuntu.com/ubuntu xenial InRelease 
Get:5 http://be.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:6 http://be.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB] 
Get:7 https://cran.rstudio.com/bin/linux/ubuntu xenial/ InRelease [3.590 B] 
Hit:8 https://download.docker.com/linux/ubuntu xenial InRelease 
Ign:9 http://download.opensuse.org/repositories/home:/sionescu/Debian ./ InRelease 
Hit:10 http://download.opensuse.org/repositories/home:/sionescu/Debian ./ Release 
Get:11 http://packages.cloud.google.com/apt cloud-sdk-xenial InRelease [6.372 B]
Get:12 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [484 kB]
Get:13 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [433 kB]
Get:14 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [209 kB]
Get:15 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [67,5 kB]
Get:16 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [68,0 kB] 
Get:17 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [107 kB]
Get:18 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [147 kB]
Get:19 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [769 kB] 
Get:20 http://be.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [710 kB] 
Get:21 http://be.archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [319 kB]
Get:22 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 Metadata [319 kB]
Get:24 http://be.archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons [228 kB] 
Get:25 http://be.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 DEP-11 Metadata [246 kB]
Err:11 http://packages.cloud.google.com/apt cloud-sdk-xenial InRelease 
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6A030B21BA07F4FB
Get:26 http://be.archive.ubuntu.com/ubuntu xenial-updates/universe DEP-11 64x64 Icons [331 kB]
Get:27 http://be.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 DEP-11 Metadata [5.964 B]
Get:28 http://be.archive.ubuntu.com/ubuntu xenial-backports/main amd64 DEP-11 Metadata [3.328 B]
Get:29 http://be.archive.ubuntu.com/ubuntu xenial-backports/universe amd64 DEP-11 Metadata [5.088 B]
Fetched 4.779 kB in 2s (1.606 kB/s) 
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://packages.cloud.google.com/apt cloud-sdk-xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6A030B21BA07F4FB
W: Failed to fetch http://packages.cloud.google.com/apt/dists/cloud-sdk-xenial/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6A030B21BA07F4FB
W: Some index files failed to download. They have been ignored, or old ones used instead.
➜ Tools git:(master) ✗ sudo apt-get install build-essential git qtbase5-dev libqt5svg5-dev
Reading package lists... Done
Building dependency tree 
Reading state information... Done
build-essential is already the newest version (12.1ubuntu2).
git is already the newest version (1:2.7.4-0ubuntu1.3).
The following packages were automatically installed and are no longer required:
bridge-utils containerd linux-headers-4.4.0-116 linux-headers-4.4.0-116-generic linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-image-4.4.0-116-generic linux-image-4.4.0-21-generic
linux-image-extra-4.4.0-116-generic linux-image-extra-4.4.0-21-generic linux-signed-image-4.4.0-116-generic runc ubuntu-fan
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
libdrm-dev libegl1-mesa-dev libgl1-mesa-dev libgles2-mesa libgles2-mesa-dev libglu1-mesa-dev libmirclient-dev libmircommon-dev libmircookie-dev libmircookie2 libmircore-dev libprotobuf-dev libprotobuf9v5
libqt5concurrent5 libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5opengl5 libqt5opengl5-dev libqt5printsupport5 libqt5sql5 libqt5sql5-sqlite libqt5svg5 libqt5test5 libqt5widgets5 libqt5xml5 libwayland-bin
libwayland-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-present-dev libxcb-randr0 libxcb-randr0-dev libxcb-render-util0 libxcb-render0-dev
libxcb-shape0-dev libxcb-sync-dev libxcb-xfixes0-dev libxcb-xkb1 libxdamage-dev libxext-dev libxfixes-dev libxkbcommon-dev libxkbcommon-x11-0 libxshmfence-dev libxxf86vm-dev mesa-common-dev qt5-qmake
qtbase5-dev-tools qttranslations5-l10n x11proto-damage-dev x11proto-dri2-dev x11proto-fixes-dev x11proto-gl-dev x11proto-xext-dev x11proto-xf86vidmode-dev
Suggested packages:
libqt5libqgtk2 qt5-image-formats-plugins qtwayland5 libxext-doc libmysqlclient-dev libpq-dev libsqlite3-dev unixodbc-dev
The following NEW packages will be installed:
libdrm-dev libegl1-mesa-dev libgl1-mesa-dev libgles2-mesa libgles2-mesa-dev libglu1-mesa-dev libmirclient-dev libmircommon-dev libmircookie-dev libmircookie2 libmircore-dev libprotobuf-dev libprotobuf9v5
libqt5concurrent5 libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5opengl5 libqt5opengl5-dev libqt5printsupport5 libqt5sql5 libqt5sql5-sqlite libqt5svg5 libqt5svg5-dev libqt5test5 libqt5widgets5 libqt5xml5
libwayland-bin libwayland-dev libx11-xcb-dev libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-present-dev libxcb-randr0 libxcb-randr0-dev libxcb-render-util0
libxcb-render0-dev libxcb-shape0-dev libxcb-sync-dev libxcb-xfixes0-dev libxcb-xkb1 libxdamage-dev libxext-dev libxfixes-dev libxkbcommon-dev libxkbcommon-x11-0 libxshmfence-dev libxxf86vm-dev mesa-common-dev
qt5-qmake qtbase5-dev qtbase5-dev-tools qttranslations5-l10n x11proto-damage-dev x11proto-dri2-dev x11proto-fixes-dev x11proto-gl-dev x11proto-xext-dev x11proto-xf86vidmode-dev
0 upgraded, 64 newly installed, 0 to remove and 11 not upgraded.
Need to get 15,2 MB of archives.
After this operation, 78,5 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5core5a amd64 5.5.1+dfsg-16ubuntu7.5 [1.817 kB]
Get:2 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5dbus5 amd64 5.5.1+dfsg-16ubuntu7.5 [175 kB]
Get:3 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5network5 amd64 5.5.1+dfsg-16ubuntu7.5 [540 kB]
Get:4 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-icccm4 amd64 0.4.1-1ubuntu1 [10,4 kB]
Get:5 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-image0 amd64 0.4.0-1build1 [12,3 kB]
Get:6 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-keysyms1 amd64 0.4.0-1 [8.406 B]
Get:7 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-randr0 amd64 1.11.1-1ubuntu1 [14,4 kB]
Get:8 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-render-util0 amd64 0.3.9-1 [9.638 B]
Get:9 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-xkb1 amd64 1.11.1-1ubuntu1 [29,2 kB]
Get:10 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxkbcommon-x11-0 amd64 0.5.0-1ubuntu2 [13,5 kB]
Get:11 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5gui5 amd64 5.5.1+dfsg-16ubuntu7.5 [2.290 kB]
Get:12 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5widgets5 amd64 5.5.1+dfsg-16ubuntu7.5 [2.252 kB]
Get:13 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libqt5svg5 amd64 5.5.1-2build1 [128 kB]
Get:14 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libqt5svg5-dev amd64 5.5.1-2build1 [9.724 B]
Get:15 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libdrm-dev amd64 2.4.83-1~16.04.1 [229 kB]
Get:16 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 x11proto-dri2-dev all 2.8-2 [12,6 kB]
Get:17 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 x11proto-gl-dev all 1.4.17-1 [17,9 kB]
Get:18 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 x11proto-xext-dev all 7.3.0-1 [212 kB]
Get:19 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxext-dev amd64 2:1.3.3-1 [82,1 kB]
Get:20 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 x11proto-xf86vidmode-dev all 2.3.1-2 [6.116 B]
Get:21 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxxf86vm-dev amd64 1:1.1.4-1 [13,3 kB]
Get:22 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 x11proto-fixes-dev all 1:5.0-2ubuntu2 [14,2 kB]
Get:23 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxfixes-dev amd64 1:5.0.1-2 [10,9 kB]
Get:24 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 x11proto-damage-dev all 1:1.2.1-2 [8.286 B]
Get:25 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxdamage-dev amd64 1:1.1.4-2 [5.028 B]
Get:26 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-glx0-dev amd64 1.11.1-1ubuntu1 [26,9 kB]
Get:27 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-dri2-0-dev amd64 1.11.1-1ubuntu1 [8.384 B]
Get:28 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-dri3-dev amd64 1.11.1-1ubuntu1 [5.752 B]
Get:29 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-render0-dev amd64 1.11.1-1ubuntu1 [15,3 kB]
Get:30 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-randr0-dev amd64 1.11.1-1ubuntu1 [18,2 kB]
Get:31 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-shape0-dev amd64 1.11.1-1ubuntu1 [6.900 B]
Get:32 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-xfixes0-dev amd64 1.11.1-1ubuntu1 [11,2 kB]
Get:33 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-sync-dev amd64 1.11.1-1ubuntu1 [10,1 kB]
Get:34 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxcb-present-dev amd64 1.11.1-1ubuntu1 [6.618 B]
Get:35 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxshmfence-dev amd64 1.2-1 [3.676 B]
Get:36 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libx11-xcb-dev amd64 2:1.6.3-1ubuntu2 [9.730 B]
Get:37 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libwayland-bin amd64 1.12.0-1~ubuntu16.04.3 [18,4 kB]
Get:38 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libwayland-dev amd64 1.12.0-1~ubuntu16.04.3 [92,4 kB]
Get:39 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmircore-dev amd64 0.26.3+16.04.20170605-0ubuntu1.1 [23,7 kB]
Get:40 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libprotobuf9v5 amd64 2.6.1-1.3 [326 kB]
Get:41 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libprotobuf-dev amd64 2.6.1-1.3 [473 kB]
Get:42 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libxkbcommon-dev amd64 0.5.0-1ubuntu2 [231 kB]
Get:43 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmircommon-dev amd64 0.26.3+16.04.20170605-0ubuntu1.1 [14,9 kB]
Get:44 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmircookie2 amd64 0.26.3+16.04.20170605-0ubuntu1.1 [22,5 kB]
Get:45 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmircookie-dev amd64 0.26.3+16.04.20170605-0ubuntu1.1 [5.152 B]
Get:46 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmirclient-dev amd64 0.26.3+16.04.20170605-0ubuntu1.1 [42,6 kB]
Get:47 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libegl1-mesa-dev amd64 17.2.8-0ubuntu0~16.04.1 [19,9 kB]
Get:48 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libgles2-mesa amd64 17.2.8-0ubuntu0~16.04.1 [13,4 kB]
Get:49 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libgles2-mesa-dev amd64 17.2.8-0ubuntu0~16.04.1 [40,2 kB]
Get:50 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 mesa-common-dev amd64 17.2.8-0ubuntu0~16.04.1 [525 kB]
Get:51 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libgl1-mesa-dev amd64 17.2.8-0ubuntu0~16.04.1 [4.456 B]
Get:52 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 libglu1-mesa-dev amd64 9.0.0-2.1 [202 kB]
Get:53 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5concurrent5 amd64 5.5.1+dfsg-16ubuntu7.5 [24,3 kB]
Get:54 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5opengl5 amd64 5.5.1+dfsg-16ubuntu7.5 [128 kB]
Get:55 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5printsupport5 amd64 5.5.1+dfsg-16ubuntu7.5 [174 kB]
Get:56 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5sql5 amd64 5.5.1+dfsg-16ubuntu7.5 [104 kB]
Get:57 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5test5 amd64 5.5.1+dfsg-16ubuntu7.5 [84,5 kB]
Get:58 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5xml5 amd64 5.5.1+dfsg-16ubuntu7.5 [91,8 kB]
Get:59 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 qt5-qmake amd64 5.5.1+dfsg-16ubuntu7.5 [1.192 kB]
Get:60 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 qtbase5-dev-tools amd64 5.5.1+dfsg-16ubuntu7.5 [1.056 kB]
Get:61 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 qtbase5-dev amd64 5.5.1+dfsg-16ubuntu7.5 [931 kB]
Get:62 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5opengl5-dev amd64 5.5.1+dfsg-16ubuntu7.5 [31,5 kB]
Get:63 http://be.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libqt5sql5-sqlite amd64 5.5.1+dfsg-16ubuntu7.5 [33,0 kB]
Get:64 http://be.archive.ubuntu.com/ubuntu xenial/main amd64 qttranslations5-l10n all 5.5.1-2build1 [1.210 kB]
Fetched 15,2 MB in 4s (3.099 kB/s) 
Extracting templates from packages: 100%
Selecting previously unselected package libqt5core5a:amd64.
(Reading database ... 480949 files and directories currently installed.)
Preparing to unpack .../libqt5core5a_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5core5a:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5dbus5:amd64.
Preparing to unpack .../libqt5dbus5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5dbus5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5network5:amd64.
Preparing to unpack .../libqt5network5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5network5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libxcb-icccm4:amd64.
Preparing to unpack .../libxcb-icccm4_0.4.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-icccm4:amd64 (0.4.1-1ubuntu1) ...
Selecting previously unselected package libxcb-image0:amd64.
Preparing to unpack .../libxcb-image0_0.4.0-1build1_amd64.deb ...
Unpacking libxcb-image0:amd64 (0.4.0-1build1) ...
Selecting previously unselected package libxcb-keysyms1:amd64.
Preparing to unpack .../libxcb-keysyms1_0.4.0-1_amd64.deb ...
Unpacking libxcb-keysyms1:amd64 (0.4.0-1) ...
Selecting previously unselected package libxcb-randr0:amd64.
Preparing to unpack .../libxcb-randr0_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-randr0:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxcb-render-util0:amd64.
Preparing to unpack .../libxcb-render-util0_0.3.9-1_amd64.deb ...
Unpacking libxcb-render-util0:amd64 (0.3.9-1) ...
Selecting previously unselected package libxcb-xkb1:amd64.
Preparing to unpack .../libxcb-xkb1_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-xkb1:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxkbcommon-x11-0:amd64.
Preparing to unpack .../libxkbcommon-x11-0_0.5.0-1ubuntu2_amd64.deb ...
Unpacking libxkbcommon-x11-0:amd64 (0.5.0-1ubuntu2) ...
Selecting previously unselected package libqt5gui5:amd64.
Preparing to unpack .../libqt5gui5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5gui5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5widgets5:amd64.
Preparing to unpack .../libqt5widgets5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5widgets5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5svg5:amd64.
Preparing to unpack .../libqt5svg5_5.5.1-2build1_amd64.deb ...
Unpacking libqt5svg5:amd64 (5.5.1-2build1) ...
Selecting previously unselected package libqt5svg5-dev:amd64.
Preparing to unpack .../libqt5svg5-dev_5.5.1-2build1_amd64.deb ...
Unpacking libqt5svg5-dev:amd64 (5.5.1-2build1) ...
Selecting previously unselected package libdrm-dev:amd64.
Preparing to unpack .../libdrm-dev_2.4.83-1~16.04.1_amd64.deb ...
Unpacking libdrm-dev:amd64 (2.4.83-1~16.04.1) ...
Selecting previously unselected package x11proto-dri2-dev.
Preparing to unpack .../x11proto-dri2-dev_2.8-2_all.deb ...
Unpacking x11proto-dri2-dev (2.8-2) ...
Selecting previously unselected package x11proto-gl-dev.
Preparing to unpack .../x11proto-gl-dev_1.4.17-1_all.deb ...
Unpacking x11proto-gl-dev (1.4.17-1) ...
Selecting previously unselected package x11proto-xext-dev.
Preparing to unpack .../x11proto-xext-dev_7.3.0-1_all.deb ...
Unpacking x11proto-xext-dev (7.3.0-1) ...
Selecting previously unselected package libxext-dev:amd64.
Preparing to unpack .../libxext-dev_2%3a1.3.3-1_amd64.deb ...
Unpacking libxext-dev:amd64 (2:1.3.3-1) ...
Selecting previously unselected package x11proto-xf86vidmode-dev.
Preparing to unpack .../x11proto-xf86vidmode-dev_2.3.1-2_all.deb ...
Unpacking x11proto-xf86vidmode-dev (2.3.1-2) ...
Selecting previously unselected package libxxf86vm-dev:amd64.
Preparing to unpack .../libxxf86vm-dev_1%3a1.1.4-1_amd64.deb ...
Unpacking libxxf86vm-dev:amd64 (1:1.1.4-1) ...
Selecting previously unselected package x11proto-fixes-dev.
Preparing to unpack .../x11proto-fixes-dev_1%3a5.0-2ubuntu2_all.deb ...
Unpacking x11proto-fixes-dev (1:5.0-2ubuntu2) ...
Selecting previously unselected package libxfixes-dev:amd64.
Preparing to unpack .../libxfixes-dev_1%3a5.0.1-2_amd64.deb ...
Unpacking libxfixes-dev:amd64 (1:5.0.1-2) ...
Selecting previously unselected package x11proto-damage-dev.
Preparing to unpack .../x11proto-damage-dev_1%3a1.2.1-2_all.deb ...
Unpacking x11proto-damage-dev (1:1.2.1-2) ...
Selecting previously unselected package libxdamage-dev:amd64.
Preparing to unpack .../libxdamage-dev_1%3a1.1.4-2_amd64.deb ...
Unpacking libxdamage-dev:amd64 (1:1.1.4-2) ...
Selecting previously unselected package libxcb-glx0-dev:amd64.
Preparing to unpack .../libxcb-glx0-dev_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-glx0-dev:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxcb-dri2-0-dev:amd64.
Preparing to unpack .../libxcb-dri2-0-dev_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-dri2-0-dev:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxcb-dri3-dev:amd64.
Preparing to unpack .../libxcb-dri3-dev_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-dri3-dev:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxcb-render0-dev:amd64.
Preparing to unpack .../libxcb-render0-dev_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-render0-dev:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxcb-randr0-dev:amd64.
Preparing to unpack .../libxcb-randr0-dev_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-randr0-dev:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxcb-shape0-dev:amd64.
Preparing to unpack .../libxcb-shape0-dev_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-shape0-dev:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxcb-xfixes0-dev:amd64.
Preparing to unpack .../libxcb-xfixes0-dev_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-xfixes0-dev:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxcb-sync-dev:amd64.
Preparing to unpack .../libxcb-sync-dev_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-sync-dev:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxcb-present-dev:amd64.
Preparing to unpack .../libxcb-present-dev_1.11.1-1ubuntu1_amd64.deb ...
Unpacking libxcb-present-dev:amd64 (1.11.1-1ubuntu1) ...
Selecting previously unselected package libxshmfence-dev:amd64.
Preparing to unpack .../libxshmfence-dev_1.2-1_amd64.deb ...
Unpacking libxshmfence-dev:amd64 (1.2-1) ...
Selecting previously unselected package libx11-xcb-dev:amd64.
Preparing to unpack .../libx11-xcb-dev_2%3a1.6.3-1ubuntu2_amd64.deb ...
Unpacking libx11-xcb-dev:amd64 (2:1.6.3-1ubuntu2) ...
Selecting previously unselected package libwayland-bin.
Preparing to unpack .../libwayland-bin_1.12.0-1~ubuntu16.04.3_amd64.deb ...
Unpacking libwayland-bin (1.12.0-1~ubuntu16.04.3) ...
Selecting previously unselected package libwayland-dev:amd64.
Preparing to unpack .../libwayland-dev_1.12.0-1~ubuntu16.04.3_amd64.deb ...
Unpacking libwayland-dev:amd64 (1.12.0-1~ubuntu16.04.3) ...
Selecting previously unselected package libmircore-dev:amd64.
Preparing to unpack .../libmircore-dev_0.26.3+16.04.20170605-0ubuntu1.1_amd64.deb ...
Unpacking libmircore-dev:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Selecting previously unselected package libprotobuf9v5:amd64.
Preparing to unpack .../libprotobuf9v5_2.6.1-1.3_amd64.deb ...
Unpacking libprotobuf9v5:amd64 (2.6.1-1.3) ...
Selecting previously unselected package libprotobuf-dev:amd64.
Preparing to unpack .../libprotobuf-dev_2.6.1-1.3_amd64.deb ...
Unpacking libprotobuf-dev:amd64 (2.6.1-1.3) ...
Selecting previously unselected package libxkbcommon-dev.
Preparing to unpack .../libxkbcommon-dev_0.5.0-1ubuntu2_amd64.deb ...
Unpacking libxkbcommon-dev (0.5.0-1ubuntu2) ...
Selecting previously unselected package libmircommon-dev:amd64.
Preparing to unpack .../libmircommon-dev_0.26.3+16.04.20170605-0ubuntu1.1_amd64.deb ...
Unpacking libmircommon-dev:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Selecting previously unselected package libmircookie2:amd64.
Preparing to unpack .../libmircookie2_0.26.3+16.04.20170605-0ubuntu1.1_amd64.deb ...
Unpacking libmircookie2:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Selecting previously unselected package libmircookie-dev:amd64.
Preparing to unpack .../libmircookie-dev_0.26.3+16.04.20170605-0ubuntu1.1_amd64.deb ...
Unpacking libmircookie-dev:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Selecting previously unselected package libmirclient-dev:amd64.
Preparing to unpack .../libmirclient-dev_0.26.3+16.04.20170605-0ubuntu1.1_amd64.deb ...
Unpacking libmirclient-dev:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Selecting previously unselected package libegl1-mesa-dev:amd64.
Preparing to unpack .../libegl1-mesa-dev_17.2.8-0ubuntu0~16.04.1_amd64.deb ...
Unpacking libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Selecting previously unselected package libgles2-mesa:amd64.
Preparing to unpack .../libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb ...
Unpacking libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Selecting previously unselected package libgles2-mesa-dev:amd64.
Preparing to unpack .../libgles2-mesa-dev_17.2.8-0ubuntu0~16.04.1_amd64.deb ...
Unpacking libgles2-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Selecting previously unselected package mesa-common-dev:amd64.
Preparing to unpack .../mesa-common-dev_17.2.8-0ubuntu0~16.04.1_amd64.deb ...
Unpacking mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Selecting previously unselected package libgl1-mesa-dev:amd64.
Preparing to unpack .../libgl1-mesa-dev_17.2.8-0ubuntu0~16.04.1_amd64.deb ...
Unpacking libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Selecting previously unselected package libglu1-mesa-dev:amd64.
Preparing to unpack .../libglu1-mesa-dev_9.0.0-2.1_amd64.deb ...
Unpacking libglu1-mesa-dev:amd64 (9.0.0-2.1) ...
Selecting previously unselected package libqt5concurrent5:amd64.
Preparing to unpack .../libqt5concurrent5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5concurrent5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5opengl5:amd64.
Preparing to unpack .../libqt5opengl5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5opengl5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5printsupport5:amd64.
Preparing to unpack .../libqt5printsupport5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5printsupport5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5sql5:amd64.
Preparing to unpack .../libqt5sql5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5sql5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5test5:amd64.
Preparing to unpack .../libqt5test5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5test5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5xml5:amd64.
Preparing to unpack .../libqt5xml5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5xml5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package qt5-qmake:amd64.
Preparing to unpack .../qt5-qmake_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking qt5-qmake:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package qtbase5-dev-tools.
Preparing to unpack .../qtbase5-dev-tools_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking qtbase5-dev-tools (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package qtbase5-dev:amd64.
Preparing to unpack .../qtbase5-dev_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking qtbase5-dev:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5opengl5-dev:amd64.
Preparing to unpack .../libqt5opengl5-dev_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5opengl5-dev:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package libqt5sql5-sqlite:amd64.
Preparing to unpack .../libqt5sql5-sqlite_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
Unpacking libqt5sql5-sqlite:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Selecting previously unselected package qttranslations5-l10n.
Preparing to unpack .../qttranslations5-l10n_5.5.1-2build1_all.deb ...
Unpacking qttranslations5-l10n (5.5.1-2build1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libqt5core5a:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5dbus5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5network5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libxcb-icccm4:amd64 (0.4.1-1ubuntu1) ...
Setting up libxcb-image0:amd64 (0.4.0-1build1) ...
Setting up libxcb-keysyms1:amd64 (0.4.0-1) ...
Setting up libxcb-randr0:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-render-util0:amd64 (0.3.9-1) ...
Setting up libxcb-xkb1:amd64 (1.11.1-1ubuntu1) ...
Setting up libxkbcommon-x11-0:amd64 (0.5.0-1ubuntu2) ...
Setting up libqt5gui5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5widgets5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5svg5:amd64 (5.5.1-2build1) ...
Setting up libqt5svg5-dev:amd64 (5.5.1-2build1) ...
Setting up libdrm-dev:amd64 (2.4.83-1~16.04.1) ...
Setting up x11proto-dri2-dev (2.8-2) ...
Setting up x11proto-gl-dev (1.4.17-1) ...
Setting up x11proto-xext-dev (7.3.0-1) ...
Setting up libxext-dev:amd64 (2:1.3.3-1) ...
Setting up x11proto-xf86vidmode-dev (2.3.1-2) ...
Setting up libxxf86vm-dev:amd64 (1:1.1.4-1) ...
Setting up x11proto-fixes-dev (1:5.0-2ubuntu2) ...
Setting up libxfixes-dev:amd64 (1:5.0.1-2) ...
Setting up x11proto-damage-dev (1:1.2.1-2) ...
Setting up libxdamage-dev:amd64 (1:1.1.4-2) ...
Setting up libxcb-glx0-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-dri2-0-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-dri3-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-render0-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-randr0-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-shape0-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-xfixes0-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-sync-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libxcb-present-dev:amd64 (1.11.1-1ubuntu1) ...
Setting up libxshmfence-dev:amd64 (1.2-1) ...
Setting up libx11-xcb-dev:amd64 (2:1.6.3-1ubuntu2) ...
Setting up libwayland-bin (1.12.0-1~ubuntu16.04.3) ...
Setting up libwayland-dev:amd64 (1.12.0-1~ubuntu16.04.3) ...
Setting up libmircore-dev:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Setting up libprotobuf9v5:amd64 (2.6.1-1.3) ...
Setting up libprotobuf-dev:amd64 (2.6.1-1.3) ...
Setting up libxkbcommon-dev (0.5.0-1ubuntu2) ...
Setting up libmircommon-dev:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Setting up libmircookie2:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Setting up libmircookie-dev:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Setting up libmirclient-dev:amd64 (0.26.3+16.04.20170605-0ubuntu1.1) ...
Setting up libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Setting up libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Setting up libgles2-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Setting up mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Setting up libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1) ...
Setting up libglu1-mesa-dev:amd64 (9.0.0-2.1) ...
Setting up libqt5concurrent5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5opengl5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5printsupport5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5sql5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5test5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5xml5:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up qt5-qmake:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up qtbase5-dev-tools (5.5.1+dfsg-16ubuntu7.5) ...
Setting up qtbase5-dev:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5opengl5-dev:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up libqt5sql5-sqlite:amd64 (5.5.1+dfsg-16ubuntu7.5) ...
Setting up qttranslations5-l10n (5.5.1-2build1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
➜ Tools git:(master) ✗ git clone https://github.com/rrwick/Bandage.git
Cloning into 'Bandage'...
remote: Counting objects: 7813, done.
remote: Total 7813 (delta 0), reused 0 (delta 0), pack-reused 7813
Receiving objects: 100% (7813/7813), 27.43 MiB | 16.33 MiB/s, done.
Resolving deltas: 100% (5973/5973), done.
Checking connectivity... done.
➜ Tools git:(master) ✗ cd Bandage 
➜ Bandage git:(master) ls
Bandage.pro BandageTests.pro blast build_scripts command_line COPYING graph images ogdf program README.md tests ui
➜ Bandage git:(master) export QT_SELECT=5
➜ Bandage git:(master) qmake
➜ Bandage git:(master) ✗ make
/home/urbe/anaconda3/bin/uic ui/mainwindow.ui -o ui_mainwindow.h
/home/urbe/anaconda3/bin/uic ui/settingsdialog.ui -o ui_settingsdialog.h
/home/urbe/anaconda3/bin/uic ui/aboutdialog.ui -o ui_aboutdialog.h
/home/urbe/anaconda3/bin/uic ui/enteroneblastquerydialog.ui -o ui_enteroneblastquerydialog.h
/home/urbe/anaconda3/bin/uic ui/blastsearchdialog.ui -o ui_blastsearchdialog.h
/home/urbe/anaconda3/bin/uic ui/myprogressdialog.ui -o ui_myprogressdialog.h
/home/urbe/anaconda3/bin/uic ui/pathspecifydialog.ui -o ui_pathspecifydialog.h
/home/urbe/anaconda3/bin/uic ui/querypathsdialog.ui -o ui_querypathsdialog.h
/home/urbe/anaconda3/bin/uic ui/blasthitfiltersdialog.ui -o ui_blasthitfiltersdialog.h
/home/urbe/anaconda3/bin/uic ui/changenodenamedialog.ui -o ui_changenodenamedialog.h
/home/urbe/anaconda3/bin/uic ui/graphinfodialog.ui -o ui_graphinfodialog.h
/home/urbe/anaconda3/bin/uic ui/changenodedepthdialog.ui -o ui_changenodedepthdialog.h
g++ -c -pipe -O2 -std=gnu++0x -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -Iui -I/usr/include -I../../anaconda3/include/qt -I../../anaconda3/include/qt/QtSvg -I../../anaconda3/include/qt/QtWidgets -I../../anaconda3/include/qt/QtGui -I../../anaconda3/include/qt/QtCore -I. -I. -I../../anaconda3/mkspecs/linux-g++ -o main.o program/main.cpp
g++ -c -pipe -O2 -std=gnu++0x -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -Iui -I/usr/include -I../../anaconda3/include/qt -I../../anaconda3/include/qt/QtSvg -I../../anaconda3/include/qt/QtWidgets -I../../anaconda3/include/qt/QtGui -I../../anaconda3/include/qt/QtCore -I. -I. -I../../anaconda3/mkspecs/linux-g++ -o settings.o program/settings.cpp
....

...
g++ -Wl,-O1 -Wl,-rpath,/home/urbe/anaconda3/lib -o Bandage main.o settings.o globals.o graphlayoutworker.o debruijnnode.o debruijnedge.o graphicsitemnode.o graphicsitemedge.o mainwindow.o graphicsviewzoom.o settingsdialog.o mygraphicsview.o mygraphicsscene.o aboutdialog.o enteroneblastquerydialog.o blasthit.o blastqueries.o blastsearchdialog.o infotextwidget.o assemblygraph.o verticalscrollarea.o myprogressdialog.o nodewidthvisualaid.o verticallabel.o load.o image.o commoncommandlinefunctions.o mytablewidget.o buildblastdatabaseworker.o colourbutton.o blastquery.o runblastsearchworker.o blastsearch.o path.o pathspecifydialog.o graphlocation.o tablewidgetitemint.o tablewidgetitemdouble.o tablewidgetitemshown.o memory.o querypathspushbutton.o querypathsdialog.o blastquerypath.o blasthitfiltersdialog.o scinot.o changenodenamedialog.o querypathsequencecopybutton.o querypaths.o info.o reduce.o Graph.o GraphAttributes.o FMMMLayout.o geometry.o ClusterGraphAttributes.o FruchtermanReingold.o NMM.o GmlParser.o simple_graph_alg.o basic.o XmlParser.o String.o Hashing.o PoolMemoryAllocator.o GraphCopy.o CombinatorialEmbedding.o OgmlParser.o ClusterGraph.o Math.o EdgeAttributes.o NodeAttributes.o MAARPacking.o Multilevel.o numexcept.o Set.o Ogml.o DinoXmlParser.o DinoXmlScanner.o DinoTools.o DinoLineBuffer.o System.o QuadTreeNM.o QuadTreeNodeNM.o Constraint.o MultilevelGraph.o graphinfodialog.o tablewidgetitemname.o changenodedepthdialog.o qrc_images.o moc_graphlayoutworker.o moc_mainwindow.o moc_graphicsviewzoom.o moc_settingsdialog.o moc_mygraphicsview.o moc_mygraphicsscene.o moc_aboutdialog.o moc_enteroneblastquerydialog.o moc_blastquery.o moc_blastsearchdialog.o moc_infotextwidget.o moc_assemblygraph.o moc_verticalscrollarea.o moc_myprogressdialog.o moc_nodewidthvisualaid.o moc_verticallabel.o moc_mytablewidget.o moc_buildblastdatabaseworker.o moc_colourbutton.o moc_runblastsearchworker.o moc_pathspecifydialog.o moc_querypathspushbutton.o moc_querypathsdialog.o moc_blasthitfiltersdialog.o moc_changenodenamedialog.o moc_querypathsequencecopybutton.o moc_graphinfodialog.o moc_changenodedepthdialog.o -L/usr/lib -L/home/urbe/anaconda3/lib -lQt5Svg -lQt5Widgets -lQt5Gui -lQt5Core -lGL -lpthread 
➜ Bandage git:(master) ✗ ls 
aboutdialog.o DinoTools.o Makefile moc_infotextwidget.cpp moc_verticalscrollarea.o scinot.o
assemblygraph.o DinoXmlParser.o Math.o moc_infotextwidget.o MultilevelGraph.o Set.o
Bandage DinoXmlScanner.o memory.o moc_mainwindow.cpp Multilevel.o settingsdialog.o
Bandage.pro EdgeAttributes.o moc_aboutdialog.cpp moc_mainwindow.o mygraphicsscene.o settings.o
BandageTests.pro enteroneblastquerydialog.o moc_aboutdialog.o moc_mygraphicsscene.cpp mygraphicsview.o simple_graph_alg.o
basic.o FMMMLayout.o moc_assemblygraph.cpp moc_mygraphicsscene.o myprogressdialog.o String.o
blast FruchtermanReingold.o moc_assemblygraph.o moc_mygraphicsview.cpp mytablewidget.o System.o
blasthitfiltersdialog.o geometry.o moc_blasthitfiltersdialog.cpp moc_mygraphicsview.o NMM.o tablewidgetitemdouble.o
blasthit.o globals.o moc_blasthitfiltersdialog.o moc_myprogressdialog.cpp NodeAttributes.o tablewidgetitemint.o
blastqueries.o GmlParser.o moc_blastquery.cpp moc_myprogressdialog.o nodewidthvisualaid.o tablewidgetitemname.o
blastquery.o graph moc_blastquery.o moc_mytablewidget.cpp numexcept.o tablewidgetitemshown.o
blastquerypath.o GraphAttributes.o moc_blastsearchdialog.cpp moc_mytablewidget.o ogdf tests
blastsearchdialog.o GraphCopy.o moc_blastsearchdialog.o moc_nodewidthvisualaid.cpp Ogml.o ui
blastsearch.o graphicsitemedge.o moc_buildblastdatabaseworker.cpp moc_nodewidthvisualaid.o OgmlParser.o ui_aboutdialog.h
buildblastdatabaseworker.o graphicsitemnode.o moc_buildblastdatabaseworker.o moc_pathspecifydialog.cpp path.o ui_blasthitfiltersdialog.h
build_scripts graphicsviewzoom.o moc_changenodedepthdialog.cpp moc_pathspecifydialog.o pathspecifydialog.o ui_blastsearchdialog.h
changenodedepthdialog.o graphinfodialog.o moc_changenodedepthdialog.o moc_querypathsdialog.cpp PoolMemoryAllocator.o ui_changenodedepthdialog.h
changenodenamedialog.o graphlayoutworker.o moc_changenodenamedialog.cpp moc_querypathsdialog.o program ui_changenodenamedialog.h
ClusterGraphAttributes.o graphlocation.o moc_changenodenamedialog.o moc_querypathsequencecopybutton.cpp qrc_images.cpp ui_enteroneblastquerydialog.h
ClusterGraph.o Graph.o moc_colourbutton.cpp moc_querypathsequencecopybutton.o qrc_images.o ui_graphinfodialog.h
colourbutton.o Hashing.o moc_colourbutton.o moc_querypathspushbutton.cpp QuadTreeNM.o ui_mainwindow.h
CombinatorialEmbedding.o image.o moc_enteroneblastquerydialog.cpp moc_querypathspushbutton.o QuadTreeNodeNM.o ui_myprogressdialog.h
command_line images moc_enteroneblastquerydialog.o moc_runblastsearchworker.cpp querypathsdialog.o ui_pathspecifydialog.h
commoncommandlinefunctions.o info.o moc_graphicsviewzoom.cpp moc_runblastsearchworker.o querypathsequencecopybutton.o ui_querypathsdialog.h
Constraint.o infotextwidget.o moc_graphicsviewzoom.o moc_settingsdialog.cpp querypaths.o ui_settingsdialog.h
COPYING load.o moc_graphinfodialog.cpp moc_settingsdialog.o querypathspushbutton.o verticallabel.o
debruijnedge.o MAARPacking.o moc_graphinfodialog.o moc_verticallabel.cpp README.md verticalscrollarea.o
debruijnnode.o main.o moc_graphlayoutworker.cpp moc_verticallabel.o reduce.o XmlParser.o
DinoLineBuffer.o mainwindow.o moc_graphlayoutworker.o moc_verticalscrollarea.cpp runblastsearchworker.o
➜ Bandage git:(master) ✗ ./Bandage

]]> Jit https://bioinformaticsonline.com/opportunity/view/20672/jrfra-structuralcomputational-biology-at-icgeb Thu, 29 Jan 2015 11:52:40 -0600 <![CDATA[JRF/RA Structural/Computational Biology at ICGEB]]> Research Associate and JRF positions in the Structural and Computational Biology Group starting 1st March 2015. Collaborative projects include work on:

a) bioinformatics, systems and computational biology
b) malaria
c) drug discovery
d) genomics
e) microbiology
f) metabolic disorders
g) molecular medicine

Eligibility: Applicants must have one of the following :

1) INSPIRE award for undertakig either PhD or Postdoctoral research;
2) SPM award for PhD;
3) JRF for pursuing PhD from CSIR/DBT/ICMR

Interest and experience in Biochemistry/Bioinformatics/Biophysics/ Chemistry/Genomics/Molecular Biology/ is essential.

Submit curriculum vitae to sb.icgeb@gmail.com by 20 February 2015

]]> https://bioinformaticsonline.com/bookmarks/view/36723/hapsembler-an-assembler-for-highly-polymorphic-genomes Tue, 22 May 2018 04:09:53 -0500 https://bioinformaticsonline.com/bookmarks/view/36723/hapsembler-an-assembler-for-highly-polymorphic-genomes <![CDATA[Hapsembler: An Assembler for Highly Polymorphic Genomes]]> Address of the bookmark: http://compbio.cs.toronto.edu/hapsembler/

]]> Jit https://bioinformaticsonline.com/opportunity/view/21538/senior-research-fellow-at-all-india-institute-of-medical-sciences-aiims-delhi-delhi-delhi Wed, 11 Mar 2015 03:06:10 -0500 <![CDATA[SENIOR RESEARCH FELLOW at All India Institute of Medical Sciences (AIIMS Delhi) - Delhi, Delhi]]> Applications are invited from eligible candidates for the following temporary post in an ICMR funded Research Project entitle “An Investigation to find out reasons for Phenotypic Heterogeneity/Variability in 22q11.2 Microdeletion Syndrome” in Department of Reproductive Biology, AIIMS, New Delhi PI: Dr. Ashutosh Halder, Professor, Department of Reproductive Biology

Name of the post: Senior Research Fellow (SRF)
Duration: 2 year
Salary: Rs. 28000/- per month + 30% HRA
Eligibility: MSc (life sciences) with 2 years research experience, NET/GATE qualified
Desirable: Experience in the field of Genomics, Epigenomics & Bioinformatics
SELECTION PROCEDURE FOR ALL INDIA INSTITUTE OF MEDICAL SCIENCES (AIIMS DELHI) – SENIOR RESEARCH FELLOW POST:

Candidates can apply on or before 15/03/2015
No Detailed information about the selection process is mentioned in the recruitment notification
HOW TO APPLY FOR SENIOR RESEARCH FELLOW VACANCY IN ALL INDIA INSTITUTE OF MEDICAL SCIENCES (AIIMS DELHI):

Deadline: 15.03.15 Submit your C.V in Room No. 2099 (Molecular Cytogenetics Lab), 2nd floor, Reproductive Biology, All India Institute of Medical Sciences, New Delhi-110029 or Email CV to: ashutoshhalder@gmail.com Your CV should include the details of your work experience & degrees along with two references with e-mail and contact number Only 10 shortlisted (on merit) candidates will be invited for interview. No TA/DA will be applicable for the same

]]> https://bioinformaticsonline.com/opportunity/view/20959/research-associate-and-jrf-positions-in-the-structural-and-computational-biology-group-at-icgeb Mon, 02 Feb 2015 23:00:37 -0600 <![CDATA[Research Associate and JRF positions in the Structural and Computational Biology Group at ICGEB]]> Research Associate and JRF positions in the Structural and Computational Biology Group starting 1st March 2015. Collaborative projects include work on:

a) bioinformatics, systems and computational biology
b) malaria
c) drug discovery
d) genomics
e) microbiology
f) metabolic disorders
g) molecular medicine

Eligibility: Applicants must have one of the following :

1) INSPIRE award for undertakig either PhD or Postdoctoral research;
2) SPM award for PhD;
3) JRF for pursuing PhD from CSIR/DBT/ICMR

Interest and experience in Biochemistry/Bioinformatics/Biophysics/ Chemistry/Genomics/Molecular Biology/ is essential.

Submit curriculum vitae to sb.icgeb@gmail.com by 20 February 2015

]]> https://bioinformaticsonline.com/bookmarks/view/38039/vgsc-a-web-based-vector-graph-toolkit-of-genome-synteny-and-collinearity Tue, 30 Oct 2018 10:46:28 -0500 https://bioinformaticsonline.com/bookmarks/view/38039/vgsc-a-web-based-vector-graph-toolkit-of-genome-synteny-and-collinearity <![CDATA[VGSC: A Web-Based Vector Graph Toolkit of Genome Synteny and Collinearity]]> VGSC, the Vector Graph toolkit of genome Synteny and Collinearity, and its online service, to visualize the synteny and collinearity in the common graphical format, including both raster (JPEG, Bitmap, and PNG) and vector graphic (SVG, EPS, and PDF). 

Address of the bookmark: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4783527/

]]> Abhimanyu Singh https://bioinformaticsonline.com/opportunity/view/21064/jrf-project-assistant-recruitment-at-shillong-%E2%80%93-bioinformatics-centre-dic Sat, 07 Feb 2015 06:00:23 -0600 <![CDATA[JRF / Project Assistant Recruitment at Shillong – Bioinformatics Centre (DIC)]]> 3 Vacancies at Bioinformatics Centre (DIC) For M.Tech/M.Sc. Degree Candidates. Apply Before 15th February,2015

Bioinformatics Centre (DIC) invites applications for the following posts:

Job Number: 01
Job Designation: Junior Research Fellow (JRF)
Number of Vacancy: 02 (Two)
Educational Qualification:
M.Tech/M.Sc. in Life Sciences/Botany/Zoology/Biochemistry/Biotechnology/Bioinformatics.
Desirable Qualification:
Aptitude for Bioinformatics and Computer Programming/Next generation sequencing data analysis.

Job Number: 02
Job Designation: Project Assistant
Number of Vacancy: 01 (One)
Educational Qualification:
Graduation in Science.
Desirable Qualification:
Experience of working in a Life Science/Plant Biotechnology Lab.

Place of Work: Shillong

How To Apply For Opening:
The applications through email bicnehu@gmail.com or post must reach the undersigned within 15 days from the date of publication of this advertisement.

Last Date To Apply: 15th February,2015

Contact Address: Bioinformatics Centre (DIC),Shillong-793022

Advertisement Details: Employment News (31 January – 6 February) Page 28

]]> https://bioinformaticsonline.com/researchlabs/view/38418/charles-swanton-lab Tue, 11 Dec 2018 08:09:22 -0600 <![CDATA[CHARLES SWANTON LAB]]> They are using the latest DNA sequencing technology to read the genetic makeup of cancer cells within tumours in ever greater detail, teasing out patterns of evolution (evolutionary rule books), cancer heterogeneity and working out what changes have happened as a tumour evolves. We’re also investigating the processes that cause mutations and accelerate tumour evolution and working out how they might be stopped. And we are running evolutionary clinical trials with immune and targeted therapies to bring the benefits of our work to patients as quickly as possible.

https://www.crick.ac.uk/research/labs/charles-swanton

]]> https://bioinformaticsonline.com/blog/view/21257/bioinformatics-phds-cover-letter Mon, 16 Feb 2015 12:48:52 -0600 https://bioinformaticsonline.com/blog/view/21257/bioinformatics-phds-cover-letter <![CDATA[Bioinformatics PhDs - Cover Letter]]> Overview
The reception your cover letter will receive is more varied and unpredictable than the other elements of your application packet.  Some readers, especially at large research universities, will skip it entirely, and focus instead on more direct indicators of your academic achievements and potential: the CV, letters, and writing sample.  Most often, however, your cover letter works in tandem with your CV, and represents your best opportunity to communicate directly with your target audience prior to an interview.

The cover letter should not simply repeat the information contained in the CV; rather it should elaborate and frame the aspects of your academic training and background that you want search committee members to have uppermost in their minds as they consider your candidacy.  At a minimum, it should contain a clear statement of your research and teaching interests, and how your qualifications match the requirements of the job description. Many disciplines have their own conventions and protocols for application materials including the cover letter. Be sure to show a draft of your letter to your chair or the department's placement advisor.

There is no perfect or even preferred style of cover letter save that tone should be that of a confident professional.  Departments aren't interested in hiring graduate students (they already have enough of those).  They are looking for serious scholars/teachers who will make interesting, congenial, and productive colleagues. While it is probably not a good use of your time to tailor your letter for each opening, you will probably need at least two base versions that emphasize different elements (You would not want to use the same cover letter to apply to Oberlin as UC Irvine). You may want to customize the letters for the three to five jobs most attractive to you.

Your cover letter should not exceed a page and a half or two at the most.  No one will read a four-page letter, and your apparent inability to communicate your credentials in a concise manner is not to your advantage. Every line of your letter should serve a demonstrable purpose. Some people have gotten excellent jobs with a brief, boilerplate letter containing no more than a short intro, a paragraph on their research, and a couple of sentences on their teaching. Others use letters that discuss in very specific terms how they, their research, and their teaching would "fit" within the existing department and institutional setting. The choice of style is up to you, and should reflect what makes you feel most comfortable and most positive about your credentials.

There are, however, circumstances where a longer, more annotated version is more likely to be helpful. The issues you should take into account when making this decision are:

    The size of the department/institution
    The extent to which your research is mainstream and its significance readily apparent
    The extent to which your qualifications diverge from those mentioned in the job ad
    The extent to which the institution to which you are applying differs from UC Berkeley and the relative importance of teaching versus research
    Unusual circumstances or career paths

Size matters. The larger the department, the less detailed your letter needs to be.  If there are already six people working in your sub-field, they can assess and translate the significance of your work to others in the department.  If, however, you will be the only history of science person or the only physical anthropologist in the department, the search committee and others will likely need more help from you to understand the import of your work.  Remember, if they are searching for your specialty they are understaffed in your area, and even if there is more than one person in your sub-field she/he may be on leave or otherwise uninvolved in the search.

Similarly, smaller departments are more likely to be concerned than larger ones about the specific courses you are prepared to teach.  If there are certain core courses your position needs to cover, make it unambiguously clear that you are prepared to do so even if you haven't taught them already.

As a rule of thumb, the more your profile diverges from the specifics of the job description (or the norm, such that it exists), the more likely you will want to say more about why you are nonetheless a strong candidate.  By doing so you can turn a question mark into an advantage.  Highlight your strengths, and if you have time perform a little research on the department (see below) so you can explain how you would add to the department in ways that they might otherwise not have considered.  Job descriptions are not always etched in stone. If you're very interested in the job, call the department and ask to speak to someone on the search committee.  If that's too intimidating, call the departmental assistant or secretary. They can at least tell you if it’s a new position or replacement which in turn can indicate whether they really need someone who can teach The Politics of Southern Africa or if Middle Eastern Politics would do just as well.  They may well be willing to sacrifice a course in an area that the ad specified in order to get the extra teaching experience or innovative research that you have to offer, but only if you give them the opportunity and explain what they'd get in return.

 If you've taken an unusually long time to finish because you spent three years learning a new language in order to prepare for two years of original research or some other factor that enriches what you have to offer as a teacher or a scholar, let them know about it.  Learning a new language, for example, is an indicator of your commitment to serious scholarship.  Think of a way to put a positive valence on an aspect of your CV that you believe is likely to raise questions or doubts.

As hard as it may be for not-yet-employed-but-soon-to-be academics like yourselves to believe, there are some individuals and departments that are intimidated by you and your institutional pedigree.  There are many fine schools and departments that are convinced that every Berkeley graduate student is only interested in a position at Harvard, Princeton, or (hold your nose) Stanford.  If it is a small liberal arts college, they may also assume that you view teaching and advising undergraduates strictly as a necessary evil. Ergo, why interview someone who will either look down their nose at us, and/or desert us for greener pastures as soon as their third book has been published and Yale comes calling.  They often don't seem to realize that Berkeley graduate students are sincerely interested in a wide range of academic settings for a variety of reasons personal and professional, and, perhaps more to the point, Yale rarely "comes calling."  An even greater burden of proof exists if a quick scan of your CV reveals that your all of your experience in higher education has occurred in a large, elite, research-oriented setting. How can you overcome this potential obstacle especially if you're very interested in a school that you have reason to believe may be suspicious of Berkeley PhDs?

It's probably not advisable to write in a cover letter that they shouldn't be intimidated by lil' old you (i.e., "I'm really not very good; in fact, my advisor says I'm her worst graduate student in twenty years."), but there are ways to indicate a sincere interest in their department.  One means is to do a little research, and briefly discuss how you might fit into the department and the institutional community-at-large.  There are numerous articles written by faculty about the search process that state explicitly the positive impact it can have on their impression of a candidate to see evidence that that he/she has taken the time to learn something about them. Researching a department and its associated programs/research centers has never been easier.  Virtually all colleges and universities are online, and their web addresses can be easily located using Education/Universities link.

A second way to address fears of imminent flight is to provide evidence of ties to the area, the university, or lifestyle.   If you are from the Midwest, have family nearby, or even if you just spent an enjoyable summer there, add a line about it and your desire to return to your cover letter for Purdue or Wayne State.  If you did your undergraduate work at a similar type of institution, draw their attention to that link.  Don't assume that they will notice where you got your BA on your CV, and make the connection.

If you are applying to small, liberal arts colleges, don't just list the courses you've taught with a line of boilerplate about how important you take your teaching responsibilities to be. These days, a good, small college has a list price of about $30,000 a year, and close contact with people like you is one of their key selling points to parents and potential students. You are expected to be more than a lecturer, and your ability to convey your recognition of that fact and a sincere interest in working closely with students matters. Advising, participating in non-academic activities, watching your students grow and mature inside the classroom and out (and having an influence on that process) can be among the most rewarding aspects of the profession.  If you value these broader elements of being a professor, let them know. In particular, if your own experience has been limited to large universities, think about describing an episode where you had a positive impact on the development of a student and the satisfaction you derived from helping him or her. At many small colleges, and large universities (including Berkeley) as well, one of the most significant pedagogical trends is fostering greater student involvement in faculty research.  If you can articulate how this might occur for you and their students in a brief but thoughtful manner, it can alleviate some of the concerns occasioned by your Berkeley background.

Your letter typically will have four segments: the introduction, research, teaching, and the closing.

Introduction
Be sure to identify the position you are applying for by rank and sub-field in the first sentence or two.  It is not uncommon for departments to be engaged in more than one search in a given year, and large departments may have more than one in your sub-field.  If it is an open rank position and you are applying as an assistant professor, in most cases you and your record of accomplishments will not be directly compared with those of more experienced candidates applying for it at the associate or full professor level.  Rather, applicants are assessed based on where they are in their career path, and you have every chance of successfully competing against them.

If you have finished, mention it up front. If not, state when you expect to file - no later than June 2003.  Many readers will view your optimistic prediction with a skeptical eye, and anything you can say that makes the claim appear more credible (e.g., "I have written and my chair has reviewed four of the six chapters.") can help mitigate their concerns.  You can put such a statement in the introduction or wait until you discuss the dissertation itself.

If your discipline holds its annual meeting in the summer or early fall (i.e., before application deadlines) and you had an excellent conference interview, make reference to it in the cover letter including the names of the faculty with whom you spoke.  By the time people actually start to read files, months may have passed and even the strongest of impressions can fade.  But they can be rehabilitated and revived, especially if you can remind them of a specific strength, ability, or issue that seemed particularly salient during the interview.
Research
Unless you are applying to a school that cares only about your teaching (increasingly rare), a description of your research generally follows next.  The challenge here is not simply to describe your research, but to frame it in terms of your sub-field and discipline. The search committee, hasn't lived, eaten and breathed Post-Edwardian Hermeneutics for the past five years the way you have. And they haven't been there every step of the torturous process like your friends and significant others. So forgive them for not immediately recognizing your research at first blush for the path-breaking work that it is.

Departments want to know that in hiring you, they are adding someone who will make a future contribution to the discipline and enhance the reputation of the department. However, they are often ill-equipped to understand exactly how that will be true in your particular case. Many disciplines are sufficiently broad that leading or cutting-edge research in one sub-field is barely intelligible to those in others.  In addition, when you became a candidate for the short list, your file will be read by department members outside your specialty, and, oftentimes later on in the process, by individuals outside your discipline as well. You need to describe the forest in which your tree resides, and explain why it matters in terms of the broader trends and issues within your discipline. Obviously, if your work is focused on one of the classic conundrums of your field, much less in the way of providing perspective is necessary than if you are addressing an emergent issue or employing an unconventional approach.

If your research is particularly novel or cutting-edge, any markers of broader acceptance by other, more established scholars or scholarly organs in your field can ameliorate possible concerns about its relevance and potential importance.  In discussing your work, note the recognition it has received in the form of competitive grants, awards, publications in refereed journals, and/or presentations at major conferences.

It is also important to mention where you expect your research to go after the completion of your dissertation and the publications that will flow from it.  They, especially at research-oriented institutions, want to know at least in broad terms where you expect to go from here.  They want to see evidence of a scholarly agenda that extends beyond the dissertation.  You don't need to have pages written or titles blocked out, but you need to tell them in a paragraph, (two at the most) about what questions intrigue you, and how you expect to go about finding the answers to them.  These questions for future research may have been generated by the findings of your dissertation, unusual data uncovered during your fieldwork, or interesting side issues that you were forced to put off in order to keep your dissertation taut and focused.  Think twice about mentioning future projects that appear entirely unrelated to your current work. Departments will want you to be firmly established in one area before you go off into another.

The relative importance of teaching versus research is a continuous and not a discrete variable.  Even schools that emphasize teaching in their job listing will generally want evidence of scholarly engagement and publishing potential. It is a very competitive market for students out there, and virtually all institutions are under pressure to sell themselves via the quality of their faculty to the limited number of good students in the applicant pool.  A good marker for the relative importance of teaching versus research is the teaching load.  An institution with a 3-2 teaching load (a total of five courses taught per two-semester year) will expect more in the way of and value research more highly than one with a 3-3 load.

If you work in a capital-intensive area, mention your track record of gaining grants and other sources of external funding.
Teaching
In a similar fashion, the more the institution you are applying to diverges from Berkeley and the more your profile differs from the job description, the more expansive you should be in talking about your teaching and what you have to offer their students.  If you have won a teaching award at Berkeley, don't make them wait until they read your CV to discover that fact.

For letters sent to large universities where you will be expected to teach large, lecture courses and graduate seminars, little is needed except to convey that you have the necessary experience and/or background.  Since the dominant pedagogical style is the same as that found at Berkeley, it will be assumed that you will be able to do the same for them.

If you have TA'd some of the courses that (based on the job description) you would be expected to offer, let them know.  If you have not had that opportunity, but your fields and research fall within the domain of the job description, you may want to add a line about how well prepared you are to teach such courses based on your training and research.

If your profile does not correspond exactly to the description found in the job announcement, but you believe that you could nonetheless teach the required courses, explain the basis for your confidence. What strength would you bring to the department that would more than make up for your "otherness"?  Departments may decide that they don't "need" another conventional European historian if you can convince them that you can handle the core courses and offer something new that they don't currently cover as well. In this case especially, think about doing some research so you can speak in more specific terms about how you would fit into and enhance the department's offerings. Help them visualize how you would strengthen them as a department.

Small colleges will want to know that you are able to teach on a more intimate basis and are prepared to take the time to do it well. If you give them three generic lines about how "important" you consider your teaching responsibilities, don't expect much of a positive response.  Spend a couple of paragraphs describing your teaching experience and philosophy, and how you would take advantage of the opportunity to create you own courses.

If you've had the opportunity to design and teach your own course, tell them, briefly, how you went about it and the choices you made. Don't just say you're a good teacher, tell them why. Look over your teaching evaluations and pick out one or two consistent strengths to highlight. Drawing on your experience, talk about how you engage students and enhance their skills (especially writing) and intellectual development.

For good, small colleges, the quality of the teaching offered to students is their stock-in- trade.  Even the most research-oriented, small colleges take teaching undergraduates very seriously. You need to demonstrate that you take it seriously as well, and can talk about it using more than vague generalities and shop-worn cliches.
Closing/Enclosures
Wrap it up quickly.  If you are going to be traveling for any significant portion of the job search season be sure to let them know how they can contact you (email, cellphone and/or a Pacific Bell message center account are particularly good options).

Before closing, include a sentence where you list the materials you have enclosed (e.g., CV, dissertation abstract, transcripts, teaching statement/portfolio, writing samples, etc.) and are having sent separately (letters of recommendation).  You will often be assembling multiple packets at the same time (as in midnight October 14th, midnight November 14th, etc.) for jobs that ask for different combinations of enclosures.  In addition to telling them what they should have received, it serves as a handy list for you to check before sealing the envelope.

Should you send a writing sample, even if they haven't asked for one? Unless the norm in your discipline is to never send more than they ask for, if you've been smart and have already run off thirty copies at two cents per page (that's only sixty cents for a thirty page chapter) by all means send it.  That way it's in the file should someone become interested in you and want to read more.

]]> Martin Jones