PolyASE
A Python package for analyzing allele-specific expression in polyploid organisms. This package is part of the LongPolyASE framework for long-read RNA-seq allele-specific expression analysis in polyploid organisms. Please see syntelogfinder and longrnaseq for generating the input data for polyase.
Installation
PolyASE is avialble on PyPI. You can install polyase using pip:
pip install polyase
Pyranges must be installed manually for reading GTF files (most of the analysis can be run without pyranges).
To create a conda environemnt for running juypter notebook:
conda create -n polyase python=3.12 ipykernel pip && conda activate polyase && pip install polyase && pip install pyranges
Docker
A Docker image with PolyASE and JupyterLab is available on Docker Hub:
docker run --rm -p 8888:8888 \
-v $(pwd)/notebooks:/home/user/notebooks \
nadjano/polyase:1.3.3
Then open http://localhost:8888 in your browser.
Tutorial
A tutorial for analysis of allele-specific gene and isoform expression in tetraploid potato can be found here. The input data for the tutorial can be found here.
Running the tutorial within Docker
-
Download the tutorial notebook and input data:
- Notebook (download the raw file): https://github.com/NIB-SI/polyase/blob/master/docs/source/potato_polyase.ipynb
- Input data: https://zenodo.org/records/17590760/files/polyase_tutorial_atlantic.zip?download=1
-
Unzip the input data and place the notebook and all data files into a local
notebooks/folder. -
Start the container, mounting your
notebooks/folder:
docker run --rm -p 8888:8888 \
-v $(pwd)/notebooks:/home/user/notebooks \
nadjano/polyase:1.3.3
- Open http://localhost:8888 in your browser, open
potato_polyase.ipynb, and update any file paths in the notebook to/home/user/notebooks/.
Troubleshooting
if you get an error installing polyase with pip for some dependencies, e.g.:
- pyranges (a known issue on mac and windows).
- Failed to build llvmlit and numba
conda install -c conda-forge numba
conda install -c bioconda pyranges
Citation
Metadata
Release files for polyase 1.3.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| polyase-1.3.6.tar.gz | 46.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| polyase-1.3.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 97.2 kB
Release files / polyase-1.3.6.tar.gz
| Download URL | polyase-1.3.6.tar.gz |
|---|---|
| Size | 46.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9adef3ea44096cc06f324aeb8f0ccd3b7d1f719f92f290157cd740c14f4d9923
|
|
BLAKE2b-256 checksum How to use checksums |
4fa9019162a82060bdcd4571186a00cba91e24c1c40a2838a381eedde417a9f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 4, 2026.
Transparency logRelease files / polyase-1.3.6-py3-none-any.whl
| Download URL | polyase-1.3.6-py3-none-any.whl |
|---|---|
| Size | 50.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94034bf8626516deefd68725944ad2bcce50ae0b39d705b98d17330eae788bb1
|
|
BLAKE2b-256 checksum How to use checksums |
8d59cb271671e7b9c80c71140cb54a0a0bc1a5eb8c31b60772924011bafd2e75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 4, 2026.
Transparency log