Redirecting to Explore
To achieve this, the user may make use of the following endpoint:
Important note: Query parameters must be percent-encoded for proper URL handling.
The following is a list of examples for various use cases:
Run + Asset + Channels
Given the following resources:
- A run named
MarsRover0.134532351
- An asset named
MarsRover0
- A channel named
voltage
. - A channel called
control_unit.cpu,temperature
.
To navigate to the explorer page, pre-populated with these resources, we would use the following percent-encoded URI:
In this particular example. since from
and to
are not specified, the explorer page will default to using the start and top times of the provided run.
If we would like to specify a custom time range like the following:
- from:
2024-02-01T23:00:05.425446Z
- to:
2024-02-01T23:00:14.038709Z
We would add them as percent-encoded query parameters like so:
A Single Run
Given the following resources, the same as before:
- A run named
MarsRover0.134532351
- An asset named
MarsRover0
- A channel named
voltage
. - A channel called
control_unit.cpu.temperature
.
We may also specify the run on its own:
Multiple Assets with Channels
Given the following resources:
-
An asset named
MarsRover0
- with channel
temperature
- with channel
-
An asset named
MarsRover1
- with channel
motor.velocity
- with channel
To view just the assets:
And to view the assets with their channels:
Redirecting Using a Run ID
If you have your run's ID on-hand, you can also visit the following URL to redirect to the explore page for your run:
So if your runID is caf9d31b-26ff-4f14-9c9b-a4ff70d79411
, the URL would look like the following: