ISEScan Save

A python pipeline to identify IS (Insertion Sequence) elements in genome and metagenome

Project README

ISEScan install with bioconda install with docker

A python pipeline to identify IS (Insertion Sequence) elements in genome and metagenome

  • ISEScan can be used to identify/annotate full-length or non-full-length IS elements in any DNA sequence but ISEScan was only tested on prokarytoic genome including draft genome and meta-genome.
  • Among the existing tools identifying IS elements, ISEScan might be the only one that gives TIR (Terminal Inverted Repeat) sequences.
  • The input sequence file (namely, genome or meta-genome) of ISEScan can contain one or more sequences and there is no limit on the length of each sequence, though ISEScan was only tested on complete genome with one or more sequences, draft genome with many contigs, assembled meta-genome with many contigs.
  • The only requirment for the input sequence file is: the sequence file must be in FASTA format. When ISEScan is started, it first scans the sequences in the FASTA file one by one, then identify/annotate the IS elements in each sequence independently, finally output all identified/annotated IS elements for each sequence and the statistics of identified/annotated IS elements from all sequences in the input FASTA file.
  • Unknown bases are allowed in the sequences, e.g. ACACGCCCGTTGTTTTNNNNNNNNN, GGGTCAGGTCATCAACTTTAGCGTAACGCNNNNNGGG.
  • If you just want to identify potential transposases (not FULL or partial IS elements) in your sequences and don't like to install ISEScan, you can do so by following two steps: 1) download the transposase models (clusters.faa.hmm and clusters.single.fa) from ISEScan subdirectory pHMMs, 2) install and use software HMMER (version 3.1b2 or later) to search transposases in your sequences.
  • ISEScan users asked many good questions (see issues) which have been answered by the developer of ISEScan. If you didn't find the answers you want at issues, you can open a new issue at issues.
  • If you want to replace some (or all) of genes/proteins predicted by ISEScan (actually FraGeneScan called by ISEScan) to predict transposases and IS elements, you can try manually replacing gene boudaries and protein sequences in file .faa under directory results/proteome after you run ISEScan on your genome sequences. For how to do so, please check my comments on May 2022.

Table of Contents

Overview

ISEScan is a python pipeline to identify IS (Insertion Sequence) elements in genome. It includes an option to report either complete IS elements or both complete and partial IS elements. It might be a good idea to try reporting both complete and partial IS elements when it is used to identify the IS elements in the assemblies of metegenome. ISEScan reports both complete and partial IS elements by default.

ISEScan was developed using Python3. It 1) scans genome (or metagenome) in fasta format; 2) predicts/translates (using FragGeneScan) genome into proteome; 3) searches the pre-built pHMMs (profile Hidden Markov Models) of transposases (two files shipped with ISEScan; clusters.faa.hmm and clusters.single.faa) against the proteome and identifies the transposase gene in genome; 4) then extends the identified transposase gene into the complete IS (Insertion Sequence) elements based on the common characteristics shared by the known IS elements reported by literatures and database; 5) finally reports the identified IS elements in a few result files (e.g. a file containing a list of IS elements, a file containing sequences of IS elements in fasta format, an annotation file in GFF3 format).

Citation

Zhiqun Xie, Haixu Tang. ISEScan: automated identification of Insertion Sequence Elements in prokaryotic genomes. Bioinformatics, 2017, 33(21): 3340-3347.

Download: full text, SupplementaryMaterials.docx, SupplementaryMaterials.xlsx.

Contact

Zhiqun Xie: [email protected]

Installation

ISEScan on linux

ISEScan was tested on Linux only and can be installed from Bioconda packages and source code. Install from Bioconda is recommended as it is the simplest way for non-experienced users.

ISEScan on mac

I have no idea about ISEScan on mac as I only fully tested it on Linux. If you cannot install ISEScan on mac from Bioconda, you can try installing ISEScan from source codes. For installing ISEScan from source codes, I knew there was an issue to compile FragGensScan on Mac but I once solved it. To solve the problem of running FragGeneScan on Mac, please modify two source files in FragGeneScan source codes: 1) open util_lib.c and comment out ‘#include <malloc.h>’ on line3; 2) open hmm_lib.c and comment out ‘‘#include <malloc.h>’ on line6 and replace values.h with limits.h on line4. The modified FragGeneScan can run on Mac and Linux without problem according to my test result.

