Differences

This shows you the differences between two versions of the page.

--- visual3d:documentation:emg:processing:onset_based_on_tko [2024/06/19 12:47] – sgranger
+++ visual3d:documentation:emg:processing:onset_based_on_tko [2024/07/17 15:45] (current) – created sgranger
@@ Line 1: / Line 1: @@
-{{===== general processing steps =====
+====== Onset Based on TKO ======
-processing emg signals typically follows some variation of the following steps:
+==== General Processing Steps ====
-. high pass filter
+Processing EMG signals typically follows some variation of the following steps:
-. low pass filter
-. rectify data
-. filter noise
-. normalize and scale data
-it should be noted that within both this page and external literature, the term "linear envelope" refers to an emg signal that has been rectified and low pass filtered.
-visual3d has a number of helpful pipeline functions (linked below) that can automate the general processing steps.
+. High Pass Filter
+. Low Pass Filter
+. Rectify Data
+. Filter Noise
+. Normalize and Scale Data
+It should be noted that within both this page and external literature, the term "Linear Envelope" refers to an EMG signal that has been rectified and low pass filtered.
-===== helpful pipeline functions =====
+Visual3D has a number of helpful pipeline functions (linked below) that can automate the general processing steps.
-the following links will redirect you to pages detailing the use of visual3d pipeline commands that are commonly used in the general processing of emg data:
+==== Helpful Pipeline Functions ====
-  * [[visual3d:documentation:emg:processing:detecting_muscle_onset|high pass filter (removing dc bias)]]
+The following links will redirect you to pages detailing the use of Visual3D pipeline commands that are commonly used in the general processing of EMG data:
-  * [[visual3d:documentation:pipeline:signal_commands:lowpass_filter|lowpass filter]]
-  * [[visual3d:documentation:pipeline:signal_commands:rectify|rectify]]
-  * [[visual3d:documentation:pipeline:signal_commands:moving_rms|moving rms]]
-  * [[visual3d:documentation:pipeline:signal_commands:teager_kaiser_energy|teager kaiser energy operator]]
-  * [[visual3d:documentation:pipeline:file_commands:assign_tags_to_file|assign tags to file]]
-===== meta commands =====
+  * [[Visual3D:Documentation:EMG:Processing:Detecting_Muscle_Onset|High Pass Filter (Removing DC Bias)]]
+  * [[Visual3D:Documentation:Pipeline:Signal_Commands:Lowpass_Filter|Lowpass Filter]]
+  * [[Visual3D:Documentation:Pipeline:Signal_Commands:Rectify|Rectify]]
+  * [[Visual3D:Documentation:Pipeline:Signal_Commands:Moving_RMS|Moving RMS]]
+  * [[Visual3D:Documentation:Pipeline:Signal_Commands:Teager_Kaiser_Energy|Teager Kaiser Energy Operator]]
+  * [[Visual3D:Documentation:Pipeline:File_Commands:Assign_Tags_To_File|Assign Tags To File]]
-this page deals with several examples of using visual3d [[visual3d:documentation:pipeline:meta_commands:meta_commands_overview|meta-commands]]. meta commands are essentially a way for you to write and upload your own function to the visual3d pipeline. they have the file extension **".v3m"**. meta commands must be stored in a folder labelled **meta-commands**, which should be located in the visual3d **plugins** folder. the plugins folder may not exist, so you may have to create it yourself. if you receive errors after running a meta-command, navigate to **edit > preferences** in visual3d and check that the directory of the plugins folder matches the location visual3d is looking for it in. restart visual3d before running the command again.
+==== Meta Commands ====
-===== removing noise from emg signals =====
+This page deals with several examples of using Visual3D [[Visual3D:Documentation:Pipeline:Meta_Commands:Meta_Commands_Overview|Meta-Commands]]. Meta commands are essentially a way for you to write and upload your own function to the Visual3D pipeline. They have the file extension **".v3m"**. Meta commands must be stored in a folder labelled **Meta-Commands**, which should be located in the Visual3D **Plugins** folder. The Plugins folder may not exist, so you may have to create it yourself. If you receive errors after running a meta-command, navigate to **Edit > Preferences** in Visual3D and check that the directory of the Plugins folder matches the location Visual3D is looking for it in. Restart Visual3D before running the command again.
-**download the [[https://www.has-motion.com/download/examples/emg/emg_noisereduction_example.zip|emg_noisereductionexample]] here.**
+==== Removing Noise from EMG Signals ====
-the text below describes two common methods of removing noise from emg signals. before using these methods, ensure you have performed a high and low pass filter on the raw data. you do not need to rectify your data to use the root mean square method or the teagan kaiser energy operator method as they will both rectify your signals for you.
+**Download the [[https://www.has-motion.com/download/examples/EMG/EMG_NoiseReduction_Example.zip|EMG_NoiseReductionExample]] here.**
-**1. root mean square (rms):** the rms method is typically used when finding overall energy, muscle activation patterns, or for fatigue analysis. the rms method takes the square root of the mean square of a set of values. because it deals with the mean square of a data set, the input emg signal does not need to be rectified before calculating the rms. example application of this command shown below:
+The text below describes two common methods of removing noise from EMG signals. Before using these methods, ensure you have performed a high and low pass filter on the raw data. You do not need to rectify your data to use the Root Mean Square method or the Teagan Kaiser Energy Operator method as they will both rectify your signals for you.
+**1. Root Mean Square (RMS):** The RMS method is typically used when finding overall energy, muscle activation patterns, or for fatigue analysis. The RMS method takes the square root of the mean square of a set of values. Because it deals with the mean square of a data set, the input EMG signal does not need to be rectified before calculating the RMS. Example application of this command shown below:
 <code>
-! example 1: use the moving rms command to process emg data
+! Example 1: Use the Moving RMS Command to Process EMG Data
-! apply a high pass filter with 50 hz cutoff
+! Apply a high pass filter with 50 Hz cutoff
-highpass_filter
+Highpass_Filter
-/signal_types=analog
+/Signal_Types=ANALOG
-/signal_names=emg1+emg2+emg3
+/Signal_Names=EMG1+EMG2+EMG3
-/signal_folder=original
+/Signal_Folder=ORIGINAL
-! /result_suffix=
+! /Result_Suffix=
-! /result_folder=processed
+! /Result_Folder=PROCESSED
-! /filter_class=butterworth
+! /Filter_Class=BUTTERWORTH
-/frequency_cutoff= 50
+/Frequency_Cutoff= 50
-/num_reflected= 0
+/Num_Reflected= 0
-/total_buffer_size=100
+/Total_Buffer_Size=100
-/num_bidirectional_passes=1
+/Num_Bidirectional_Passes=1
 ;
-! apply a low pass filter with 500 hz cutoff
+! Apply a low pass filter with 500 Hz cutoff
-lowpass_filter
+Lowpass_Filter
-/signal_types=analog
+/Signal_Types=ANALOG
-/signal_names=emg1+emg2+emg3
+/Signal_Names=EMG1+EMG2+EMG3
-/signal_folder=processed
+/Signal_Folder=PROCESSED
-! /result_suffix=
+! /Result_Suffix=
-! /result_folder=processed
+! /Result_Folder=PROCESSED
-! /filter_class=butterworth
+! /Filter_Class=BUTTERWORTH
-/frequency_cutoff= 500
+/Frequency_Cutoff= 500
-/num_reflected= 0
+/Num_Reflected= 0
-/total_buffer_size=100
+/Total_Buffer_Size=100
-/num_bidirectional_passes=1
+/Num_Bidirectional_Passes=1
 ;
-! moving rms with 100 millisecond window
+! Moving RMS with 100 millisecond window
-moving_rms
+Moving_RMS
-/signal_types=analog
+/SIGNAL_TYPES=ANALOG
-/signal_names=emg1+emg2+emg3
+/SIGNAL_NAMES=EMG1+EMG2+EMG3
-/signal_folder=processed
+/SIGNAL_FOLDER=PROCESSED
-! /result_suffix=
+! /RESULT_SUFFIX=
-/result_folder=rms
+/RESULT_FOLDER=RMS
-/num_window_frames= ( 0.1*parameter::analog::rate ) + 1
+/NUM_WINDOW_FRAMES= ( 0.1*PARAMETER::ANALOG::RATE ) + 1
 ;
 </code>
-**2. teager kaiser energy operator (tkeo):** the tkeo method is typically used when finding muscle onset/offset contracts and analyzing frequency data. the tkeo method is a signal processing technique used to extract information from a time-series signal. it involves calculating the teager energy of the signal, which is a measure of the signal's instantaneous power, and then smoothing the energy values using a kaiser window. the resulting smoothed energy values can be used to identify important features in the signal, such as peaks or changes in frequency. example application of this command shown below:
+**2. Teager Kaiser Energy Operator (TKEO):** The TKEO method is typically used when finding muscle onset/offset contracts and analyzing frequency data. The TKEO method is a signal processing technique used to extract information from a time-series signal. It involves calculating the Teager energy of the signal, which is a measure of the signal's instantaneous power, and then smoothing the energy values using a Kaiser window. The resulting smoothed energy values can be used to identify important features in the signal, such as peaks or changes in frequency. Example application of this command shown below:
 <code>
-! example 2: use the tkeo command to process emg data
+! Example 2: Use the TKEO Command to Process EMG Data
-highpass_filter
+Highpass_Filter
-/signal_types=analog
+/SIGNAL_TYPES=ANALOG
-/signal_folder=original
+/SIGNAL_FOLDER=ORIGINAL
-/signal_names=emg_c
+/SIGNAL_NAMES=EMG_C
-/result_folder=processed
+/RESULT_FOLDER=PROCESSED
-! /result_suffix=
+! /RESULT_SUFFIX=
-! /filter_class=butterworth
+! /FILTER_CLASS=BUTTERWORTH
-/frequency_cutoff=20
+/FREQUENCY_CUTOFF=20
-/num_reflected=0
+/NUM_REFLECTED=0
-! /num_extrapolated=0
+! /NUM_EXTRAPOLATED=0
-/total_buffer_size=100
+/TOTAL_BUFFER_SIZE=100
-! /num_bidirectional_passes=1
+! /NUM_BIDIRECTIONAL_PASSES=1
 ;
-lowpass_filter
+Lowpass_Filter
-/signal_types=analog
+/SIGNAL_TYPES=ANALOG
-/signal_folder=original
+/SIGNAL_FOLDER=ORIGINAL
-/signal_names=emg_c
+/SIGNAL_NAMES=EMG_C
-/result_folder=processed
+/RESULT_FOLDER=PROCESSED
-! /result_suffix=
+! /RESULT_SUFFIX=
-! /filter_class=butterworth
+! /FILTER_CLASS=BUTTERWORTH
-/frequency_cutoff=6.0
+/FREQUENCY_CUTOFF=6.0
-/num_reflected=6
+/NUM_REFLECTED=6
-! /num_extrapolated=0
+! /NUM_EXTRAPOLATED=0
-/total_buffer_size=6
+/TOTAL_BUFFER_SIZE=6
-! /num_bidirectional_passes=1
+! /NUM_BIDIRECTIONAL_PASSES=1
 ;
-teager_kaiser_energy
+Teager_Kaiser_Energy
-/signal_types=analog
+/SIGNAL_TYPES=ANALOG
-/signal_folder=original
+/SIGNAL_FOLDER=ORIGINAL
-/signal_names=emg_c
+/SIGNAL_NAMES=EMG_C
-! /result_types=
+! /RESULT_TYPES=
-/result_folders=processed
+/RESULT_FOLDERS=PROCESSED
-/result_name=emg_c_tkeo
+/RESULT_NAME=EMG_C_TKEO
-! /apply_as_suffix_to_signal_name=
+! /APPLY_AS_SUFFIX_TO_SIGNAL_NAME=
 ;
 </code>
-**3. integrating emg signals:** integrating emg signals can be useful for quantifying muscle activity, comparing muscle activity between conditions, and assessing fatigue. the result of integrating an emg signal (an iemg) is a single metric value of microvolts or millivolts. while this isn't strictly a noise reduction method, it does have applications once a signal has been filtered. an example of using visual3d's pipeline commands to integrate an emg signal can be found here: [[visual3d:documentation:emg:processing:normalize_emg_signal_to_maximum_within_gait_cycle|emg integrate]].
+**3. Integrating EMG Signals:** Integrating EMG signals can be useful for quantifying muscle activity, comparing muscle activity between conditions, and assessing fatigue. The result of integrating an EMG signal (an iEMG) is a single metric value of microvolts or millivolts. While this isn't strictly a noise reduction method, it does have applications once a signal has been filtered. An example of using Visual3D's pipeline commands to integrate an EMG signal can be found here: [[Visual3D:Documentation:EMG:Processing:Normalize_EMG_Signal_to_Maximum_Within_Gait_Cycle|EMG Integrate]].
-**4. removing background noise example:** the [[visual3d:documentation:emg:processing_tools|removing background noise]] page shows an example of using the visual3d pipeline and meta commands to implement a noise reduction algorithm. the algorithm finds the mean of the data, rectifies the data around a mean baseline, and calculates threshold values to store as a global variable.
+**4. Removing Background Noise Example:** The [[Visual3D:Documentation:EMG:Processing_Tools|Removing Background Noise]] page shows an example of using the Visual3D pipeline and Meta Commands to implement a noise reduction algorithm. The algorithm finds the mean of the data, rectifies the data around a mean baseline, and calculates threshold values to store as a global variable.
-===== normalization and scaling methods =====
+==== Normalization and Scaling Methods ====
+Normalizing data is a useful transformation for comparing signals across groups of data. This section discusses several methods of using Visual3D's pipeline features to normalize and scale EMG signals after they have been filtered.
-normalizing data is a useful transformation for comparing signals across groups of data. this section discusses several methods of using visual3d's pipeline features to normalize and scale emg signals after they have been filtered.
+**1. Normalize and Scale EMG Signal to Global Maximum:** One method of normalizing EMG signals is to use the maximum voluntary contraction (MVC) value. MVC values are an EMG signal measuring during a maximal effort task , which is then used as a reference value to normalize EMG signals during all subsequent experimental tasks. What this translates to in Visual3D is first calculating the maximum value of the reference signal and store it in the Global workspace, then normalize your signals by dividing them by this global metric. Sample files and pipelines are available [[Visual3D:Documentation:EMG:Filtering:EMG_Envelope_Version_3|here]] and [[Visual3D:Documentation:EMG:Processing:Normalize_EMG_to_Generic_Global_Variable|here]].
+**2. Compute Normalization Scale Factors:** Here are two examples of the steps that would be used to compute a normalization factor using MVC data.
+**Example 1: Single MVC Trial:** The process for computing a normalization factor from a single MVC value uses the following general steps:
+  - Process EMG
+    - High pass filter (remove DC offset)
+    - Calculate RMS of predetermined time intervals (example: 0.02 seconds)
+  - Normalize
+    - Calculate the average of the processed signal over 30 second intervals
+    - Get the maximum of the 30 second interval
+    - Normalize by dividing the average by the maximum
-**1. normalize and scale emg signal to global maximum:** one method of normalizing emg signals is to use the maximum voluntary contraction (mvc) value. mvc values are an emg signal measuring during a maximal effort task , which is then used as a reference value to normalize emg signals during all subsequent experimental tasks. what this translates to in visual3d is first calculating the maximum value of the reference signal and store it in the global workspace, then normalize your signals by dividing them by this global metric. sample files and pipelines are available [[visual3d:documentation:emg:filtering:emg_envelope_version_3|here]] and [[visual3d:documentation:emg:processing:normalize_emg_to_generic_global_variable|here]].
+**Example 2: Multiple MVC Trials**
-**2. compute normalization scale factors:** here are two examples of the steps that would be used to compute a normalization factor using mvc data.
+  - Process EMG
-**example 1: single mvc trial:** the process for computing a normalization factor from a single mvc value uses the following general steps:
+    - High pass filter (remove DC offset)
-  - process emg
+    - Calculate RMS of predetermined time intervals (example: 0.02 seconds)
-    - high pass filter (remove dc offset)
+  - Normalize
-    - calculate rms of predetermined time intervals (example: 0.02 seconds)
+    - Calculate the average of the processed signal over some time interval (in this example: 0.5 seconds)
-  - normalize
+    - Get the maximum of the processed signal
-    - calculate the average of the processed signal over 30 second intervals
+    - Calculate the maximum of the average signal
-    - get the maximum of the 30 second interval
+    - Normalize by dividing the processed signal by the maximum average over the interval
-    - normalize by dividing the average by the maximum
-**example 2: multiple mvc trials**
+Sample files and pipelines are available [[Visual3D:Documentation:EMG:Filtering:Removing_DC_Bias|here]].
-  - process emg
+|**3. Normalize to Maximum within Gait Cycle:** The image to the (right) shows four "checkpoints" in normalizing a signal to the maximum within a gait cycle.\\ \\ * First graph: raw EMG signal with gait events RHS (pink) and RTO (purple). These correspond to the signal within ANALOG::ORIGINAL in the Sample_Workspace.cmz download.\\ * Second graph: the linear envelope (ANALOG::ENVELOPE) showing the rectified and smoothed signal with maximums A (~0.76) and B (~0.69).\\ * Third graph: all frames within each gait cycle set to the maximum value, and all other frames are set to zero.\\ * Fourth graph: the linear envelope signal is divided by the maximum of the corresponding gait cycle. Notice how the peaks of both cycles are now 1, and all values outside the defined event sequence are set to "data not found".\\ \\ Sample files and pipelines are available [[Visual3D:Documentation:EMG:Processing:Normalize_EMG_to_MVC|here]].  |  {{:EMG_Normalized_Gait_Cycle.png}}|
-    - high pass filter (remove dc offset)
-    - calculate rms of predetermined time intervals (example: 0.02 seconds)
-  - normalize
-    - calculate the average of the processed signal over some time interval (in this example: 0.5 seconds)
-    - get the maximum of the processed signal
-    - calculate the maximum of the average signal
-    - normalize by dividing the processed signal by the maximum average over the interval
-sample files and pipelines are available [[visual3d:documentation:emg:filtering:removing_dc_bias|here]].
-|**3. normalize to maximum within gait cycle:** the image to the (right) shows four "checkpoints" in normalizing a signal to the maximum within a gait cycle.\\ \\ * first graph: raw emg signal with gait events rhs (pink) and rto (purple). these correspond to the signal within analog::original in the sample_workspace.cmz download.\\ * second graph: the linear envelope (analog::envelope) showing the rectified and smoothed signal with maximums a (~0.76) and b (~0.69).\\ * third graph: all frames within each gait cycle set to the maximum value, and all other frames are set to zero.\\ * fourth graph: the linear envelope signal is divided by the maximum of the corresponding gait cycle. notice how the peaks of both cycles are now 1, and all values outside the defined event sequence are set to "data not found".\\ \\ sample files and pipelines are available [[visual3d:documentation:emg:processing:normalize_emg_to_mvc|here]].  |  emg_normalized_gait_cycle.png|
-}}