Skip to main content

rnpfind

Command line tool for collecting and generating RNA-RBP interaction data in various formats.

Installation

pip install rnpfind

Requirements:

  • Python >=3.8

Usage

rnpfind can be used as a command line tool as follows:

rnpfind <transcript>

where transcript is a gene name such as "PTEN", or an hg38 coordinate range (such as 11:65497688-65506516)

Note: If a transcript is specified through genomic coordinates, the transcript is assumed to be on the forward strand (the "+" strand). On the other hand, a transcript specified by name will have its strand positioning correctly identified.

The tool takes a transcript as input, and computes the binding sites of various RBPs on the transcript. The information is collected from data sources including RBPDB, ATTRACT, and POSTAR.

The tool produces as output the binding data in a folder (use --out-dir to specify). A few output formats are supported (use --out-format to specify):

  • bed format: a widely used format for displaying intervals. A bed file created in this way could be visualized on a genome browser, for example. Note the --trackhub option avaiable to generate a trackhub structure (useful for hosting a large number of indexed bed files (bigBed files) and allowing users to view on genome browsers like the UCSC Genome Browser.

  • csv format: an NxN table (where N=number of RBPs) showing binding correlations of RBPs on the particular transcript analyzed. This could be useful for inferring molecular mechanisms on certain regions of the transcriptome.

For more options, run rnpfind --help

Within Python

You can import rnpfind to your Python code as follows:

from rnpfind import rnpfind

# Collect data on Malat1
rnpfind("malat1")

The data is written to disk like in the command line call. Check help(rnpfind) for keyword arg options.

Perhaps not so usefully, you can find the genome version rnpfind is working with programatically:

from rnpfind import GENOME_VERSION
print(GENOME_VERSION)

How does it work?

In principle, RNA-RBP interactions can be backed by two forms of evidence: experimental and computational.

The experimental binding sites are collected on large databases such as POSTAR. The computational binding sites are generated by scanning RNA-binding-motifs of various RBPs (collected from RBPDB and ATTRACT) across a transcript to look for hits.

As a result, the tool requires around 6.4GB to function. The data is downloaded automatically on the first run of the tool, or can be downloaded manually using rnpfind-download.

If the above memory footprint is too much for you to handle, consider using the web tool avaiable at https://rnpfind.com

Contributing

Any suggestions / PR requests are welcome!

Metadata

Release files for rnpfind 1.2.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rnpfind 1.2.6
File Size Uploaded Provenance Actions
rnpfind-1.2.6.tar.gz 8.9 MB Without provenance Details for rnpfind-1.2.6.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for rnpfind 1.2.6
File Interpreter ABI Platform Actions
rnpfind-1.2.6-py3-none-any.whl Python 3 none any Details for rnpfind-1.2.6-py3-none-any.whl

Total release size: 17.8 MB

Release files / rnpfind-1.2.6.tar.gz

Download URL rnpfind-1.2.6.tar.gz
Size 8.9 MB
Tags Source
SHA-256 checksum
How to use checksums
da97c4d9feba6e6c5787145e121a79b25a2b5df0d5955650fd9f9f9883d5a154
BLAKE2b-256 checksum
How to use checksums
91c39da83ce4fcfe4270c9a2d10ae63659ce5594391e5299461379ab5cec351e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.9.7

Release files / rnpfind-1.2.6-py3-none-any.whl

Download URL rnpfind-1.2.6-py3-none-any.whl
Size 8.9 MB
Tags Python 3
SHA-256 checksum
How to use checksums
5896fc449078cb9efedd6461b9384573d06269ab33680c9cfa2461ae65046dea
BLAKE2b-256 checksum
How to use checksums
7f7a0480f8aac5d9fc1779905a5ba0c0c3fa2a4a6563009b90a7f7d18fd85ce9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.1 CPython/3.9.7

Security for rnpfind 1.2.6

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page