The steps below will install ISEScan package via bioconda to /apps/inst/miniconda3/. You can install ISEScan to other place by changing the default miniconda3 install path in step Install Miniconda3. Visit Bioconda recipe for ISEScan for more details (Thanks both pbasting and tseemann for making it available!).

  • Install Bioconda. To minimize the install time and size, we install miniconda 
    url -O https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
    • Install Miniconda3
    h Miniconda3-latest-Linux-x86_64.sh
    • Please answer yes (see my screen shot below) for all questions of sh Miniconda3-latest-Linux-x86_64.sh if you have no idea about the questions.
    o you wish the installer to initialize Miniconda3
y running conda init? [yes|no]
no] >>> yes

    m Miniconda3-latest-Linux-x86_64.sh
ource ~/.bashrc
    • Add the bioconda channel as well as the other channels bioconda depends on. It is important to add them in this order so that the priority is set correctly (that is, conda-forge is highest priority).
    onda config --add channels defaults
onda config --add channels bioconda
onda config --add channels conda-forge
  • Install and update ISEScan
conda install isescan
  • Try ISEScan (You can find the available command options by running isescan.py -h).
cp /apps/inst/miniconda3/test/NC_012624.fna ./
isescan.py --seqfile NC_012624.fna --output results --nthread 2

Note: replace /apps/inst/miniconda3 in commands with your conda install path.

If system reports isescan.py: command not found..., please add ISEScan package to your PATH (replace /apps/inst/miniconda3 in the command below with your conda install path):

export PATH=/apps/inst/miniconda3/bin/:$PATH

Then, try ISEScan again:

isescan.py --seqfile NC_012624.fna --output results --nthread 2

Manual install (install from source code)

  • Install ISEScan

    • Download the latest ISEScan from https://github.com/xiezhq/ISEScan/releases, e.g. Source code (tar.gz).

    • Uncompress the .zip (or .tar.gz) file.

      • Use unzip command to uncompress the zip file:
      nzip v1.7.2.2.zip
      • Use tar command to uncompress the tar.gz file:
      ar -zvxf v1.7.2.2.tar.gz

      This will create a ISEScan folder, e.g. ISEScan-1.7.2.2. You need to go to ISEScan folder to configure and run it.

      d ISEScan-1.7.2.2

  • Install dependencies before you run ISEScan

    • Python 3.3.3 or later
    • numpy-1.8.0 or later
    • scipy-0.13.1 or later
    • fastcluster, latest version recommended, https://pypi.python.org/pypi/fastcluster
    • FragGeneScan1.30 or earlier, (The .faa file output by version1.31 is not compatible with ISEScan!), http://omics.informatics.indiana.edu/FragGeneScan
    • HMMER-3.1b2 or later, http://hmmer.org/download.html
    • BLAST 2.2.31 or later
    • SSW Library, the latest version is not tested with ISEScan and the tested version of SSW library is shipped with ISEScan, please find it at ssw201507 subdirectory.
      • To use the shipped SSW library in ISEScan, please go to ssw201507 and then compile the codes by gcc:
      d ssw201507
cc -Wall -O3 -pipe -fPIC -shared -rdynamic -o libssw.so ssw.c ssw.h
      • And then copy libssw.so and set search path:
      p libssw.so ../
