FullPlot
FullPlot is a lightweight HDF5 plotting, trace-processing, and map-generation package for engineering simulation and test data.
It is designed for workflows where the data is already in HDF5 and the user wants a simple Python interface for inspecting, plotting, filtering, aligning, and saving engineering traces without building a large application around the file format.
FullPlot is especially useful for:
- simulation outputs stored in HDF5,
- rocket-engine and test-stand time histories,
- generic sensor data,
- controller commands and sequence traces,
- redline, blueline, yellowline, and greenline overlays,
- quick HDF5 inspection,
- 1D trace overlays,
- dual-axis plots,
- 2D heat maps,
- multidimensional dataset slicing,
- simple rectangular-grid map generation for downstream tools such as FullFlow.
FullPlot does not require a special FullFlow file format. If your HDF5 file contains normal numeric datasets, FullPlot can inspect and plot them.
Repository status for 0.1.0
FullPlot 0.1.0 is prepared as the first publish-ready public release of the package.
There is no separate official documentation site yet, so the repository is intentionally documentation-heavy:
README.mdis the primary user guide.CHANGELOG.mdrecords release-level changes and bug fixes.PUBLISHING.mdrecords the build, smoke-test, artifact-inspection, and upload checklist.THIRD_PARTY_LICENSES.mdrecords dependency and license notes.examples/contains detailed runnable examples.- Public classes, functions, properties, and exceptions include docstrings so
help(fullplot.Trace), IDE inspection, and future generated API docs are useful immediately.
The 0.1.0 release focuses on documentation, packaging, smoke testing, public API docstrings, and fixing obvious publish-blocking bugs. The core plotting, trace, and map-generation model is intentionally small.
Installation
pip install fullplot
FullPlot requires Python 3.11 or newer.
For local development from the repository:
python -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install -e .
python -m pytest
With uv:
uv sync --dev
uv run pytest
Quick start
Create or open an HDF5 file that contains a time dataset and one or more numeric channels:
hotfire.h5
├── time
├── PCMC_1
├── PCMC_2
├── PCMC_3
├── OIPT
├── FIPT
├── PBTC_1
└── MOV_CMD
Plot a single trace:
import fullplot as fplt
run = fplt.open("hotfire.h5")
run.plot(
x="time",
y="PCMC_1",
xlabel="Time [s]",
ylabel="Pressure [psia]",
title="Chamber Pressure",
)
Plot several traces:
run.plot(
x="time",
y=["PCMC_1", "PCMC_2", "PCMC_3"],
xlabel="Time [s]",
ylabel="Pressure [psia]",
title="Chamber Pressure Sensors",
)
Make a dual-axis plot:
run.plot(
x="time",
y=["PCMC_1", "OIPT", "FIPT"],
y2="MOV_CMD",
xlabel="Time [s]",
ylabel="Pressure [psia]",
y2label="Command [-]",
title="Pressure and Main Ox Valve Command",
)
Save a figure without showing a GUI window:
run.plot(
x="time",
y="PCMC_1",
save="pcmc_1.png",
show=False,
)
HDF5 inspection
FullPlot starts with inspection. Use tree() when you want to see the file layout and list() when you want the datasets grouped by dimensionality.
import fullplot as fplt
run = fplt.open("hotfire.h5")
run.tree()
run.list()
The same operations are available at module level:
fplt.tree("hotfire.h5")
fplt.list("hotfire.h5")
You can scope an H5File to a group:
run = fplt.open("engine_sim.h5")
transient = run.at("/Engine/transient/runs/startup")
transient.tree()
transient.plot(x="time", y="Chamber_Pressure")
Dataset selectors can be:
- absolute HDF5 paths, such as
"/Engine/transient/time", - paths relative to the current root, such as
"tracks/PCMC_1", - unique short names, such as
"PCMC_1".
If a short name matches more than one dataset, FullPlot raises AmbiguousDatasetError instead of guessing.
Read a raw dataset:
pressure = run.read("PCMC_1")
Read scalar datasets under a group:
settings = run.values("metadata")
Core public API
Most users only need these names:
import fullplot as fplt
fplt.open
fplt.plot
fplt.map
fplt.tree
fplt.list
fplt.read
fplt.time
fplt.trace
fplt.write_traces
fplt.Trace
fplt.TimeAxis
fplt.Axis
fplt.generate_map
The main classes are:
| Name | Purpose |
|---|---|
H5File |
Lightweight handle for one HDF5 file and root group. Created with fplt.open(...). |
Trace |
Reusable one-dimensional x/y data object. Used for raw data, filtered data, generated limits, commands, and derived traces. |
TimeAxis |
Shared shiftable time basis. Several traces can share one time axis and be shifted together. |
Axis |
Independent variable definition for rectangular-grid map generation. |
Important exceptions are:
| Name | Meaning |
|---|---|
FullPlotError |
Base package exception. |
DatasetNotFoundError |
A requested HDF5 dataset or group could not be found. |
AmbiguousDatasetError |
A short name matched more than one HDF5 object. |
PlotDataError |
Data shape, type, dimensionality, or scale is invalid for plotting or trace creation. |
FullPlotMapError |
Base map-generation exception. |
MapGenerationError |
Map generation failed during evaluation, resume, or file layout validation. |
MapOutputError |
The map evaluate(...) function returned invalid outputs. |
Trace objects
A Trace is a one-dimensional line of data:
import fullplot as fplt
run = fplt.open("hotfire.h5")
time = run.time("time")
pc = run.trace(y="PCMC_1", x=time, name="Chamber Pressure")
A trace stores:
x: current x-values,y: y-values,name: legend/display name,role: plotting role,attrs: metadata dictionary.
Useful trace attributes:
pc.x
pc.y
pc.value
pc.time
pc.finite
pc.tmin
pc.tmax
pc.time_range
Create traces directly from arrays:
import numpy as np
import fullplot as fplt
x = np.linspace(0.0, 10.0, 1001)
y = 300.0 + 10.0 * np.sin(x)
trace = fplt.Trace.from_arrays("Synthetic Pressure", x=x, y=y)
Create a constant reference trace:
redline = fplt.Trace.constant("PCMC Redline", x=pc.x, y=400.0, role="redline")
Create a command or sequence trace from points:
mov_command = fplt.Trace.from_points(
"MOV Command",
points=[
(0.0, 0.0),
(0.5, 0.0),
(0.6, 1.0),
(10.0, 1.0),
(10.1, 0.0),
],
x=pc.x,
mode="previous",
role="command",
)
Create an analytic trace from a function:
reference = fplt.Trace.from_function(
"Reference",
x=pc.x,
function=lambda t: 300.0 + 5.0 * np.sin(2.0 * np.pi * 0.2 * t),
)
Plot trace objects directly:
fplt.plot([pc, redline, mov_command])
Trace roles
Trace roles are plotting hints. They do not perform limit checking, abort checking, controller execution, or sequence execution.
Valid roles are:
| Role | Intended meaning | Default line style |
|---|---|---|
"data" |
Normal measured or simulated data | solid |
"redline" |
Abort or hard limit reference | dashed red-tinted line |
"blueline" |
Lower/secondary reference | dashed blue-tinted line |
"yellowline" |
Warning or caution reference | dashed yellow-tinted line |
"greenline" |
Nominal target or expected value | dashed green-tinted line |
"command" |
Command, schedule, or sequence state | dash-dot step line |
Example:
redline = fplt.Trace.constant("Abort", x=pc.x, y=400.0, role="redline")
yellowline = fplt.Trace.constant("Warning", x=pc.x, y=350.0, role="yellowline")
greenline = fplt.Trace.constant("Target", x=pc.x, y=300.0, role="greenline")
fplt.plot([pc, redline, yellowline, greenline])
Shared time axes and test-data alignment
TimeAxis is useful when several traces should move together in time.
time = run.time("time")
pc = run.trace(y="PCMC_1", x=time)
oipt = run.trace(y="OIPT", x=time)
fipt = run.trace(y="FIPT", x=time)
Shift the shared time axis so raw test time 95 seconds becomes model time zero:
time.zero_at(95.0)
All three traces now report shifted x-values because they share the same TimeAxis object.
Use align(...) when matching a raw data time to a model time:
time.align(data_time=95.0, model_time=0.0)
Useful TimeAxis attributes:
time.raw # original samples
time.values # shifted samples
time.value # alias for values
time.time # alias for values
time.zero # current zero offset
time.dt # median sample spacing
time.dt_array # array of adjacent spacings
time.duration # raw time span
time.is_uniform # approximate uniform-spacing check
Missing values and windows
FullPlot preserves non-finite y-values such as NaN. This is deliberate. Missing test-data samples should appear as gaps in plots instead of being connected by a misleading line.
Create a windowed trace:
startup = pc.window(start=0.0, stop=3.0, name="Startup Window")
Trace.window(...) keeps the full time axis and replaces values outside the window with NaN. This is useful when a solver or comparison routine should know that the trace only provides valid data inside a specific interval.
Remove missing samples when you explicitly need compact finite data:
pc_compact = pc.omit_missing()
drop_missing is an alias:
pc_compact = pc.drop_missing()
Filtering and trace math
Filter a trace:
pc_filtered = pc.filter("moving_average", window=0.05, name="PCMC Filtered")
Supported filters:
pc.filter("moving_average", window=0.05)
pc.filter("median", window=0.05)
pc.filter("savgol", window=0.05, order=2)
pc.filter("lowpass", cutoff=50.0)
For moving-average, median, and Savitzky-Golay filters, window can be either:
- an integer sample count, or
- a positive x-width, such as seconds when x is time.
Scale or offset a trace:
pressure_pa = pc.scale(6894.757, name="Pressure [Pa]")
pressure_gauge = pc.offset(-14.7, name="Gauge Pressure")
Compute a numerical derivative:
pc_rate = pc.derivative(name="dPc/dt")
Resample a trace:
new_time = np.linspace(0.0, 10.0, 1001)
pc_resampled = pc.resample(new_time)
Do trace math. When combining two traces, FullPlot automatically resamples the right-hand trace onto the left-hand trace x-axis:
error = sim_pc - test_pc
ratio = sim_pc / test_pc
Sample a trace at one or more x-values:
value = pc.value_at(1.25)
values = pc.value_at([1.0, 1.5, 2.0], method="linear")
value = pc(1.25, method="nearest")
Supported sample methods are "previous", "linear", and "nearest".
Supported bounds modes are:
"nan": returnNaNoutside the trace range,"clamp": use the first or last sample outside the trace range,"raise": raise an error outside the trace range.
Writing processed traces
Write one or more Trace objects to a simple HDF5 layout:
fplt.write_traces(
"processed_traces.h5",
[pc, pc_filtered, redline],
group="traces",
overwrite=True,
)
The file layout is:
processed_traces.h5
└── traces
├── PCMC_1
│ ├── x
│ └── y
├── PCMC_Filtered
│ ├── x
│ └── y
└── PCMC_Redline
├── x
└── y
Trace metadata is stored as HDF5 attributes when possible.
Line plotting options
H5File.plot(...) and fplt.plot(...) support:
- single or multiple left-axis traces,
- optional right-axis traces with
y2, - HDF5 datasets and
Traceobjects in the same plot, - custom labels,
- log x/y axes,
- dark and light themes,
- saving to PNG, SVG, PDF, or any Matplotlib-supported output,
- returning Matplotlib objects for custom edits.
Example with labels and a right axis:
fig, axes = run.plot(
x="time",
y=["PCMC_1", "PCMC_2"],
y2="MOV_CMD",
labels=["PC 1", "PC 2"],
y2labels=["MOV"],
xlabel="Time [s]",
ylabel="Pressure [psia]",
y2label="Command [-]",
title="Pressure and Valve Command",
theme="light",
save="pressure_command.svg",
show=False,
)
For module-level plotting:
fplt.plot(
"hotfire.h5",
x="time",
y="PCMC_1",
)
For trace-only plotting:
fplt.plot([pc, pc_filtered, redline])
Multidimensional datasets
FullPlot can expand a 2D or higher-dimensional dataset into several line traces.
Use axis to choose which dimension becomes the line direction:
run.plot(
x="time",
y="pressure_grid",
axis=-1,
)
Use slice to reduce higher-dimensional arrays before plotting:
run.plot(
x="time",
y="pressure_3d",
slice={0: 1},
axis=-1,
)
The same idea applies to maps. A 3D dataset can become a 2D heat map after slicing:
run.map(
z="temperature_3d",
slice={0: 2},
)
Heat maps
Plot a 2D dataset:
run.map(
z="pressure_map",
x="mixture_ratio",
y="chamber_pressure",
xlabel="Mixture Ratio [-]",
ylabel="Chamber Pressure [Pa]",
zlabel="Temperature [K]",
)
Stack several 1D datasets into a heat map:
run.map(
z=["TC_1", "TC_2", "TC_3", "TC_4"],
x="time",
ylabel="Station Index",
zlabel="Temperature [K]",
)
Use log scales when all displayed values are positive:
run.map(
z="residual_map",
x="iteration",
y="case",
zscale="log",
)
Map generation
FullPlot can generate simple rectangular-grid HDF5 maps.
The generated layout is intentionally generic:
demo_map.h5
└── properties
├── axes
│ ├── pressure
│ └── temperature
├── outputs
│ ├── density
│ └── enthalpy
└── status
├── success
└── message
Generate a map:
import fullplot as fplt
fplt.generate_map(
"demo_map.h5",
group="properties",
axes=[
fplt.Axis.linear("pressure", 1.0e5, 5.0e5, 5, units="Pa"),
fplt.Axis.linear("temperature", 250.0, 500.0, 6, units="K"),
],
constants={"gas_constant": 287.0},
evaluate=lambda pressure, temperature, gas_constant: {
"density": pressure / (gas_constant * temperature),
"enthalpy": 1005.0 * temperature,
},
overwrite=True,
)
Axis helpers:
fplt.Axis.linear("temperature", start=250.0, stop=600.0, count=8, units="K")
fplt.Axis.log("pressure", start=1.0e5, stop=1.0e7, count=9, units="Pa")
fplt.Axis.values("mixture_ratio", values=[1.5, 2.0, 2.5, 3.0])
Use constants={...} for values that should be passed to every evaluation but should not become interpolation axes.
The evaluate(...) function must return a flat dictionary of scalar numeric outputs. Each key becomes one dataset in /outputs.
Example:
def evaluate(pressure, temperature, gas_constant):
density = pressure / (gas_constant * temperature)
return {"density": density}
generate_map(...) supports:
- explicit output names with
outputs=[...], - overwrite protection with
overwrite=True, - interrupted-map continuation with
resume=True, - configurable failure behavior with
raise_errors=False, - optional compression,
- metadata storage.
A robust long-running map call might look like this:
fplt.generate_map(
"engine_map.h5",
group="chamber",
axes=[
fplt.Axis.log("pressure", 1.0e5, 1.0e7, 25, units="Pa"),
fplt.Axis.values("mixture_ratio", [1.5, 2.0, 2.5, 3.0]),
],
constants={"area": 0.0039},
outputs=["temperature", "gamma", "molecular_weight"],
evaluate=evaluate_chamber,
metadata={"description": "Chamber property map"},
resume=True,
raise_errors=False,
fill_value=float("nan"),
)
Command-line inspection
FullPlot installs a small fullplot command for HDF5 inspection.
Print a tree:
fullplot hotfire.h5
fullplot hotfire.h5 --tree
List datasets:
fullplot hotfire.h5 --list
Inspect a root group:
fullplot engine_sim.h5 --root /Engine/transient/runs/startup --list
Limit tree depth:
fullplot engine_sim.h5 --max-depth 2
The CLI does not create plots. Use the Python API for plotting so scripts can control Matplotlib backends, figure editing, saving, and showing.
Examples
The repository includes three example folders:
examples/
├── hdf5_plotting/
├── maps/
└── traces/
examples/hdf5_plotting/ demonstrates:
- generating a synthetic HDF5 plotting file,
- inspecting the tree and dataset list,
- single-trace plots,
- multiple-trace plots,
- dual-axis plots,
- 2D heat maps,
- stacked 1D heat maps,
- log axes and log color scales,
- multidimensional line traces,
- multidimensional slices,
- light theme plots,
- module-level API calls,
- saving figures.
examples/traces/ demonstrates:
- generating synthetic hotfire-style sensor data,
- extracting reusable traces,
- filtering,
- redlines/bluelines/yellowlines/greenlines,
- command and sequence traces,
- trace math and automatic resampling,
- windowing,
- scaling and offsetting,
- derivatives,
- saving processed traces,
- missing-value handling,
- shared
TimeAxisalignment.
examples/maps/ demonstrates:
- simple map generation,
- linear/log/explicit axes,
- constants,
- metadata,
- output discovery,
- HDF5 layout inspection.
Themes
FullPlot includes two themes:
run.plot(x="time", y="PCMC_1", theme="dark")
run.plot(x="time", y="PCMC_1", theme="light")
The dark theme is useful for quick interactive engineering plots. The light theme is better for reports, documents, and slides.
Units
FullPlot does not perform unit conversion.
It reads numeric arrays and uses labels provided by the user or stored in HDF5 attributes. This keeps FullPlot generic and avoids guessing how engineering units should be converted.
Recommended practice:
run.plot(
x="time",
y="PCMC_1",
xlabel="Time [s]",
ylabel="Pressure [psia]",
)
If you need converted data, convert explicitly with trace math:
pc_pa = pc.scale(6894.757, name="PCMC_1 [Pa]")
Limitations and design choices
FullPlot is intentionally small.
Current limitations:
- HDF5 is the only supported file format.
- The package focuses on numeric datasets.
- There is no built-in unit conversion.
- There is no built-in DAQ metadata standard.
- Trace roles are plotting hints only.
- Redlines and commands are not safety logic.
- Map generation is for rectangular grids only.
- Map outputs must be scalar numeric values.
- Interpolation and filtering are intentionally simple and NumPy/SciPy based.
- FullPlot does not attempt to replace specialized dashboards, data historians, or test-stand control software.
This is deliberate. The package is meant to be a simple bridge between HDF5 engineering data and Python plotting/processing workflows.
Development checks
Useful local checks:
python -m compileall -q src tests examples
python -m pytest -q
uv build
A minimal smoke test:
import tempfile
from pathlib import Path
import h5py
import numpy as np
import fullplot as fplt
with tempfile.TemporaryDirectory() as tmp:
filename = Path(tmp) / "demo.h5"
with h5py.File(filename, "w") as h5:
h5["time"] = np.linspace(0.0, 1.0, 11)
h5["pressure"] = np.linspace(100.0, 200.0, 11)
run = fplt.open(filename)
time = run.time("time")
pressure = run.trace("pressure", x=time)
redline = fplt.Trace.constant("redline", x=time, y=250.0, role="redline")
run.plot(x="time", y="pressure", show=False)
fplt.plot([pressure, redline], show=False)
License
FullPlot is released under the GNU General Public License v3.0 only (GPL-3.0-only). See LICENSE for the full text.
See THIRD_PARTY_LICENSES.md for dependency license notes.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file fullplot-0.1.0.tar.gz.
File metadata
- Download URL: fullplot-0.1.0.tar.gz
- Upload date:
- Size: 74.4 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
f6f04ab82996b1cf6fa92ae98412b5b3182a8f702f0a851f8ad3c909011e62ac
|
|
| MD5 |
5ebbd0d0bcdac2a4ccc2aa06733f89aa
|
|
| BLAKE2b-256 |
3c48da3f46cac6039d54bff5d45f75faf43788ce85a1575fc08d3e980f5c6b56
|
File details
Details for the file fullplot-0.1.0-py3-none-any.whl.
File metadata
- Download URL: fullplot-0.1.0-py3-none-any.whl
- Upload date:
- Size: 51.1 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via:
uv/0.11.28 {"installer":{"name":"uv","version":"0.11.28","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6372d4064807d1a66fb715a5259c01495f9b47dbe6130dda3321543e14651a0d
|
|
| MD5 |
44edb8d2b886190960e308e008c4aab2
|
|
| BLAKE2b-256 |
d32385e6a9c11294dc86c267346989bd56db9247b601638d77fbbc9e86dc559a
|