Use assembly-matched 3′UTR RNA-seq coverage to obtain a context-specific, quantitative
ranking of miRNA repression, or compare relative repression patterns across multiple samples.
Paste gene symbols (or miRNA IDs in miRNA mode), one per line or comma-separated.
Up to 200. Each returns its top hits.
About miRPRISM
miRPRISM — microRNA Prioritization by Regression-informed Integrated
Sequence-expression Modeling.
miRNA regulation is quantitative and context-dependent: the same candidate site is repressed
to different degrees depending on whether the 3′UTR region is actually expressed in a given
cellular state. Like a prism resolving mixed light into a spectrum, miRPRISM resolves
context-specific repression that static sequence tools cannot see.
The model integrates the 3′UTR sequence, its per-base RNA-seq coverage, and the miRNA sequence
through base-pairing attention, and was trained on a confidence-scored, context-resolved atlas
of repression strength (RS) derived by bootstrap elastic-net regression of target mRNA on miRNA
and transcription-factor expression. It reproduces expression-derived repression rankings on
held-out interactions and generalises to an independent paired cohort.
Predictions reflect an expression-derived repression measure, not an experimental
causal ground truth. The human model uses GRCh38; non-human results are labeled cross-species transfer
predictions and require coverage aligned to the assembly shown in the species selector.
If you use miRPRISM in your work, please acknowledge it:
“miRNA repression-strength predictions were generated with miRPRISM (https://mirprism.com).”
How to use
Reference mode: use pooled tissue-specific human 3′UTR coverage without an upload.
Upload mode: provide one sample's RNA-seq coverage as an assembly-matched
bigWig to obtain a context-specific ranking.
Compare samples: combine 2–8 uploaded samples, or human reference tissues,
to find common, sample-specific, variable and weak candidates using relative scores.
The bigWig assembly must match the selected species and displayed assembly accession.
Coverage is normalised and processed server-side. BAM files are not accepted.