xport LD_LIBRARY_PATH=/home/xiezhq/projects/ISEScan-1.7.2.2:$LD_LIBRARY_PATH
      In command export LD_LIBRARY_PATH=/home/xiezhq/projects/ISEScan-1.7.2.2:$LD_LIBRARY_PATH, please replace /home/xiezhq/projects/ISEScan-1.7.2.2 with the actual path of libssw.so on your computer!
    • biopython 1.62 or later (required by SSW library)

  • Add the required packages to your $PATH before you run ISEScan

    • Add to $PATH the paths pointing to run_FragGeneScan.pl, phmmer, hmmsearch, blastn, blastp, makeblastdb
    xport PATH=$PATH:/apps/inst/FragGeneScan1.30:/apps/inst/hmmer-3.3/bin:/apps/inst/ncbi-blast-2.10.0+/bin

    In command export above, please replace /apps/inst/FragGeneScan1.30, /apps/inst/hmmer-3.3/bin and /apps/inst/ncbi-blast-2.10.0+/bin with the actual paths of FragGeneScan, HMMER and BLAST on your computer!

Upgrade ISEScan to the latest version

Automated upgrade from Bioconda

The lastest version becomes available on Bioconda is in a few hours or days after it is released on https://github.com/xiezhq/ISEScan. You can run the command below to upgrade the existing ISEScan if the existing ISEScan was installed by Bioconda.

conda update isescan

Manual upgrade from existing ISEScan

By manual upgrade, you may get the lastest version immediately from https://github.com/xiezhq/ISEScan). It is quite easy to upgrade the existing ISEScan to the latest version: copy all .py files from the latest version to the ISEScan install directory.

  • Locate the existing ISEscan (ISEScan install directory). If you don't know where isescan.py is installed, you can run which isescan.py to help find where it is on your system. 
    hich isescan.py
apps/inst/miniconda3/bin/isescan.py
  • Get the latest ISEScan source codes and then copy the all .py files to ISEScan install directory. Please check Manual install (install from source code) on how to get the latest ISEScan source codes. For example, you downlaoded the latest ISEScan, v1.7.2.2.2.tar.gz. 
    ar -zxf v1.7.2.2.2.tar.gz
d ISEScan-1.7.2.2.2/
p *.py /apps/inst/miniconda3/bin/

Check and test the upgraded ISEScan

  • Check the version of the upgraded ISEScan. 
    ython3 isescan.py --version
    or 
    sescan.py --version
  • Test the upgraded ISEScan. 
    ython3 isescan.py --seqfile /apps/inst/miniconda3/test/NC_012624.fna --output /home/xiezhq/results --nthread 2

Usage example

Let's try an example, NC_012624.fna.

  • The command below scans NC_012624.fna (genome sequence of Sulfolobus_islandicus_Y_N_15_51, ~42 kb), and outputs all results in results directory:

    p /apps/inst/miniconda3/test/NC_012624.fna ./
