IGVer
Conveniently take IGV snapshots in multiple bam files over mutliple regions.
Prerequisites
- The standard way of running
igver.pyis through docker or singularity. - Supports genomes listed in the genomes.json from the IGV team.
Installation
pip install igver
I would also suggest you pull the IGVer singularity container so it's saved to your cache, as follows. This is to ensure you're using an environment where the following are present. Also, since igver functions will invoke singularity anyways, pulling the image allows you to use the cached image instead of having to pull the image on the fly.
xvfb-run(required to redirect IGV GUI to an image)- IGV jar files, and
- IGV genome dictionaries (as in IGV Hosted Genome List)
singularity pull docker://quay.io/soymintc/igver
Features
- Load BAM files and visualize genomic regions using IGV
- Generate IGV batch scripts programmatically
- Run IGV inside a Singularity container for reproducibility
- Save IGV screenshots as high-resolution PNG files
- Load screenshots directly into Matplotlib figures for visualization
Usage
CLI
Example
igver \
-i test/test_tumor.bam test/test_normal.bam \
-r 8:32534767-32536767 "19:16780041-16782041 19:17553189-17555189" \
-o ./
Creates two png files:
-
./8-32534767-32536767.pngfor one IGV region panel -
./19-16780041-16782041.19-17553189-17555189.pngfor two IGV region panels
API
igver --helpgives:
usage: igver [-h] -i INPUT [INPUT ...] -r REGIONS [REGIONS ...] [-o OUTPUT] [-g GENOME] [--dpi DPI]
[--igv-dir IGV_DIR] [-p MAX_PANEL_HEIGHT] [-d {expand,collapse,squish}] [-c IGV_CONFIG]
[--singularity-image SINGULARITY_IMAGE] [--singularity-args SINGULARITY_ARGS] [--debug]
IGVer: A tool for generating IGV screenshots
options:
-h, --help show this help message and exit
-i INPUT [INPUT ...], --input INPUT [INPUT ...]
Input BAM, BEDPE, VCF, or bigWig file(s)
-r REGIONS [REGIONS ...], --regions REGIONS [REGIONS ...]
Genomic regions (e.g., chr1:100000-200000) or regions file (e.g. regions.txt)
-o OUTPUT, --output OUTPUT
Output directory for screenshots (default: /tmp)
-g GENOME, --genome GENOME
Genome reference (default: hg19)
--dpi DPI DPI for output images (default: 300)
--igv-dir IGV_DIR Path to IGV installation (default: /opt/IGV_2.17.4)
-p MAX_PANEL_HEIGHT, --max-panel-height MAX_PANEL_HEIGHT
Maximum panel height for IGV (default: 200).
-d {expand,collapse,squish}, --overlap-display {expand,collapse,squish}
Display mode for overlapping reads (default: squish).
-c IGV_CONFIG, --igv-config IGV_CONFIG
Path to additional IGV preferences file (optional).
--singularity-image SINGULARITY_IMAGE
`singularity` image path (default: docker://quay.io/soymintc/igver)
--singularity-args SINGULARITY_ARGS
`singularity` arguments string (default: "-B /home")
--debug Enable debug logging
Python
Example
import igver
bam_paths = ['./test/test_tumor.bam', './test/test_normal.bam']
regions = [
"8:32534767-32536767",
"19:16780041-16782041 19:17553189-17555189",
]
figures = igver.load_screenshots(bam_paths, regions)
Returns two figures:
-
figures[0]for region8:32534767-32536767 -
figures[1]for region19:16780041-16782041 19:17553189-17555189
Which you can also use .savefig to save into a given path.
API
import igver
help(igver.load_screenshots)
Will give you
load_screenshot(paths, regions, output_dir='/tmp', genome='hg19', igv_dir='/opt/IGV_2.17.4', overwrite=True, remove_png=True, dpi=300, singularity_image='docker://quay.io/soymintc/igver', singularity_args='-B /home', debug=False, **kwargs)
Generates IGV screenshots and loads them into a Matplotlib figure.
Parameters:
paths (list of str): Paths to input files (BAM, BEDPE, VCF, bigWig, etc).
regions (list of str): List of genomic regions in 'chr:start-end' format.
output_dir (str, optional): Directory for output screenshots (default: "/tmp").
genome (str, optional): Genome version (default: "hg19").
igv_dir (str, optional): Directory containing IGV installation (default: "/opt/IGV_2.17.4").
overwrite (bool, optional): Whether to overwrite existing PNG files (default: True).
remove_png (bool, optional): Whether to remove created PNG files (default: True).
dpi (int, optional): DPI of the figure (default: 300).
singularity_image (str, optional): singularity image path (default: "docker://quay.io/soymintc/igver").
singularity_args (str, optional): singularity arguments string (default: "-B /home").
debug (bool, optional): Whether to show logs for debugging (default: False).
**kwargs (optional): *kwargs* such as tag, max_panel_height, overlap_display, igv_config for create_batch_script
Returns:
matplotlib.figure.Figure: Matplotlib figure containing the IGV screenshots.
Additional IGV Preferences
- You can plug in additional IGV preferences as in https://github.com/igvteam/igv/wiki/Batch-commands -- an example would be
test/tag_haplotype.batch:
group TAG HP
colorBy TAG rl
sort READNAME
Caveat: Setting IGV Screenshot Width
- AFAIK, the only way to modify the batch screenshot width is by modifying your
${IGV_DIR}/prefs.propertiesfile. There is a line that looks something likeIGV.Bounds=0,0,640,480, meaning that IGV set the bounds of the left, top, width, height (refer to https://github.com/igvteam/igv/issues/161). I've tried to override this but seems that it doesn't work that way. For the example below, I've fixed my prefs.properties file so that the screenshot width is 800 (i.e. setIGV.Bounds=0,0,800,480).
Detailed CLI Usage Example
- An example command getting two bam files as inputr, displayed vertically in the order put in (i.e. top panel:
haplotag_tumor.bam, bottom panel:haplotag_normal.bam), is as follows. - Here,
test/tag_haplotype.batchincludes additional IGV preferences to group and color haplotagged reads, as written above.
igver \
-i test/test_tumor.bam test/test_normal.bam \
-r test/regions.txt \
-o test/snapshots \
-p 500 -d squish \
-c test/tag_haplotype.batch
- The regions file for the test case,
test/regions.txt, includes 4 lines of different regions. The number of regions in the same line will lead to a snapshot with the regions horizontally aligned. You can annotate the region with an optional final field, which you can omit. - Here's the content of
test/regions.txtand some explanation below.
8:32534767-32536767 region_of_interest
8:32534767-32536767 19:11137898-11139898 translocation
19:16780041-16782041 19:17553189-17555189 inversion
19:12874447-12876447 19:13500000-13501000 19:14461465-14463465 duplication
- The first region will take a 1001bp;1001bp snapshot on the region coined "region of interest", and create a png file
8-32534767-32536767.region_of_interest.pngin the OUTDIR. - The second region will take a 1001bp;1001bp snapshot on the two breakpoints of the translocation, and create a png file
8-32534767-32536767.19-11137898-11139898.translocation.pngin the OUTDIR. - The third region will take a 1001bp;1001bp snapshot on the two breakpoints of the inversion, and create a png file
19-16780041-16782041.19-17553189-17555189.inversion.pngin the OUTDIR. - The fourth region will take a 1001bp;1001bp;1001bp snapshot on the two breakpoints and a region inbetween, and create a png file
19-12874447-12876447.19-13500000-13501000.19-14461465-14463465.duplication.pngin the OUTDIR.
- You can see that the png files in OUTDIR includes
.tumoras a suffix. This is because the default TAG of the--tag / -toption is "tumor". You can set it to "None" to omit tagging the suffix.
Example results
- You can see the IGV snapshots already taken using the script above in
test/snapshots.
- Region of interest
- Translocation
- Inversion
- Duplication
Metadata
Release files for igver 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| igver-1.1.tar.gz | 34.7 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| igver-1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.7 MB
Release files / igver-1.1.tar.gz
| Download URL | igver-1.1.tar.gz |
|---|---|
| Size | 34.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffddac1d4e8efe24017f4e613600dfed5977e81d26d6268b720952649a96dadf
|
|
BLAKE2b-256 checksum How to use checksums |
34fd49d416961a8a8d225e78d2a0cbfb5f9c1c427c05faf6805abbd2985592af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.11.8
|
Release files / igver-1.1-py3-none-any.whl
| Download URL | igver-1.1-py3-none-any.whl |
|---|---|
| Size | 11.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c19cb9ffcba378d2f2d3d66bbcb65fdab766191af42f1d3e925870f20fb44caf
|
|
BLAKE2b-256 checksum How to use checksums |
61954c63797cd806214541b283469a3478d6038a5e7e94c755a7f199fb794269
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.11.8
|