About Vicon Nexus 2.9
Vicon Nexus 2.9 is a point release that provides features and enhancements in addition to those that were included in earlier releases of Nexus 2.
Nexus 2.9 provides the following new features and enhancements:
For a description of the other features and enhancements that have been released since Nexus 2.0, see the other Nexus What's New PDFs.
For a description of the other features and enhancements that have been released since Nexus 2.0, see the PDFs What's New in Nexus 2.8, What's New in Nexus 2.7, What's New in Vicon Nexus 2.6, What's New in Vicon Nexus 2.5 and What's New in Nexus 2.4.
To watch Nexus videos, see the Nexus 2 tutorials playlist and the Nexus 2 How To playlist on YouTube.
Location: Pipeline Tools pane > Data Processing operations
The Conventional Gait Model 2 (CGM2) is now fully integrated into Nexus, so that it is automatically installed with Nexus 2.9.
For information on using the CGM2 model with Nexus, see Modeling with CGM2 in the Vicon Nexus Reference Guide.
You can now quickly obtain feedback on the data quality of all your data captures (including those prior to Nexus 2.9) on the Data Management tab, without having to open each trial to access the information on the Quality tab.
On the default Data Management tab, a new Quality column displays data quality information about each trial.
To display quality information, if your trials:
The information displayed (from left to right) is:
If you are using a custom scheme for the Data Management tab, you can either revert to the default layout or, to add a Quality column:
You can now overlay normalized trial data (eg, gait data) in Quick Reports, so that you can quickly observe model outputs and intra-trial repeatability without having to use Polygon.
A new dropdown menu enables you to select the display mode.
You can select from these options:
Location: View pane > Camera view > View menu
You can now mirror the view displayed for both optical and video cameras.
To select this option, in a Camera view, click the View menu and then select Mirrored.
To enable you to quickly identify when you are looking at a mirrored view, the view title now displays Mirrored when this option is selected.
Location: Subjects Resources pane > Create a new subject from a Labeling Skeleton button or
C:\Program Files (x86)\Vicon\Nexus2.9\ModelTemplates
If you use a Hybrid CAST Visual3D model with Nexus, you no longer need to generate your own labeling template (VST). A Hybrid CAST Visual3D model is included with Nexus 2.9 so that the marker set is automatically labeled when you use the Auto Initialize Labeling pipeline.
Location: Options dialog box (F7) > Footstrikes option > Properties pane
You can now add a foot strike counter to the Camera view, enabling you to get quick feedback on foot contact when watching a video camera view.
You use the foot strike counter in the same way as in the 3D Perspective view (see Automatically assess foot strikes).
To display a foot strike counter in the Camera view:
In the Options dialog box (F7), ensure that Footstrikes is selected and in the Properties pane on the right, ensure Show in Video Cameras is selected.
You can't select this option while calibrating the cameras.
To change foot strike counter properties:
The following new options are available in Event Identification mode:
Time bar Zoom option
Location: Options dialog box (F7) > Time Bar option > Properties pane > Event Identification Mode section
A new option enables you to choose whether to zoom into the time bar when in Event Identification mode.
To control zooming into the time bar in Event Identification mode:
Load view type when in Event Identification mode
Location: Options dialog box (F7) > Event Identification View Options > Properties pane
To make it easier to identify an event more precisely, Nexus now provides an option for Event Identification mode that enables you to quickly load a specific view type. For example, you may find it helpful to be able to quickly view a graph of a particular marker, etc.
To specify the view type for Event Identification mode:
For information about using Event Identification mode, see Add events to trials in the Vicon Nexus User Guide.
Location: Window menu > Error Message Settings option
A new feature enables you to adjust the length of time that popup notifications are displayed and the maximum number of notifications that are displayed.
To control popup notifications:
To open the Log, click on any of the error messages.
Location: Pipeline Tools pane > Fill Gaps & Filter Data operations
A new pipeline operation enables you to run a residual analysis to determine the optimum cut-off frequencies to apply for a low pass filter for your devices.
Results are displayed in the Log and saved in the trial History.
This feature is for low pass filtering analysis only, eg, for force plates and plantar pressure plates, and not for high-pass filter devices like EMG.
To run a residual analysis for your devices:
You can use the Residual Analysis as part of a batch process.
Results of the Residual Analysis are saved in the trial History.
This example was run on the Vicon Sample Data - 2018, Kory Gait. (Note that as residual analysis was required on the selected force plates only, the Devices field was changed to Selected before the operation was run):
Location: Pipeline Tools pane > System operations
The new Set Delay Compensation pipeline operation enables you to save time and effort by applying a delay compensation for your digital devices to multiple trials simultaneously, instead of having to open each trial individually and applying the compensation.
To apply a delay compensation to your devices:
To apply the same delay compensation value to multiple trials, add the Set Delay Compensation operation to a custom pipeline and then use batch processing to run the pipeline on marked trials (see Batch process trials).
Location: Time bar context menu
Location: Pipeline Tools pane > Events & timebar operations > Delete Timebar Events operation
You now have the option to clear all events for one context only (ie, for left, right, general and custom events).
You can do this either using the time bar context menu or as a pipeline operation, which enables you to run this as a batch process.
To delete events using the time bar context menu:
To delete events using the Delete Timebar Events pipeline operation:
Two new functions,
GetDeviceChannelForFrameGlobal, enable you to access digital device data that corresponds to optical measurements.
The new functions are available in the the SDK for Python, and MATLAB.
The new functions address the issue that while the existing function
GetDeviceChannelAtFrame provides the analog frame that contains the requested optical measurement (ie, the frame number in Nexus), for digital devices the analog frame may not align with the optical measurements. The new functions return the analog samples that correspond to the optical frame requested.
Note that these functions are not available in the Datastream.
The following is an example of using
vicon = ViconNexus.ViconNexus()
# ... stuff to work out what IDs are available...
# demonstrate that the frame counters are different for the system and the forceplate (output results are different)
# demonstrate that frame length is different (different number of samples, 16 vs 10)
vicon.GetDeviceChannelAtFrame(10, 1, 1, 100)
# output ([-0.475459, 1.28333, 0.554047, -0.855607, -3.24367, -2.81851, -1.16626, -0.394893, -2.00863, -3.02354, -2.41265, -0.732007, -0.266873, -0.487017, -0.627091, 0.381795], True, 1000.0)
vicon.GetDeviceChannelForFrame(10, 1, 1, 100)
# output ([-2.00863, -3.02354, -2.41265, -0.732007, -0.266873, -0.487017, -0.627091, 0.381795, 1.51932, 1.49286], True, 1000.0)
# demonstrate that the forceplate has an initial sample offset
# (ForFrame initial sample is AtFrame's 11th sample at frame 1)
vicon.GetDeviceChannelAtFrame(10, 1, 1, 1)
# output ([0.18679, 0.174022, 0.191151, 0.301362, 0.0804058, -0.479919, -1.002, -1.38398, -1.51135, -1.14212, -0.547826, -0.127377, -0.0933952, -0.106104, -0.190911, -0.428488], True, 1000.0)
# compare this to the graphed value, initial sample here is the value at frame 1
vicon.GetDeviceChannelForFrame(10, 1, 1, 1)
# output ([-0.547826, -0.127377, -0.0933952, -0.106104, -0.190911, -0.428488, -0.649677, -0.551753, -0.666456, -0.713149], True, 1000.0
A new SDK command,
GetSubjectInfo, lets you identify which subjects are active for the current active trial.
The new command is available in the Nexus SDK for both Python and MATLAB.
Location: Pipeline Tools pane > System operations
To run a monitor as part of a pipeline:
You can run the pipeline on multiple trials via batch processing.
Location: System Preparation Tools pane > Set Volume Origin section > Show Advanced option > Auto Scale option
To achieve maximum positional reproducibility of the Vicon coordinate system, you can create a large custom L-Frame object from markers permanently placed around the edge of the volume. You can then use this L-Frame object for subsequent setting of the system origin.
This provides a high degree of precision of the coordinate system across the camera calibration, which is particularly useful in larger volumes.
To help with this, select the new Auto Scale option when you set the origin, as described below.
This improves the consistency of the volume size, further improving the positional reproducibility.
The following procedure describes how to create a custom L-frame in Nexus. You can instead create an L-frame object in Tracker and export it for use in Nexus, but remember to first copy it from your Tracker CalibrationObjects folder:
to your Nexus CalibrationObjects folder:
To perform a camera calibration with rescale:
My L-Frame), and click Create.