sescan.py --seqfile NC_012624.fna --output results --nthread 2

    Note: run isescan.py -h or isescan.py --help to get help.

  • Wait for its finishing. It may take a while (~40 seconds) as ISEScan uses the HMMER to scan the genome sequences and it will use 621 profile HMM models to scan each protein sequence (predicted by FragGeneScan) in the genome sequence. HMMER searching is usually more sensitive but slower than the regular BLAST searching for remote homologs. The running time for larger genome will increase quickly, e.g. about 20 minutes for NC_000913.fna (genome sequence of Escherichia coli str. K-12 substr. MG1655, ~4.6 Mb) with two cpu cores on my virtual machine.

  • After ISEScan finish running, you can find the output files in results directory:

    • NC_012624.fna.sum: the summarization of IS copies for each IS family
    • NC_012624.fna.csv: details about IS copies in NC_012624, one copy per line, comma-separated tabular table
    • NC_012624.fna.tsv: details about IS copies in NC_012624, one copy per line, tab-separated tabular table
    • NC_012624.fna.raw: details about IS copies in NC_012624, one copy per line
    • NC_012624.fna.gff: listing each IS copy and its TIR, gff3 format
    • NC_012624.fna.is.fna: the nucleic acid sequence of each IS copy, fasta format
    • NC_012624.fna.orf.fna: the nucleic acid sequence of the Tpase gene in each IS copy, fasta format
    • NC_012624.fna.orf.faa: the amino acid sequence of the Tpase in each IS copy, fasta format

  • Details about NC_012624.fna.sum:

    • The title line starts with #, followed by the summarization of IS content for each sequence in NC_012624. The last line is the summarization of IS content for all sequences in NC_012624.
    • Summarization of IS content for each sequence in NC_012624:
      • seqid: sequence identifier, extracted from head lines begining with > in NC_012624.fna, usuall the texts between > and the first blank character in a head line
      • family: family name of IS element
      • nIS: number of IS copies assigned to the specific family in a sequence
      • %Genome: percentage of genome sequence content spaned by IS elements in a sequence, calculated by bps4IS/dnaLen (see the following columns)
      • bps4IS: length of sequence segments spaned by IS elements in a sequence
      • dnaLen: length of the specific sequence

  • Details about NC_012624.fna.csv (NC_012624.fna.tsv, NC_012624.fna.raw):

    • The first row is header line listing column names.
    • The rows after the first row are the main content of NC_012624.fna.csv file, one IS copy per line.
    • Columns in NC_012624.fna.csv (NC_012624.fna.tsv, NC_012624.fna.raw):
      • seqID: sequence identifier
      • family: family name of IS element
      • cluster: Tpase cluster
      • isBegin and isEnd: genome coordinates of the predicted IS element
      • isLen: length of the predicted IS element
      • ncopy4is: number of predicted IS copies including full-length and partial IS copies
      • start1, end1, start2, end2: genome coordinates of the IRs
      • score: score of the IRs
      • irId: number of identical matches in pairwise alignment of left and righ hand invered repeats
      • irLen, length of inverted repeats
      • nGaps: number of gaps in IRs
      • orfBegin, orfEnd: genome coordinates of the predicted Tpase ORF
      • strand: strand where the Tpase is
      • orfLen: length of predicted Tpase ORF
      • E-value: the best E-value among all IS copies for the same IS element, the smaller the better
      • E-value4copy: the E-value of the reported IS copy, the smaller the better
        • Note: the E-value is the E-value returned by hmmer when searching profile HMMs against proteome translated from a genome sequence
      • type: type of IS element copy, 'c' for complete IS element and 'p' for partial IS element
      • ov: ov number returned by hmmer search
      • tir: terminal inverted repeat sequences

Tips to run ISEScan efficiently:

How to run a set of genomes in a row

Sometimes, we want to run hundres of genomes in one line of command and then wait for all computing jobs to complete. Before doing it, we assume:

  • You can successfully run ISEScan on one genome:
    • run commands as the following if you installed ISEScan via Bioconda.
    conda activate base
isescan.py --seqfile NC_012624.fna --output results
    • run the commands as the following if you installed ISEScan manually.
    python3 /home/xiezhq/projects/ISEScan-1.7.2.2/isescan.py --seqfile genome1.fa --output results
    where genome1.fa is your genome sequence file in fasta format. By default, ISEScan will use one CPU core but you can change it using command option --nthread NTHREAD, e.g. 
    isescan.py --seqfile genome1.fa --output results --nthread 2
  • You are running ISEScan jobs on a Linux computer instead of a Linux cluster system.
  • Your Linux computer has nproc (nproc could be 1 or 2 or 4 or 6 or 8 or ....) CPU cores.
  • You want to run ISEScan on ngenome (ngenome could be 1 or 2 or 3, ...) fasta file(s) (genome) in parallel on your Linux computer.

Now, let's run 200 genomes in one line of command and then wait for all computing jobs to complete (probably several days or weeks, depending on how many hours are required for each of your 200 genomes on average). If your computer has 8 CPU cores, you can execute the command below:

nohup cat test.fna.list | xargs -n 1 -P 4 -I{} isescan.py --seqfile {} --output results --nthread 2 > log.txt &

In the command line,

  • test.fna.list is a text file which includes 200 fasta files, one fasta file per row, for example: 
    /N/dc2/scratch/zhiqxie/hmp/HMASM/SRS014235.scaffolds.fa
