Before using Pulsars in a live experience, make the following checks:
- Ensure Pulsars are paired with a Beacon in the volume (see Turn on the Beacon and enable pairing and Pair Pulsars with a Beacon).
- Ensure the Beacon is enabled and that on the System tab, no warning indicators are displayed.
- Turn on the Pulsars and in Evoke, check the following indicators:
- On the System tab, in the Clusters section, Pulsars are displayed.
- The connection status for all clusters is green.
- Battery levels are sufficient for the experience.
If any of the Pulsar batteries is running low (indicated in the System tree by the low battery indicator), replace it before continuing (see Swap clusters).
- No warning indicators are displayed.
- Objects are tracked and labeled in the 3D Scene.
If you need to find out which physical Pulsar is linked to its representation in Evoke, press the Pulsar's power button. It is then selected in Evoke and its status light blinks to indicate that it's currently selected.
Monitor your system
To monitor your system to ensure consistent performance, from Evoke 1.3 and later, you can remotely trigger the collection of data for a system health report while continuing to run a live experience. The report includes raw data for each camera, indicating how much data it has seen and how well it corresponds to the other cameras.
If data is collected over too short a time period, these metrics may be highly variable for some cameras.
It is strongly recommended that before analysis, you collect data over a sustained period of time, and during a standardized type of activity.
These API services are available for system health reporting:
- Start/stop/cancel report collection
- Get latest report
Information on the status of your system is accessible via the API.
An example implementation (system_health_report.py) can be found in the supplied Evoke API sample scripts.
To access the example, extract the files from the .zip file installed in this default location to a suitable folder:
You can find system_health_report.py in the sample_scripts subfolder.
The information generated for each camera includes:
- Centroid count: The number of 2D centroids seen by the camera
- Labeled centroid count: The number of centroids that correspond to a 3D model point on a tracked object
- Average reprojection error: RMS error between the observed centroid coordinates and the coordinates computed by projecting the 3D model point onto the image
The following reports were generated by running the example. Three reports were generated, showing the system running normally (Report 1), a camera having been moved (Report 2), the issue fixed and the system healthy again (Report 3):
For more information, see Vicon Evoke API & automation.