OpenMS-Insight
Interactive visualization components for mass spectrometry data in Streamlit, backed by Vue.js.
Features
- Cross-component selection linking via shared identifiers
- Memory-efficient preprocessing via subprocess isolation
- Automatic disk caching with config-based invalidation
- Cache reconstruction - components can be restored from cache without re-specifying configuration
- Table component (Tabulator.js) with server-side pagination, filtering, sorting, go-to, CSV export
- Line plot component (Plotly.js) with highlighting, annotations, zoom
- Mirror plot component for paired-spectrum comparison with independent per-side filtering and shared click selection
- Heatmap component (Plotly scattergl) with multi-resolution downsampling for millions of points
- Clustered heatmap component (Plotly) for feature-by-sample matrices, with row/column dendrograms and a group annotation bar
- Volcano plot component for differential expression visualization with significance thresholds
- PCA component for sample-level dimensionality reduction with per-group coloring and confidence ellipses
- Sequence view component for peptide visualization with fragment ion matching and auto-zoom
- Differential expression analysis (
openms_insight.analysis) - filtering, imputation, normalization, statistical testing and GO enrichment over Polars LazyFrames
Installation
pip install openms-insight
GO enrichment (openms_insight.analysis.enrichment) needs two
additional packages:
pip install "openms-insight[analysis]"
Everything else - every component, and the rest of openms_insight.analysis -
works with the base install.
Quick Start
import streamlit as st
from openms_insight import Table, LinePlot, Heatmap, VolcanoPlot, StateManager
# Create state manager for cross-component linking
state_manager = StateManager()
# Create a table - clicking a row sets the 'item' selection
table = Table(
cache_id="items_table",
data_path="items.parquet",
interactivity={"item": "item_id"},
column_definitions=[
{"field": "item_id", "title": "ID", "sorter": "number"},
{"field": "name", "title": "Name"},
],
)
table(state_manager=state_manager)
# Create a linked plot - filters by the selected 'item'
plot = LinePlot(
cache_id="values_plot",
data_path="values.parquet",
filters={"item": "item_id"},
x_column="x",
y_column="y",
)
plot(state_manager=state_manager)
Cross-Component Linking
Components communicate through identifiers using three mechanisms:
filters: INPUT - filter this component's data by the selectionfilter_defaults: INPUT - default value when selection is Noneinteractivity: OUTPUT - set a selection when user clicks
# Master table: no filters, sets 'spectrum' on click
master = Table(
cache_id="spectra",
data_path="spectra.parquet",
interactivity={"spectrum": "scan_id"}, # Click -> sets spectrum=scan_id
)
# Detail table: filters by 'spectrum', sets 'peak' on click
detail = Table(
cache_id="peaks",
data_path="peaks.parquet",
filters={"spectrum": "scan_id"}, # Filters where scan_id = selected spectrum
interactivity={"peak": "peak_id"}, # Click -> sets peak=peak_id
)
# Plot: filters by 'spectrum', highlights selected 'peak'
plot = LinePlot(
cache_id="plot",
data_path="peaks.parquet",
filters={"spectrum": "scan_id"},
interactivity={"peak": "peak_id"},
x_column="mass",
y_column="intensity",
)
# Table with filter defaults - shows unannotated data when no identification selected
annotations = Table(
cache_id="annotations",
data_path="annotations.parquet",
filters={"identification": "id_idx"},
filter_defaults={"identification": -1}, # Use -1 when identification is None
)
Components
Table
Interactive table using Tabulator.js with filtering dialogs, sorting, pagination, and CSV export.
Table(
cache_id="spectra_table",
data_path="spectra.parquet",
interactivity={"spectrum": "scan_id"},
column_definitions=[
{"field": "scan_id", "title": "Scan", "sorter": "number"},
{
"field": "rt",
"title": "RT (min)",
"sorter": "number",
"hozAlign": "right",
"formatter": "money",
"formatterParams": {"precision": 2, "symbol": ""},
},
{"field": "precursor_mz", "title": "m/z", "sorter": "number"},
],
index_field="scan_id",
go_to_fields=["scan_id"],
initial_sort=[{"column": "scan_id", "dir": "asc"}],
default_row=0,
pagination=True,
page_size=100,
)
Key parameters:
column_definitions: List of Tabulator column configs (field, title, sorter, formatter, etc.)index_field: Column used as unique row identifier (default: 'id')go_to_fields: Columns available in "Go to" navigationinitial_sort: Default sort configurationpagination: Enable server-side pagination (default: True). Only the current page of data is sent to the browser, dramatically reducing memory usage for large datasets.page_size: Rows per page (default: 100)
Custom formatters: In addition to Tabulator's built-in formatters, these custom formatters are available:
scientific: Exponential notation (e.g., "1.23e-05") - useformatterParams: {precision: 3}signed: Explicit +/- prefix (e.g., "+1.234") - useformatterParams: {precision: 3, showPositive: true}badge: Colored pill/badge for categorical values - useformatterParams: {colorMap: {"Up": "#FF0000"}, defaultColor: "#888"}
column_definitions = [
{
"field": "pvalue",
"title": "P-value",
"formatter": "scientific",
"formatterParams": {"precision": 2},
},
{
"field": "log2fc",
"title": "Log2 FC",
"formatter": "signed",
"formatterParams": {"precision": 3},
},
{
"field": "regulation",
"title": "Status",
"formatter": "badge",
"formatterParams": {
"colorMap": {"Up": "#d62728", "Down": "#1f77b4", "NS": "#888888"}
},
},
]
LinePlot
Stick-style line plot using Plotly.js for mass spectra visualization.
LinePlot(
cache_id="spectrum_plot",
data_path="peaks.parquet",
filters={"spectrum": "scan_id"},
interactivity={"peak": "peak_id"},
x_column="mass",
y_column="intensity",
highlight_column="is_annotated",
annotation_column="ion_label",
title="MS/MS Spectrum",
x_label="m/z",
y_label="Intensity",
styling={
"highlightColor": "#E4572E",
"selectedColor": "#F3A712",
"unhighlightedColor": "lightblue",
},
)
Key parameters:
x_column,y_column: Column names for x/y valueshighlight_column: Boolean/int column indicating which points to highlightannotation_column: Text column for labels on highlighted pointsstyling: Color configuration dict
MirrorPlot
Two stick-style spectra rendered against a shared x-axis with the bottom half flipped, used for comparing paired spectra (experimental vs. theoretical, sample vs. reference, MS1 vs. MS2 fragments). Each half is filtered independently, while clicks on either half feed into one shared selection.
from openms_insight import MirrorPlot
mirror = MirrorPlot(
cache_id="mirror",
data_path="peaks.parquet",
filters_top={"spectrum_a": "scan_id"}, # top half follows spectrum_a
filters_bottom={"spectrum_b": "scan_id"}, # bottom half follows spectrum_b
interactivity={"selected_peak": "peak_id"}, # click in either half -> shared
x_column="mass",
y_column="intensity", # positive for both halves
highlight_column="is_annotated",
annotation_column="ion_label",
title_top="Experimental",
title_bottom="Reference",
x_label="m/z",
y_label="Intensity",
)
mirror(state_manager=state_manager, height=600)
Key parameters:
filters_top/filters_bottom: Per-side filter mappings (independent selections drive each half)filter_defaults_top/filter_defaults_bottom: Per-side default values when the corresponding selection isNoneinteractivity: Shared across both halves — a click in either half writes the same identifierx_column,y_column: Shared schema. Provide y values as positive numbers; the bottom half is flipped at render timehighlight_column,annotation_column: Shared schema for highlights and label texttitle_top,title_bottom: In-figure labels for each half (rendered inside the plot, not above it)styling: Color dict withhighlightColor,selectedColor,unhighlightedColor(same defaults as LinePlot)
Behavior:
- The y-axis auto-rescales to the maximum visible peak when zooming, and overlapping annotation labels are re-evaluated at the new pixel/data ratio so previously hidden labels reappear when there is room (matches LinePlot's zoom behavior)
- Tick labels show absolute intensity on both sides — the bottom half is flipped only for layout, not for the displayed values
- Marker traces are kept in addition to stick shapes so Plotly fires
plotly_clickevents; the click handler picks the side viacurveNumberand routes the row's interactivity column value to the shared selection set_top_dynamic_annotations(...)/set_bottom_dynamic_annotations(...)allow another component (e.g. aSequenceView) to push fragment-ion annotations into one half without invalidating the cache
Heatmap
2D scatter heatmap using Plotly scattergl with multi-resolution downsampling for large datasets (millions of points).
Heatmap(
cache_id="peaks_heatmap",
data_path="all_peaks.parquet",
x_column="retention_time",
y_column="mass",
intensity_column="intensity",
interactivity={"spectrum": "scan_id", "peak": "peak_id"},
min_points=30000,
x_bins=400,
y_bins=50,
title="Peak Map",
x_label="Retention Time (min)",
y_label="m/z",
colorscale="Portland",
)
Key parameters:
x_column,y_column,intensity_column: Column names for axes and colormin_points: Target size for downsampling (default: 20000)x_bins,y_bins: Grid resolution for spatial binningcolorscale: Plotly colorscale name (default: 'Portland')reversescale: Invert colorscale direction (default: False)log_scale: Use log10 color mapping (default: True). Set to False for linear.low_values_on_top: Prioritize low values during downsampling and display them on top (default: False). Use for scores where lower = better (e.g., e-values, PEP, q-values).intensity_label: Custom colorbar label (default: 'Intensity')
Linear scale example:
Heatmap(
cache_id="psm_scores",
data_path="psm_data.parquet",
x_column="rt",
y_column="mz",
intensity_column="score",
log_scale=False, # Linear color mapping
intensity_label="Score", # Custom colorbar label
colorscale="Blues",
)
Low values on top (PSM scores):
For identification results where lower scores indicate better matches (e.g., e-values, PEP, q-values), use low_values_on_top=True to preserve low-scoring points during downsampling and display them on top of high-scoring points:
Heatmap(
cache_id="psm_evalue",
data_path="psm_data.parquet",
x_column="rt",
y_column="mz",
intensity_column="e_value",
log_scale=True, # Log scale for e-values
low_values_on_top=True, # Keep/show low e-values (best hits)
reversescale=True, # Bright color = low value = best
intensity_label="E-value",
colorscale="Portland",
)
Categorical mode:
Use category_column for discrete coloring by category instead of continuous intensity colorscale:
Heatmap(
cache_id="samples_heatmap",
data_path="samples.parquet",
x_column="retention_time",
y_column="mass",
intensity_column="intensity",
category_column="sample_group", # Color by category instead of intensity
category_colors={ # Optional custom colors
"Control": "#1f77b4",
"Treatment_A": "#ff7f0e",
"Treatment_B": "#2ca02c",
},
)
ClusteredHeatmap
Grid heatmap for categorical axes (e.g. proteins against samples), with optional hierarchical clustering and dendrograms on either axis.
Use this rather than Heatmap when both axes are labels rather than numbers.
Heatmap is a scattergl point cloud built for continuous axes (RT vs m/z) and
millions of points; ClusteredHeatmap renders an actual grid and ships the whole
matrix in one payload, so it expects tens to low-thousands of cells and has no
pagination, filtering or zoom machinery.
from openms_insight import ClusteredHeatmap
ClusteredHeatmap(
cache_id="protein_heatmap",
data_path="quantification.parquet", # wide: id_col + one column per sample
id_col="ProteinName",
metadata=metadata_df, # columns: sample_id, group
row_cluster=True,
col_cluster=True,
linkage_method="average",
linkage_metric="euclidean",
title="Protein Abundance",
colorscale="RdBu",
reversescale=True,
group_colors={"Control": "#1f77b4", "Treatment": "#d62728"},
)(state_manager=state_manager, height=600)
Key parameters:
id_col: Column naming each row (e.g. protein name). Every other column is treated as a sample columnmetadata: Optionalsample_id->grouptable. When given, a group color bar is drawn above the heatmaprow_cluster/col_cluster: Cluster that axis and draw its dendrogram (left for rows, top for columns). Skipped automatically when the axis has fewer than 2 entrieslinkage_method/linkage_metric: Passed through toscipy.cluster.hierarchy.linkagecolorscale,reversescale,intensity_label: Cell color mapping and colorbar labelgroup_colors: Map group value -> color for the annotation bar. Groups without an explicit color get one from a default palette
No filters or interactivity. Unlike the other components, ClusteredHeatmap
does not participate in cross-component linking: the clustered layout depends on the
full matrix, so there is nothing sensible to filter. Both arguments are accepted (they are
part of the shared signature) but have no effect on what is rendered.
The matrix must be complete when clustering. Hierarchical clustering cannot
compute distances across missing values, so the component raises a ValueError
naming the number of affected rows. Impute first (see
Differential Expression Analysis), or pass
row_cluster=False, col_cluster=False to render an incomplete matrix as-is.
Mouse-wheel zoom is disabled here. The layout anchors the heatmap, both
dendrograms and the group bar to manually positioned axes, which scrollZoom
re-ranges inconsistently. Use the mode bar's box zoom instead.
VolcanoPlot
Interactive volcano plot for differential expression analysis with significance thresholds.
from openms_insight import VolcanoPlot
VolcanoPlot(
cache_id="de_volcano",
data_path="differential_expression.parquet",
log2fc_column="log2FC",
pvalue_column="pvalue",
label_column="protein_name", # Optional: labels for significant points
filters={"comparison": "comparison_id"},
interactivity={"protein": "protein_id"},
title="Differential Expression",
x_label="Log2 Fold Change",
y_label="-log10(p-value)",
up_color="#d62728", # Color for up-regulated
down_color="#1f77b4", # Color for down-regulated
ns_color="#888888", # Color for not significant
)(
state_manager=state_manager,
fc_threshold=1.0, # Fold change threshold (render-time)
p_threshold=0.05, # P-value threshold (render-time)
max_labels=20, # Max labels to show
)
Key parameters:
log2fc_column: Column with log2 fold change valuespvalue_column: Column with p-values (automatically converted to -log10)label_column: Optional column for point labelsup_color,down_color,ns_color: Colors for significance categoriesfc_threshold,p_threshold: Significance thresholds (passed at render time, not cached)max_labels: Maximum number of labels to display on significant points
Render-time thresholds: The fc_threshold and p_threshold are passed via __call__(), not __init__(). This allows instant threshold adjustment without cache invalidation.
PCAPlot
Sample-level PCA scatter plot, computed directly from a wide quantification matrix.
from openms_insight import PCAPlot
PCAPlot(
cache_id="protein_pca",
data_path="quantification.parquet", # wide: id_col + one column per sample
metadata=metadata_df, # columns: sample_id, group
n_components=4, # compute 4 PCs, display any pair of them
standardize=True, # z-score each feature before fitting
interactivity={"sample": "sample_id"},
title="Sample PCA",
group_colors={"Control": "#1f77b4", "Treatment": "#d62728"},
show_ellipses=True,
)(
state_manager=state_manager,
pc_x=1, # x-axis component, 1-indexed (render-time)
pc_y=2, # y-axis component, 1-indexed (render-time)
)
Key parameters:
metadata:sample_id->grouptable. Required wheneverdataordata_pathis givenn_components: How many principal components to compute. Set above 2 to browse further component pairs without recomputingstandardize: Z-score each feature across samples before fitting (defaultTrue; recommended when features are on different scales)show_ellipses: Draw a 95% confidence ellipse per group. Only drawn for groups with at least 3 samplesgroup_colors: Map group value -> color. Each group is its own trace, so the legend is clickablepc_x,pc_y: Which components to plot (passed at render time, not cached)
filters and interactivity map to columns of the computed score table -
sample_id, group, and PC1..PCn - not to columns of the input matrix.
Render-time component selection: like VolcanoPlot's thresholds, pc_x and
pc_y are passed via __call__(). Switching from PC1/PC2 to PC1/PC3 re-renders
immediately; PCA itself is only recomputed when the data, metadata or
n_components change.
Axis labels default to PC{n} (xx.x%) from each component's explained variance
ratio.
SequenceView
Peptide sequence visualization with fragment ion matching. Supports both dynamic (filtered by selection) and static sequences.
# Dynamic: sequence from DataFrame filtered by selection
SequenceView(
cache_id="peptide_view",
sequence_data_path="sequences.parquet", # columns: scan_id, sequence, precursor_charge
peaks_data_path="peaks.parquet", # columns: scan_id, peak_id, mass, intensity
filters={"spectrum": "scan_id"},
interactivity={"peak": "peak_id"},
deconvolved=False, # peaks are m/z values, consider charge states
title="Fragment Coverage",
)
# Static: single sequence with optional peaks
SequenceView(
cache_id="static_peptide",
sequence_data=("PEPTIDEK", 2), # (sequence, charge) tuple
peaks_data=peaks_df, # Optional: LazyFrame with mass, intensity columns
deconvolved=True, # peaks are neutral masses
)
# Simplest: just a sequence string
SequenceView(
cache_id="simple_seq",
sequence_data="PEPTIDEK", # charge defaults to 1
)
Key parameters:
sequence_data: LazyFrame, (sequence, charge) tuple, or sequence stringsequence_data_path: Path to parquet with sequence datapeaks_data/peaks_data_path: Optional peak data for fragment matchingdeconvolved: If False (default), peaks are m/z and matching considers charge statesannotation_config: Dict with ion_types, tolerance, neutral_losses settings
Features:
- Automatic fragment ion matching (a/b/c/x/y/z ions)
- Configurable mass tolerance (ppm or Da)
- Neutral loss support (-H2O, -NH3)
- Auto-zoom for short sequences (≤20 amino acids)
- Fragment coverage statistics
- Click-to-select peaks with cross-component linking
Shared Component Arguments
All components accept these common arguments:
| Argument | Type | Default | Description |
|---|---|---|---|
cache_id |
str |
Required | Unique identifier for disk cache |
data_path |
str |
None |
Path to parquet file (preferred for memory efficiency) |
data |
pl.LazyFrame |
None |
Polars LazyFrame (alternative to data_path) |
filters |
Dict[str, str] |
None |
Map identifier -> column for filtering |
filter_defaults |
Dict[str, Any] |
None |
Default values when selection is None |
interactivity |
Dict[str, str] |
None |
Map identifier -> column for click actions |
cache_path |
str |
"." |
Base directory for cache storage |
regenerate_cache |
bool |
False |
Force cache regeneration |
height |
int |
400 |
Component height in pixels (render-time parameter) |
Memory-Efficient Preprocessing
When working with large datasets (especially heatmaps with millions of points), use data_path instead of data to enable subprocess preprocessing:
# Subprocess preprocessing (recommended for large datasets)
# Memory is fully released after cache creation
heatmap = Heatmap(
data_path="large_peaks.parquet", # triggers subprocess
cache_id="peaks_heatmap",
...
)
# In-process preprocessing (for smaller datasets or debugging)
# Memory may be retained by allocator after preprocessing
heatmap = Heatmap(
data=pl.scan_parquet("large_peaks.parquet"), # runs in main process
cache_id="peaks_heatmap",
...
)
Why this matters: Memory allocators like mimalloc (used by Polars) retain freed memory for performance. For large datasets, this can cause memory usage to stay high even after preprocessing completes. Running preprocessing in a subprocess guarantees all memory is returned to the OS when the subprocess exits.
Cache Reconstruction
Components can be reconstructed from cache using only cache_id and cache_path. All configuration is restored from the cached manifest:
# First run: create component with data and config
table = Table(
cache_id="my_table",
data_path="data.parquet",
filters={"spectrum": "scan_id"},
column_definitions=[...],
cache_path="./cache",
)
# Subsequent runs: reconstruct from cache only
table = Table(
cache_id="my_table",
cache_path="./cache",
)
# All config (filters, column_definitions, etc.) restored from cache
Rendering
All components are callable. Pass a StateManager to enable cross-component linking:
from openms_insight import StateManager
state_manager = StateManager()
table(state_manager=state_manager, height=300)
plot(state_manager=state_manager, height=400)
Differential Expression Analysis
openms_insight.analysis is the pipeline that feeds VolcanoPlot, PCAPlot and
ClusteredHeatmap: filtering, imputation, normalization, statistical testing and
GO enrichment.
It sits outside the component architecture and is deliberately not re-exported from
the package root, so import the modules directly. Note that analysis.filter
shadows the builtin filter if you import it under its bare name - the example
below aliases it:
import polars as pl
from openms_insight.analysis import filter as feature_filter
from openms_insight.analysis import imputation, normalization, statistics
Every function takes a wide-format pl.LazyFrame (one row per feature, one
column per sample) plus a sample metadata pl.DataFrame with sample_id and
group columns, and returns a LazyFrame. Nothing is collected until you ask for
it.
data = pl.scan_parquet("quantification.parquet") # ProteinName, S1 .. S6
metadata = pl.DataFrame(
{
"sample_id": ["S1", "S2", "S3", "S4", "S5", "S6"],
"group": ["Control"] * 3 + ["Treatment"] * 3,
}
)
data = feature_filter.filter_low_abundance(data, metadata, threshold_percentile=10.0)
data = feature_filter.filter_low_repeatability(data, metadata, max_missing_ratio=0.5)
data = imputation.impute_mar(data, metadata, strategy="median")
data = normalization.transform_data(data, metadata, "log2")
data = normalization.normalize_samples(data, metadata, "median", id_col="ProteinName")
data = normalization.scale_data(data, metadata, "auto_scaling")
results = statistics.calculate_statistical_tests(data, metadata, method="limma_like")
results = statistics.adjust_fdr_lazy(results, strategy="BH")
report = results.collect() # adds log2FC, stat, p-value, p-adj
Filtering
| Function | Keeps a row when |
|---|---|
filter_low_abundance |
at least one group's median clears that group's threshold_percentile cutoff |
filter_low_repeatability |
at least one group has no more than max_missing_ratio of its samples missing |
filter_low_variance |
at least one group's variance clears that group's threshold_percentile cutoff |
All three apply their cutoff per group and keep the row if any single group passes, so a feature that varies only within one condition is not discarded for having low variance overall. Zeros count as missing. A metadata table with no usable groups leaves the data unchanged rather than filtering everything away.
Imputation
impute_mar(data, metadata, strategy="median")- missing at random: fill from the feature's own mean or median within the same groupimpute_smallest_value(data, metadata, scope="row")- missing not at random: fill with the smallest observed value, per feature ("row") or across the whole matrix ("global"), on the assumption that missing MS values fall below the detection limit
Both treat explicit nulls and zeros as missing.
Normalization
| Function | Operates on | Strategies |
|---|---|---|
transform_data |
each value | "log2", "log10" (both add 1 first, so zeros do not become -inf), "square_root", "cube_root" |
normalize_samples |
whole samples (columns) | "sum", "median", "pqn", "reference_feature", "quantile" |
scale_data |
each feature (row) | "mean_centering", "auto_scaling" (Z-score), "pareto_scaling", "range_scaling" |
All three accept "None" and return the input unchanged, which makes them easy to
wire straight to a Streamlit selectbox. "reference_feature" additionally needs
reference_feature= naming a row in id_col.
Statistical testing
calculate_statistical_tests(data, metadata, method=...) adds log2FC, stat and
p-value:
| Method | Test | Groups |
|---|---|---|
"limma_like" (default) |
Empirical Bayes variance-moderated t-test / F-test | 2 / 3+ |
"welch" |
Welch's t-test (unequal variances) | exactly 2 |
"paired" |
Paired t-test | exactly 2, equal size |
"anova" |
One-way ANOVA F-test | 3+ |
limma_like shrinks each feature's variance towards a common prior, which is what
makes small-n experiments usable. Everything is expressed as lazy Polars operations
and only drops into SciPy for the final p-value.
adjust_fdr_lazy(results, strategy=...) then adds p-adj, using "BH"
(Benjamini-Hochberg, the default), "Bonferroni", or "None" to copy p-value
through unchanged.
The result feeds VolcanoPlot directly:
VolcanoPlot(
cache_id="de_volcano",
data=results,
log2fc_column="log2FC",
pvalue_column="p-adj",
label_column="ProteinName",
)(state_manager=state_manager, fc_threshold=1.0, p_threshold=0.05)
GO enrichment
calculate_go_enrichment annotates UniProt accessions via
MyGene.info and runs Fisher's exact test per GO term, for
each of the BP, CC and MF categories.
It is the odd one out in this module: it makes a live network call, takes an
eager pl.DataFrame, and returns a (status, payload) tuple instead of raising,
so callers can tell "not enough significant proteins" apart from a hard failure.
from openms_insight.analysis.enrichment import calculate_go_enrichment
status, payload = calculate_go_enrichment(
report, # eager DataFrame with an ID column, log2FC, and a p-value column
id_col="ProteinName",
target_p_col="p-adj",
p_cutoff=0.05,
fc_cutoff=1.0,
)
if status == "success":
for category, result in payload["categories"].items():
st.plotly_chart(result["fig"]) # "BP" | "CC" | "MF"
status is "success", "insufficient_proteins" (fewer than 3 proteins pass the
cutoffs) or "empty_data". This function needs the analysis extra:
pip install "openms-insight[analysis]"
Development
For a comprehensive guide to the internal architecture, conventions, and pitfalls, see CONTRIBUTING.md.
Building the Vue Component
cd js-component
npm install
npm run build
Development Mode (Hot Reload)
# Terminal 1: Vue dev server
cd js-component
npm run dev
# Terminal 2: Streamlit with dev mode
SVC_DEV_MODE=true SVC_DEV_URL=http://localhost:5173 streamlit run app.py
Debug Mode
Enable hash tracking logs to debug data synchronization issues:
SVC_DEBUG_HASH=true streamlit run app.py
Running Tests
# Python tests
pip install -e ".[dev]"
pytest tests/ -v
# TypeScript type checking
cd js-component
npm run type-check
Linting and Formatting
# Python
ruff check .
ruff format .
# JavaScript/TypeScript
cd js-component
npm run lint
npm run format
Release files for openms-insight 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| openms_insight-0.2.0.tar.gz | 4.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openms_insight-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.4 MB
Release files / openms_insight-0.2.0.tar.gz
| Download URL | openms_insight-0.2.0.tar.gz |
|---|---|
| Size | 4.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87231943bf3a23be10996b8ef520d228eca148ca0318fbb623413673643a69dc
|
|
BLAKE2b-256 checksum How to use checksums |
c96e598041f679ef613e3b4c38ff11be00b63eb326f452eacb911657fe71f076
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 18, 2026.
Transparency logRelease files / openms_insight-0.2.0-py3-none-any.whl
| Download URL | openms_insight-0.2.0-py3-none-any.whl |
|---|---|
| Size | 4.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b57bb8a9dacfbb5dd6bc70127139447dc3cc54bb976748fd673e6ed55558144a
|
|
BLAKE2b-256 checksum How to use checksums |
797c14d81566b2ced5be2f88c71a5c54d5b80af85a06e6f841757a082032410c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 18, 2026.
Transparency log