/N/dc2/scratch/zhiqxie/hmp/HMASM/SRS049959.scaffolds.fa
/N/dc2/scratch/zhiqxie/hmp/HMASM/SRS020233.scaffolds.fa
/N/dc2/scratch/zhiqxie/hmp/HMASM/SRS022609.scaffolds.fa
/N/dc2/scratch/zhiqxie/hmp/HMASM/SRS024132.scaffolds.fa
  • -n 1 tells your computer to pick only one fasta file from test.fna.list for each ISEScan computing job.
  • -P 4 tells your computer to spawn 4 processes at the same time (run 4 ISEScan jobs in parallel, namely, run 4 genomes at the same time). When one job completes with success or exits with error, a new ISEScan job on the next fasta file (e.g. 5th fasta file) in test.fna.list is spawned. So, the command line will keep 4 ISEScan computing jobs (one fasta file per ISEScan job) running on your computer, and each job utilizes two CPU cores by default. It means all of 8 CPU cores on your computer have been utilized by your 4 ISEScan computing jobs till the last fasta file is processed by ISEScan.
  • > log.txt tells your computer to write the screen messages output by ISEScan to the file log.txt.
  • & tells your computer to run jobs in the background without interrupting you on the current terminal (e.g. xterm), in order that you can work on other things on the same terminal. You can check your job status by the command top -c -u xiezhq (assuming your user name is xiezhq).

It might take several days or weeks for 200 genomes to complete. It depends on how many CPU cores you have on your computer and how fast each CPU core is. Please do not load too many ISEScan jobs because each ISEScan job will consume part of your RAM on your computer. However, you can always test and estimate how many GB RAM and how many hours are required for one genome.

Re-run ISEScan without gene/protein prediction and HMMER searching

  • ISEScan will run much faster if you run it on the same genome sequence more than once (e.g., trying different optimal parameters of near and far regions (see our paper [...] for the definitions of near and far regions)) to search for IS elements in your genome). The reason is that it skips either FragGeneScan or both FragGeneScan and phmer/hmmsearch steps which are most time-consuming steps in ISEScan pipeline.
  • If you prefer ISEScan recalculating the the results, you can simply remove the proteome file and HMMER search results which are related to your genome sequence file name. For example, you can delete NC_012624.fna.faa in results/proteome directory and clusters.faa.hmm.NC_012624.fna.faa and clusters.single.faa.NC_012624.fna.faa in results/hmm directory, and then rerun it: 
    sescan.py --seqfile NC_012624.fna --output results

