Skip to main content
After completing this topic, you can align multiple Runs with a common reference point to compare signals across Runs on a shared timeline.

​
Before you begin

  • You have at least two Runs plotted in the same Panel in Explore.

​
How Run alignment works

Runs rarely start at the same absolute time, so plotting them together without alignment results in signals that appear offset. Alignment solves this by defining a shared T-0 reference point for each Run, converting absolute timestamps to relative time so signals line up for direct comparison. You can align Runs to a Run start, Run end, a specific timestamp, or an Annotation. For supported alignment methods, see Time alignment.

​
Create a relative time alignment

  1. In an Explore Panel with at least two Runs plotted, click Settings.
  2. Open the Time-alignment tab.
  3. In the Alignment list, select Create relative alignment.
  4. In the Name box, enter a name for the alignment.
  5. In the Default alignment method list, select a method.
  6. Optional: Configure how the alignment is applied:
    • To apply the alignment method to all Runs, click Apply default to all.
    • To configure an individual Run, select a method from the Alignment method list in the Run’s tile under Alignment points.
  7. Optional: Configure additional settings if you selected Timestamp or Annotation as the method.

​
Align to an event using an Annotation

To align Runs to an Annotation, each Run needs a matching Annotation marking the event before you can select it as an alignment point. Add the Annotation using one of the following methods:
  • Rule-based: Create a Rule whose expression detects the event, then evaluate the Rule against each Run you want to align. An Annotation is not created until the Rule has been evaluated against that Run’s data.
  • Manual: Add an Annotation directly on a Run in Explore, without a Rule. Use this for a one-off alignment that doesn’t need to repeat across future Runs.
Once each Run has the Annotation, select Annotation as the alignment method and point it at that Annotation’s start or end. All Runs then share a common relative T-0 anchored to the event.

​
Reference