Release History

  • 1.7.2.3
    • remove the bug in pred.py, which cuases the issue 'UnboundLocalError: local variable raworfhits referenced before assignment' in rare cases.
  • 1.7.2.2.2
    • add code to remove temporary files (created by tempfile.NamedTemporaryFile()) once blastn search completes in case that large amounts of temporary files consume too much space. (Thanks Biancamaria for the suggestion)
  • 1.7.2.2
    • ISEScan can output .csv (columns are separated by ,) and .tsv (columns are separated by tab) result files, which are much easier for users to parse the results (Thanks oschwengers for his suggestion)
    • add command options --seqfile and --output to remove the positional parmater seqfile, proteome and hmm (Thanks oschwengers for his suggestion)
    • modify constants.py to remove the hard coded paths pointing to the third party dependencies and the output directory dir4prediction (Thanks oschwengers for his suggestion)
    • add tips for installing ISEScan from source codes on Mac (Thanks Ania Gorska for her suggestion)
  • 1.7.2.1
    • modify constants.py to remove the hard coded path poiting to the profile HMM files (clusters.single.faa and clusters.faa.hmm)
    • update readme to add an introduction for installing ISEScan package via bioconda (Thanks both pbasting and tseemann for making it available!)
  • 1.7.2.
    • Add command options --removeShortIS and --no-FragGeneScan, and remove removeShortIS and translateGenome from constants.py. (Thanks EricDeveaud for his suggestion and codes)
    • Add command option --nthread to isescan.py, and remove nthread and nproc from constants.py.
    • Remove useless parallel testing codes from code base.
  • 1.7.1
    • fix a bug in constants.py, which fails to locate the correct path pointing to profile HMM files (clusters.single.faa and clusters.faa.hmm). Thank giuliodimaria92 for it.
  • 1.7
    • Set removeShortIS = False in constants.py for ISEScan to report both complete and partial IS elements by default. One additional column (type) was added accordingly in .raw output file to label each IS element copy as either complete (c) or partial (p) IS element. For details refer to the section 'Details about NC_012624.fna.raw' in Readme.
  • 1.6
    • Update Readme about the configuration of ISEScan where the paths to clusters.faa.hmm and clusters.single.faa should also be correctly specified in constants.py (Thank Ania Gorska for it).
  • 1.5.4.3
    • Fix the bug which failed to report the Tpase ORFs in multi-copy IS elements, and ISEScan now output a .raw file with one additional column E-value4copy which is the E-value of the reported IS copy while the column E-value is the best E-value among all IS copies for the same IS element.
  • 1.5.4.1
    • fix bug for batch4bacteria.py when *.sum files were created by either outputIndividual() or outputIS4multipleSeqOneFile() in pred.py
  • 1.5.4
    • Add removeFalsePositive() to remove the potentail false positive in the 'new' family: 1) single-copy hits with e-value > e-50 or no tir or nGaps > 0 or irId < 20 or irId/irLen < 0.75; 2) multi-copy hits with evalue > e-50 and (irId < 13 or (irId < 20 and ngaps > 0))
    • Modify refineHits() to remove the single-copy partial IS elements: 1) if evalue > e-50 or (irId < 13 or (irId < 20 and ngaps > 0 for familys other than IS200/IS605)
    • Modify refineHits() to remove the multi-copy partial IS elements: 1) if evalue > e-50 for IS200/IS605 family; 2) if irId < 10 for familys other than ten familys which could have the full IS without perfect TIR (irId < 10), IS110, IS4, IS5, IS6, ISAS1, ISH3, ISNCY.
    • Change irSim4singleCopy in constants.py from 0.85 to 0.75, for the use in removeFalsePositive()
  • 1.5.3
    • Fix bug in getFullIS4seqOnStream() for genome sequence with long multi-copy fregments containing the common IS element
    • Use 'average' instead of 'single' method in fastcluster.linkage()
    • Fix bug in removeOverlappedOrfhits() to correctly count single-copy IS elements for genome sequence without multi-copy IS elements
  • 1.5.2
    • Fix bug for genome sequence without multi-copy IS elements
  • 1.5.1
    • Change: changed consensusBoundaryByCutoff() to consensusBoundaryByCutoffBySeparated()
    • Change: added consensusBoundaryByCutoffByCombined() and getbds4opt4start(), to determine the left and right boundaries of multi-copy pro-IS element simultaneously, namely, to determine the optimal combined left and right boundaries instead of separated left and right boundaries.
  • 1.5
    • Change: add consensusBoundaryByCutoff() and ncopyByCutoff() in tools.py, to determine the optimal boundary of multi-copy pro-IS element.
  • 1.4
    • Change: recruit the IS copies without predicted Tpase when search for multi-copy IS elements
  • 1.3
    • Remove buildHMM.py from ISEScan
  • 1.2
    • CHANGE: pHMMs clusters.faa.hmm and clusters.single.faa, both files are now built upon the curated ACLAME dataset (ACLAME is a mobile genetic element database.)
  • 1.1.1
    • Add option in constants.py to report either complete IS elements or both complete and partial IS elements
  • 1.0
    • The first proper release
Open Source Agenda is not affiliated with "ISEScan" Project. README Source: xiezhq/ISEScan
Stars
70
Open Issues
3
Last Commit
5 months ago
Repository
xiezhq/ISEScan
License
Apache-2.0

Open Source Agenda Badge

Open Source Agenda Rating
Submit Review Review Your Favorite Project
Submit Resource Articles, Courses, Videos
Submit Article Submit a post to our blog

From the blog

Dec 11, 2022

How to Choose Which Programming Language to Learn First?

From the blog

Dec 11, 2022

How to Choose Which Programming Language to Learn First?