HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » tutorials » emg » Automatic EMG Events
visual3d:tutorials:emg:automatic_emg_events

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
visual3d:tutorials:emg:automatic_emg_events [2024/06/19 12:54] – sgrangervisual3d:tutorials:emg:automatic_emg_events [2024/10/09 14:42] (current) – Fixed external links. wikisysop
Line 1: Line 1:
-{{{{{{{{\\+====== Automatic EMG Events ======
  
 +\\
  
-===== overview ===== 
  
-processing motion files with multiple emg signals can become tedious when manually extracting events and identifying points of “rest”. we can manually detect sections of minimal activity within a motion trial to set as a reference threshold. using the data download from [[visual3d:tutorials:emg:typical_emg_processing|tutorial emg]], we can look at automatically detecting periods of low muscle activity to help us auto populate emg onset/offset detection.+==== Overview ====
  
-in this tutorial we will:+Processing motion files with multiple EMG signals can become tedious when manually extracting events and identifying points of “rest”. We can manually detect sections of minimal activity within a motion trial to set as a reference threshold. Using the data download from [[Visual3D:Tutorials:EMG:Typical_EMG_Processing|Tutorial EMG]], we can look at automatically detecting periods of low muscle activity to help us auto populate EMG onset/offset detection.
  
-  - load emg data into visual 3d +In this tutorial we will:
-  - perform a series of signal filtering commands including: +
-    - bandpass filter +
-    - full-wave rectify +
-    - moving root mean squared (rms) +
-    - teager-kaiser energy operator (tkeo) +
-  - automatically detect low muscle activity +
-  - generate tkeo threshold to perform onset offset detection +
-  - visualize the event detection and demonstrate the effects of changing the meta parameters+
  
-===== preparing for the tutorial =====+  - Load EMG data into Visual 3D 
 +  - Perform a series of signal filtering commands including: 
 +    - Bandpass filter 
 +    - Full-wave rectify 
 +    - Moving Root Mean Squared (RMS) 
 +    - Teager-Kaiser Energy Operator (TKEO) 
 +  - Automatically detect low muscle activity 
 +  - Generate TKEO threshold to perform Onset Offset detection 
 +  - Visualize the event detection and demonstrate the effects of changing the meta parameters
  
-**tutorial data download**: files used in this tutorial can be found here: [[[https://www.has-motion.com/download/examples/emg_tutorial.zip|emg tutorial]]]+==== Preparing for the Tutorial ====
  
-the following pipeline has been provided as a **meta_function**, and you may copy and paste it into your **visual3d x64 > plugins > meta-commands** folder. for more information on meta-commands and how they work, follow see [[visual3d:documentation:pipeline:meta_commands:meta_commands_overview|here]].+**Tutorial data download**: Files used in this tutorial can be found here: [[https://www.has-motion.com/download/examples/EMG_Tutorial.zip|EMG Tutorial]]
  
-**meta-commands download**: meta-command file found here: [[[https://www.has-motion.com/download/examples/emg/automatic_emg_events.v3m|automatic_emg_events]]]+The following pipeline has been provided as a **meta_function**, and you may copy and paste it into your **Visual3D x64 > Plugins > Meta-Commands** folder. For more information on Meta-Commands and how they work, follow see [[Visual3D:Documentation:Pipeline:Meta_Commands:Meta_Commands_Overview|here]].
  
-===== loading data and calling the meta-function =====+**Meta-Commands download**: Meta-Command file found here: [[https://www.has-motion.com/download/examples/EMG/Automatic_EMG_Events.v3m|Automatic_EMG_Events]]
  
-open the **trial_1.c3d** file from the tutorial download into visual3d.+==== Loading Data and Calling the Meta-Function ====
  
-to begin the automatic detection, we first need to follow the typical processing procedure for emg signals, going through all signals individually. we will work through the pipeline of **automatic_emg_events**. you may look through the meta-command file along with this description, or use this pipeline to help build your own.+Open the **trial_1.c3d** file from the Tutorial download into Visual3D.
  
-to call the meta-command in the pipeline, use the following:+To begin the automatic detection, we first need to follow the typical processing procedure for EMG signals, going through all signals individually. We will work through the pipeline of **Automatic_EMG_Events**. You may look through the meta-command file along with this description, or use this pipeline to help build your own. 
 + 
 +To call the meta-command in the pipeline, use the following:
  
 <code> <code>
-automatic_emg_events +Automatic_EMG_Events 
-/signal_names=emg_a+emg_b+emg_c +/SIGNAL_NAMES=EMG_A+EMG_B+EMG_C 
-/thresholdpercent=0.2+/ThresholdPercent=0.2
 ; ;
 </code> </code>
  
-we can go through the meta-command pipeline itself to see what is being done. we begin by initializing the pipeline as a meta-command. this command will take two parameters, **signals_names** and **thresholdpercent**. the signal names are associated with your emgs and associated .c3d files. the threshold percent determines what percent of the maximum signal voltage you want to consider as noise or low muscle activity.+We can go through the meta-command pipeline itself to see what is being done. We begin by initializing the pipeline as a meta-command. This command will take two parameters, **Signals_Names** and **ThresholdPercent**. The signal names are associated with your EMGs and associated .c3d files. The threshold percent determines what percent of the maximum signal voltage you want to consider as noise or low muscle activity.
  
 <code> <code>
-! begin_meta +! BEGIN_META 
-! meta_cmd_name=automatic_emg_events +! META_CMD_NAME=Automatic_EMG_Events 
-! meta_param= signal_names:string::yes +! META_PARAM= SIGNAL_NAMES:string::yes 
-! meta_param= thresholdpercent:string::no +! META_PARAM= ThresholdPercent:string::no 
-! meta_highpass=  +! META_HIGHPASS=  
-! meta_lowpass=  +! META_LOWPASS=  
-! end_meta+! END_META
 </code> </code>
  
-===== processing and filtering raw emg signals =====+==== Processing and Filtering Raw EMG Signals ====
  
-this meta command can be used to process emg data in two ways; first, through the **moving rms** filtering to remove noise from the analog signal while maintaining overall power, amplitude and energy, muscle activation patterns, and fatigue properties [**1**]. second, **tkeo** will be used on the raw signals to perform a more rigorous filtration that will allow for onset/offset contraction detection. the **tkeo** will reduce power and amplitude but is more accurate when finding exact timing of events [**2**].+This meta command can be used to process EMG data in two ways; First, through the **moving RMS** filtering to remove noise from the analog signal while maintaining overall power, amplitude and energy, muscle activation patterns, and fatigue properties [**1**]. Second, **TKEO** will be used on the raw signals to perform a more rigorous filtration that will allow for onset/offset contraction detection. The **TKEO** will reduce power and amplitude but is more accurate when finding exact timing of events [**2**].
  
-we initialize a for loop to go through all emg signals in the open file.+We initialize a for loop to go through all EMG signals in the open file.
  
 <code> <code>
-for_each +For_Each 
-/iteration_parameter_name= signal +/Iteration_Parameter_Name= SIGNAL 
-/items= ::signal_names+/Items= ::SIGNAL_NAMES
 ; ;
 </code> </code>
  
-now we will look at filtering only at emg data, if you wish to find grfs or **model_based_data**, run a different pipeline before or after this one. first, a **bandpass filter** (high and lowpass) will be performed on raw analog signals. the **highpass filter** removes high frequency noise, the cutoff may need to be adjusted to suit your raw signals and how much noise there is. that is the **thresholdpercent** parameter, and is expressed as a decimal.+Now we will look at filtering only at EMG data, if you wish to find GRFs or **model_based_data**, run a different pipeline before or after this one. First, a **bandpass filter** (high and lowpass) will be performed on raw analog signals. The **highpass filter** removes high frequency noise, the cutoff may need to be adjusted to suit your raw signals and how much noise there is. That is the **ThresholdPercent** parameter, and is expressed as a decimal.
  
-in the **analog** folder, several sub-folders will be generated in this section of the pipeline, as we go through the different filtering methods.+In the **ANALOG** folder, several sub-folders will be generated in this section of the pipeline, as we go through the different filtering methods.
  
-the **processed** data folder is going to contain the data that has gone through a highpass and lowpass filter.+The **PROCESSED** data folder is going to contain the data that has gone through a highpass and lowpass filter.
  
-the **envelope** data folder will contain filtered data in order of highpass, rectify, lowpass - this will be used later to help us find a resting period of the signal, with the **thresholdpercent** parameter.+The **ENVELOPE** data folder will contain filtered data in order of highpass, rectify, lowpass - this will be used later to help us find a resting period of the signal, with the **ThresholdPercent** parameter.
  
-the **processed_rms** data folder will take the **processed** data and perform moving rms.+The **PROCESSED_RMS** data folder will take the **PROCESSED** data and perform moving RMS.
  
-the **processed_tkeo** data folder will take the **processed** data and perform tkeo.+The **PROCESSED_TKEO** data folder will take the **PROCESSED** data and perform TKEO.
  
 <code> <code>
-! highpass filter removes large frquency noise from signal +! Highpass filter removes large frquency noise from signal 
-highpass_filter +Highpass_Filter 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_folder=original +/SIGNAL_FOLDER=ORIGINAL 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/result_folder=processed +/RESULT_FOLDER=PROCESSED 
-! /result_suffix= +! /RESULT_SUFFIX= 
-! /filter_class=butterworth +! /FILTER_CLASS=BUTTERWORTH 
-/frequency_cutoff=50 +/FREQUENCY_CUTOFF=50 
- /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
 ; ;
 </code> </code>
  
 <code> <code>
-! rectify and lowpass for envelop development (difference freq cutoff in lowpass filter) +! Rectify and Lowpass for envelop development (difference freq cutoff in lowpass filter) 
-rectify +Rectify 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/signal_folder=processed  +/SIGNAL_FOLDER=PROCESSED  
-! /result_names= +! /RESULT_NAMES= 
-! /result_types= +! /RESULT_TYPES= 
-/result_folder=rectify  +/RESULT_FOLDER=RECTIFY  
-! /result_suffix=+! /RESULT_SUFFIX=
 ; ;
 </code> </code>
  
 <code> <code>
-lowpass_filter +Lowpass_Filter 
- /signal_types=analog + /SIGNAL_TYPES=ANALOG 
-/signal_folder=rectify +/SIGNAL_FOLDER=RECTIFY 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/result_folder=envelope +/RESULT_FOLDER=ENVELOPE 
-! /result_suffix= +! /RESULT_SUFFIX= 
-! /filter_class=butterworth +! /FILTER_CLASS=BUTTERWORTH 
-/frequency_cutoff=10 +/FREQUENCY_CUTOFF=10 
-/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
 ; ;
 </code> </code>
  
-next, lowpass filter will be applied to the original processed data for bandpass filtering. the lowpass filter removes any baseline drift, and again may need to be adjusted for your data. for more details on these filtering functions, see [[visual3d:documentation:emg:processing:onset_based_on_tko|emg processing tools]].+Next, Lowpass filter will be applied to the original processed data for bandpass filtering. The lowpass filter removes any baseline drift, and again may need to be adjusted for your data. For more details on these filtering functions, see [[Visual3D:Documentation:EMG:Processing:Onset_Based_on_TKO|EMG Processing Tools]].
  
 <code> <code>
-lowpass_filter +Lowpass_Filter 
- /signal_types=analog + /SIGNAL_TYPES=ANALOG 
-/signal_folder=processed +/SIGNAL_FOLDER=PROCESSED 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/result_folder=processed +/RESULT_FOLDER=PROCESSED 
-! /result_suffix= +! /RESULT_SUFFIX= 
-! /filter_class=butterworth +! /FILTER_CLASS=BUTTERWORTH 
-/frequency_cutoff=80 +/FREQUENCY_CUTOFF=80 
-/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
 ; ;
 </code> </code>
  
 <code> <code>
-! rms filtering: putting results in a new processed_rms folder to identify which +! RMS Filtering: Putting results in a new PROCESSED_RMS folder to identify which 
-! filtering process was used. using the processed data from the bandpass filter +! filtering process was used. Using the PROCESSED data from the bandpass filter 
-! to perform rms on. +! to perform RMS on. 
-moving_rms +Moving_RMS 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_folder=processed +/SIGNAL_FOLDER=PROCESSED 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-! /result_types= +! /RESULT_TYPES= 
-/result_folders=processed_rms +/RESULT_FOLDERS=PROCESSED_RMS 
-! /result_name= +! /RESULT_NAME= 
-! /apply_as_suffix_to_signal_name= +! /APPLY_AS_SUFFIX_TO_SIGNAL_NAME= 
-! /num_window_frames=3 +! /NUM_WINDOW_FRAMES=3 
-! /if_even_frames_increment_1=false+! /IF_EVEN_FRAMES_INCREMENT_1=FALSE
 ; ;
 </code> </code>
  
 <code> <code>
-! tkeo filtering: putting results in a new processed_tkeo folder to identify which +! TKEO Filtering: Putting results in a new PROCESSED_TKEO folder to identify which 
-! filtering process was used. using the processed data from the bandpass filter +! filtering process was used. Using the PROCESSED data from the bandpass filter 
-! to perform rms on. +! to perform RMS on. 
-teager_kaiser_energy +Teager_Kaiser_Energy 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_folder=processed +/SIGNAL_FOLDER=PROCESSED 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-!/signal_components= +!/SIGNAL_COMPONENTS= 
- /result_folder=processed_tkeo + /RESULT_FOLDER=PROCESSED_TKEO 
-! /event_sequence= +! /EVENT_SEQUENCE= 
-! /exclude_events=+! /EXCLUDE_EVENTS=
 ; ;
 </code> </code>
  
-===== detecting low activity signal regions =====+==== Detecting Low Activity Signal Regions ====
  
-envelope.png+{{:ENVELOPE.png}}
  
-this section will essentially perform on/off detection of the **envelope** signal with an arbitrary baseline that we define with a user-given parameter.+This section will essentially perform on/off detection of the **ENVELOPE** signal with an arbitrary baseline that we define with a user-given parameter.
  
-event detection using analog signal envelop method: creates events that define the resting baseline of the muscle. we will find the resting period based on an arbitrary value that the user can change. for this example, we use 20% of the maximum signal of the **envelope** (which is a highly smoothed signal). after we find the rest period, we compute the median and standard deviation to find an appropriate baseline for on/off detection of muscle activation that can be used on **tkeo** signals.+Event detection using Analog signal envelop method: Creates events that define the resting baseline of the muscle. We will find the resting period based on an arbitrary value that the user can change. For this example, we use 20% of the maximum signal of the **ENVELOPE** (which is a highly smoothed signal). After we find the rest period, we compute the median and standard deviation to find an appropriate baseline for ON/OFF detection of muscle activation that can be used on **TKEO** signals.
  
-when we run this pipeline section, you can open your **envelope** analog signals and highlight the **ascent** and **descent** events that are associated with each signal. here, you can determine if the **thresholdpercent** parameter is at an appropriate level for your signals. increasing the **thresholdpercent** will consider more of the signal to be “rest”, or noise, and lowering the **thresholdpercent** will decrease the noise that you include in your “resting” data.+When we run this pipeline section, you can open your **ENVELOPE** analog signals and highlight the **ASCENT** and **DESCENT** events that are associated with each signal. Here, you can determine if the **ThresholdPercent** parameter is at an appropriate level for your signals. Increasing the **ThresholdPercent** will consider more of the signal to be “rest”, or noise, and lowering the **ThresholdPercent** will decrease the noise that you include in your “resting” data.
  
-find maximum for each signal+Find Maximum for each signal
  
 <code> <code>
-metric_maximum +Metric_Maximum 
-/result_metric_folder=processed +/RESULT_METRIC_FOLDER=PROCESSED 
-/result_metric_name=::signal&max +/RESULT_METRIC_NAME=::SIGNAL&MAX 
-/apply_as_suffix_to_signal_name=false +/APPLY_AS_SUFFIX_TO_SIGNAL_NAME=FALSE 
-/signal_types= analog +/SIGNAL_TYPES= ANALOG 
-/signal_folder=envelope +/SIGNAL_FOLDER=ENVELOPE 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-! /component_sequence= +! /COMPONENT_SEQUENCE= 
-!/event_sequence= +!/EVENT_SEQUENCE= 
-!/exclude_events= +!/EXCLUDE_EVENTS= 
-! /generate_mean_and_stddev=true +! /GENERATE_MEAN_AND_STDDEV=TRUE 
-! /append_to_existing_values=false +! /APPEND_TO_EXISTING_VALUES=FALSE 
-! /create_global_maximum=false +! /CREATE_GLOBAL_MAXIMUM=FALSE 
-! /create_trial_maximum=false+! /CREATE_TRIAL_MAXIMUM=FALSE
 ; ;
 </code> </code>
  
-find events when signal crosses threshold that is some specified % of metric max, to find "activation" and "rest"+Find Events when signal crosses threshold that is some specified % of metric max, to find "activation" and "rest"
  
 <code> <code>
-! set threshold +! Set threshold 
-set_pipeline_parameter_from_expression +Set_Pipeline_Parameter_From_Expression 
-/parameter_name= thresh +/PARAMETER_NAME= THRESH 
-/expression=(metric::processed::&::signal&max)*&::thresholdpercent +/EXPRESSION=(METRIC::PROCESSED::&::SIGNAL&MAX)*&::ThresholdPercent 
-/as_integer=false+/AS_INTEGER=FALSE
 ; ;
-! find when signal "ascents" above threshold +! Find when signal "ascents" above threshold 
-metric_time_of_threshold_from_event +Metric_Time_Of_Threshold_From_Event 
-/result_event_name=::signal&ascent +/RESULT_EVENT_NAME=::SIGNAL&ASCENT 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/signal_folder=envelope +/SIGNAL_FOLDER=ENVELOPE 
-/signal_components=x +/SIGNAL_COMPONENTS=X 
-! /frame_offset=0 +! /FRAME_OFFSET=0 
-! /time_offset= +! /TIME_OFFSET= 
-! /event_sequence= +! /EVENT_SEQUENCE= 
-! /exclude_events= +! /EXCLUDE_EVENTS= 
-!/event_sequence_instance=0 +!/EVENT_SEQUENCE_INSTANCE=0 
-! /event_subsequence= +! /EVENT_SUBSEQUENCE= 
-! /subsequence_exclude_events= +! /SUBSEQUENCE_EXCLUDE_EVENTS= 
-! /event_subsequence_instance=0 +! /EVENT_SUBSEQUENCE_INSTANCE=0 
-/event_instance=0 +/EVENT_INSTANCE=0 
-/select_x=true +/SELECT_X=TRUE 
-! /select_y= +! /SELECT_Y= 
-! /select_z= +! /SELECT_Z= 
-! /select_residual= +! /SELECT_RESIDUAL= 
-! /start_at_event= +! /START_AT_EVENT= 
-! /end_at_event= +! /END_AT_EVENT= 
-/threshold=::thresh +/THRESHOLD=::THRESH 
-/on_ascent=true +/ON_ASCENT=TRUE 
-!/on_descent= +!/ON_DESCENT= 
-! /frame_window=8 +! /FRAME_WINDOW=8 
-! /ensure_frames_before= +! /ENSURE_FRAMES_BEFORE= 
-! /ensure_frames_after=+! /ENSURE_FRAMES_AFTER=
 ; ;
-! find when signal "descents" below threshold +! Find when signal "descents" below threshold 
-metric_time_of_threshold_from_event +Metric_Time_Of_Threshold_From_Event 
-/result_event_name=::signal&descent +/RESULT_EVENT_NAME=::SIGNAL&DESCENT 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/signal_folder=envelope +/SIGNAL_FOLDER=ENVELOPE 
-/signal_components=x +/SIGNAL_COMPONENTS=X 
-! /frame_offset=0 +! /FRAME_OFFSET=0 
-! /time_offset= +! /TIME_OFFSET= 
-! /event_sequence= +! /EVENT_SEQUENCE= 
-! /exclude_events= +! /EXCLUDE_EVENTS= 
-!/event_sequence_instance=0 +!/EVENT_SEQUENCE_INSTANCE=0 
-! /event_subsequence= +! /EVENT_SUBSEQUENCE= 
-! /subsequence_exclude_events= +! /SUBSEQUENCE_EXCLUDE_EVENTS= 
-! /event_subsequence_instance=0 +! /EVENT_SUBSEQUENCE_INSTANCE=0 
-/event_instance=0 +/EVENT_INSTANCE=0 
-/select_x=true +/SELECT_X=TRUE 
-! /select_y= +! /SELECT_Y= 
-! /select_z= +! /SELECT_Z= 
-! /select_residual= +! /SELECT_RESIDUAL= 
-! /start_at_event= +! /START_AT_EVENT= 
-! /end_at_event= +! /END_AT_EVENT= 
-/threshold=::thresh +/THRESHOLD=::THRESH 
-/on_ascent=false +/ON_ASCENT=FALSE 
-/on_descent=true +/ON_DESCENT=TRUE 
-! /frame_window=8 +! /FRAME_WINDOW=8 
-! /ensure_frames_before= +! /ENSURE_FRAMES_BEFORE= 
-! /ensure_frames_after=+! /ENSURE_FRAMES_AFTER=
 ; ;
 </code> </code>
  
-now define events at the times of "ascent" and "descent". a period of time between descent to ascent should be an area of low activity and just noise.+Now define events at the times of "ascent" and "descent". A period of time between descent to ascent should be an area of low activity and just noise.
  
 <code> <code>
-event_explicit +Event_Explicit 
-/event_name=::signal&ascent +/EVENT_NAME=::SIGNAL&ASCENT 
-!/frame=1 +!/FRAME=1 
-/time=metric::processed::&::signal&ascent+/TIME=METRIC::PROCESSED::&::SIGNAL&ASCENT
 ; ;
-event_explicit +Event_Explicit 
-/event_name=::signal&descent +/EVENT_NAME=::SIGNAL&DESCENT 
-!/frame=150 +!/FRAME=150 
-/time=metric::processed::&::signal&descent+/TIME=METRIC::PROCESSED::&::SIGNAL&DESCENT
 ; ;
 </code> </code>
  
-===== onset/offset detection =====+==== Onset/Offset Detection ====
  
-now that we have **ascent** and **descent** events of our emg envelopes, we can consider low activity or “rest” periods to be between descent - ascent events. the reason we cannot officially define these events as **onset** or **offset** of the muscle, is because it is more correct to use the **tkeo** signal with a threshold of **median + 3*stdv** of the “resting” signal. so now we have identified the resting periods of each signal and can find our official **onset** and **offset** thresholds.+Now that we have **ASCENT** and **DESCENT** events of our EMG envelopes, we can consider low activity or “rest” periods to be between descent - ascent events. The reason we cannot officially define these events as **onset** or **offset** of the muscle, is because it is more correct to use the **TKEO** signal with a threshold of **median + 3*stdv** of the “resting” signal. So now we have identified the resting periods of each signal and can find our official **onset** and **offset** thresholds.
  
-here we compute the median and standard deviation of the **tkeo** envelope during defined "rest". we have the events to define a period of rest, and we can define these times for the **tkeo** signal. tkeo is used to define **on/off** for muscle activity by identify that the signal is on based on a threshold crossing of the **median + 3 * standard deviation** (from tkeo filtered data specifically. for more detail, [[visual3d:documentation:emg:processing:onset|emg onset based on tko]] or reference **[3]**).+Here we compute the median and standard deviation of the **TKEO** envelope during defined "rest". We have the events to define a period of rest, and we can define these times for the **TKEO** signal. TKEO is used to define **ON/OFF** for muscle activity by identify that the signal is on based on a threshold crossing of the **median + 3 * standard deviation** (from TKEO filtered data specifically. For more detail, [[Visual3D:Documentation:EMG:Processing:Onset|EMG Onset Based on TKO]] or reference **[3]**).
  
 <code> <code>
-metric_median +Metric_Median 
-/result_metric_name=_med +/RESULT_METRIC_NAME=_MED 
-/apply_as_suffix_to_signal_name=true +/APPLY_AS_SUFFIX_TO_SIGNAL_NAME=TRUE 
-/result_metric_folder=emg_tkeo +/RESULT_METRIC_FOLDER=EMG_TKEO 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/signal_folder=processed_tkeo +/SIGNAL_FOLDER=PROCESSED_TKEO 
-! /signal_components=all_components +! /SIGNAL_COMPONENTS=ALL_COMPONENTS 
-/event_sequence=::signal&descent+::signal&ascent +/EVENT_SEQUENCE=::SIGNAL&DESCENT+::SIGNAL&ASCENT 
-/exclude_events= +/EXCLUDE_EVENTS= 
-/generate_mean_and_stddev=true +/GENERATE_MEAN_AND_STDDEV=TRUE 
-! /append_to_existing_values=false+! /APPEND_TO_EXISTING_VALUES=FALSE
 ; ;
-metric_stddev +Metric_StdDev 
-/result_metric_name=_sd +/RESULT_METRIC_NAME=_SD 
-/apply_as_suffix_to_signal_name=true +/APPLY_AS_SUFFIX_TO_SIGNAL_NAME=TRUE 
-/result_metric_folder=emg_tkeo +/RESULT_METRIC_FOLDER=EMG_TKEO 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/signal_folder=processed_tkeo +/SIGNAL_FOLDER=PROCESSED_TKEO 
-! /signal_components=all_components +! /SIGNAL_COMPONENTS=ALL_COMPONENTS 
-/event_sequence=::signal&descent+::signal&ascent +/EVENT_SEQUENCE=::SIGNAL&DESCENT+::SIGNAL&ASCENT 
-/exclude_events= +/EXCLUDE_EVENTS= 
-/generate_mean_and_stddev=true +/GENERATE_MEAN_AND_STDDEV=TRUE 
-! /append_to_existing_values=false+! /APPEND_TO_EXISTING_VALUES=FALSE
 ; ;
 </code> </code>
  
-identify the event emg_c_on based on a threshold crossing+Identify the event EMG_C_ON based on a threshold crossing
  
 <code> <code>
 !of the median + 3 * standard deviation !of the median + 3 * standard deviation
-set_pipeline_parameter_from_expression +Set_Pipeline_Parameter_From_Expression 
-/parameter_name= thresh2 +/PARAMETER_NAME= THRESH2 
-/expression=(metric::emg_tkeo::&::signal&_med_mean)+3*(metric::emg_tkeo::&::signal&_sd_mean) +/EXPRESSION=(METRIC::EMG_TKEO::&::SIGNAL&_MED_MEAN)+3*(METRIC::EMG_TKEO::&::SIGNAL&_SD_MEAN) 
-/as_integer=false+/AS_INTEGER=FALSE
 ; ;
-! create threshold line vector for plotting purposes +! Create threshold line vector for plotting purposes 
-create_target +Create_Target 
-/signal_names=::signal&_threshold +/SIGNAL_NAMES=::SIGNAL&_Threshold 
-! /signal_description= +! /SIGNAL_DESCRIPTION= 
-/expression=vector(&::thresh2&,0,0) +/EXPRESSION=VECTOR(&::THRESH2&,0,0) 
-! /include_motionfile=true +! /INCLUDE_MOTIONFILE=TRUE 
-! /include_calfile=false+! /INCLUDE_CALFILE=FALSE
 ; ;
 </code> </code>
  
-defining signal off based on descending through the new threshold+Defining signal OFF based on descending through the new threshold
  
 <code> <code>
-metric_time_of_threshold_from_event +Metric_Time_Of_Threshold_From_Event 
-/result_event_name=::signal&off +/RESULT_EVENT_NAME=::SIGNAL&OFF 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/signal_folder=processed_tkeo +/SIGNAL_FOLDER=PROCESSED_TKEO 
-/signal_components=x +/SIGNAL_COMPONENTS=X 
-! /frame_offset=0 +! /FRAME_OFFSET=0 
-! /time_offset= +! /TIME_OFFSET= 
-! /event_sequence= +! /EVENT_SEQUENCE= 
-! /exclude_events= +! /EXCLUDE_EVENTS= 
-!/event_sequence_instance=0 +!/EVENT_SEQUENCE_INSTANCE=0 
-! /event_subsequence= +! /EVENT_SUBSEQUENCE= 
-! /subsequence_exclude_events= +! /SUBSEQUENCE_EXCLUDE_EVENTS= 
-! /event_subsequence_instance=0 +! /EVENT_SUBSEQUENCE_INSTANCE=0 
-/event_instance=0 +/EVENT_INSTANCE=0 
-/select_x=true +/SELECT_X=TRUE 
-! /select_y= +! /SELECT_Y= 
-! /select_z= +! /SELECT_Z= 
-! /select_residual= +! /SELECT_RESIDUAL= 
-! /start_at_event= +! /START_AT_EVENT= 
-! /end_at_event= +! /END_AT_EVENT= 
-/threshold=::thresh2 +/THRESHOLD=::THRESH2 
-/on_ascent=false +/ON_ASCENT=FALSE 
-/on_descent=true +/ON_DESCENT=TRUE 
-! /frame_window=8 +! /FRAME_WINDOW=8 
-! /ensure_frames_before= +! /ENSURE_FRAMES_BEFORE= 
-! /ensure_frames_after=+! /ENSURE_FRAMES_AFTER=
 ; ;
 </code> </code>
  
-creating an event for the off detection+Creating an event for the OFF detection
  
 <code> <code>
-event_explicit +Event_Explicit 
-/event_name=::signal&off +/EVENT_NAME=::SIGNAL&OFF 
-!/frame=1 +!/FRAME=1 
-/time=metric::processed::&::signal&off+/TIME=METRIC::PROCESSED::&::SIGNAL&OFF
 ; ;
 </code> </code>
  
-defining signal on based on ascending through the new threshold+Defining signal ON based on ascending through the new threshold
  
 <code> <code>
-metric_time_of_threshold_from_event +Metric_Time_Of_Threshold_From_Event 
-/result_event_name=::signal&on +/RESULT_EVENT_NAME=::SIGNAL&ON 
-/signal_types=analog +/SIGNAL_TYPES=ANALOG 
-/signal_names=::signal +/SIGNAL_NAMES=::SIGNAL 
-/signal_folder=processed_tkeo +/SIGNAL_FOLDER=PROCESSED_TKEO 
-/signal_components=x +/SIGNAL_COMPONENTS=X 
-! /frame_offset=0 +! /FRAME_OFFSET=0 
-! /time_offset= +! /TIME_OFFSET= 
-! /event_sequence= +! /EVENT_SEQUENCE= 
-! /exclude_events= +! /EXCLUDE_EVENTS= 
-!/event_sequence_instance=0 +!/EVENT_SEQUENCE_INSTANCE=0 
-! /event_subsequence= +! /EVENT_SUBSEQUENCE= 
-! /subsequence_exclude_events= +! /SUBSEQUENCE_EXCLUDE_EVENTS= 
-! /event_subsequence_instance=0 +! /EVENT_SUBSEQUENCE_INSTANCE=0 
-/event_instance=0 +/EVENT_INSTANCE=0 
-/select_x=true +/SELECT_X=TRUE 
-! /select_y= +! /SELECT_Y= 
-! /select_z= +! /SELECT_Z= 
-! /select_residual= +! /SELECT_RESIDUAL= 
-! /start_at_event= +! /START_AT_EVENT= 
-! /end_at_event= +! /END_AT_EVENT= 
-/threshold=::thresh2 +/THRESHOLD=::THRESH2 
-/on_ascent=true +/ON_ASCENT=TRUE 
-/on_descent=false +/ON_DESCENT=FALSE 
-! /frame_window=8 +! /FRAME_WINDOW=8 
-! /ensure_frames_before= +! /ENSURE_FRAMES_BEFORE= 
-! /ensure_frames_after=+! /ENSURE_FRAMES_AFTER=
 ; ;
 </code> </code>
  
-creating an event for the on detection+Creating an event for the ON detection
  
 <code> <code>
-event_explicit +Event_Explicit 
-/event_name=::signal&on +/EVENT_NAME=::SIGNAL&ON 
-!/frame=1 +!/FRAME=1 
-/time=metric::processed::&::signal&on+/TIME=METRIC::PROCESSED::&::SIGNAL&ON
 ; ;
 </code> </code>
  
-===== visualizing event detection =====+==== Visualizing Event Detection ====
  
-there we go! we have automatically found onset and offset for all signals, and can look at these events in our data. before this, we end the for loop for the meta-function.+There we go! We have automatically found onset and offset for all signals, and can look at these events in our data. Before this, we end the for loop for the meta-function.
  
 <code> <code>
-end_for_each +End_For_Each 
-/iteration_parameter_name=signal+/Iteration_Parameter_Name=SIGNAL
 ; ;
 </code> </code>
  
-tkeo_new.png+{{:TKEO_NEW.png}} 
 + 
 +{{:ZOOMED.png}}
  
-zoomed.png+We can now take a look at our onset and offset detection.
  
-we can now take a look at our onset and offset detection.+Select a **TKEO** processed signal from the **ANALOG > PROCESSED_TKEO** folder and plot a new graph.
  
-select a **tkeo** processed signal from the **analog > processed_tkeo** folder and plot a new graph.+Under **EVENT_LABEL > ORIGINAL**, select the '**signalName'ON** and '**signalName'OFF** events for the signal plotted.
  
-under **event_label > original**, select the '**signalname'on** and '**signalname'off** events for the signal plotted.+You can see on the signal there are faint pink lines all across the signal, that do not all get highlighted when the events are selected. This is because event assignment happens at then file level, not at the signal level. So these events are being assigned to the entire motion file each time we define an event for one of the signals. This is why it is important that you highlight only the events associated with the signal you are looking at.
  
-you can see on the signal there are faint pink lines all across the signal, that do not all get highlighted when the events are selected. this is because event assignment happens at then file level, not at the signal level. so these events are being assigned to the entire motion file each time we define an event for one of the signals. this is why it is important that you highlight only the events associated with the signal you are looking at.+We can see from these figures that there are a lot of **ON** and **OFF** detections for the **TKEO** signal. This is due to a lot of fluctuation and noise in the signal, and the threshold is passed through many times where there is large muscle activity.
  
-we can see from these figures that there are a lot of **on** and **off** detections for the **tkeo** signal. this is due to a lot of fluctuation and noise in the signal, and the threshold is passed through many times where there is large muscle activity.+If you find the automatic detection is identify data fluctuation that is too low in amplitude for your liking, we can adjust the **ThresholdPercent** parameter to change this. For example, this meta-command was re-run on this data using **ThresholdPercent = 0.6**, and the following results were found. We can see that only muscle activity of high magnitude were noted as **ON/OFF** events. {{:THRESH60.png}}
  
-if you find the automatic detection is identify data fluctuation that is too low in amplitude for your liking, we can adjust the **thresholdpercent** parameter to change this. for example, this meta-command was re-run on this data using **thresholdpercent = 0.6**, and the following results were found. we can see that only muscle activity of high magnitude were noted as **on/off** events. thresh60.png+==== References ====
  
-===== references =====+1. [[https://www.sciencedirect.com/science/article/abs/pii/S0966636208000994|Amedeo Troiano, Francesco Naddeo, Erik Sosso, Gianfranco Camarota, Roberto Merletti, Luca Mesin, Assessment of force and fatigue in isometric contractions of the upper trapezius muscle by surface EMG signal and perceived exertion scale, Gait & Posture 2018]]
  
-1. [[https://www.sciencedirect.com/science/article/abs/pii/s0966636208000994|amedeo troiano, francesco naddeo, erik sosso, gianfranco camarota, roberto merletti, luca mesin, assessment of force and fatigue in isometric contractions of the upper trapezius muscle by surface emg signal and perceived exertion scale, gait & posture 2018]]+2. [[https://ieeexplore.ieee.org/abstract/document/7096455|José A. Biurrun Manresa, Carsten D. Mørch, and Ole K. Andersen, Teager-Kaiser Energy Operator Improves the Detection and Quantification of Nociceptive Withdrawal Reflexes From Surface Electromyography, IEEE]]
  
-2. [[https://ieeexplore.ieee.org/abstract/document/7096455|josé a. biurrun manresa, carsten d. mørch, and ole k. andersen, teager-kaiser energy operator improves the detection and quantification of nociceptive withdrawal reflexes from surface electromyography, ieee]]+3. Solnik S, DeVita P, Rider P, Long B, and Hortobágyi T (2008) Teager–Kaiser Operator improves the accuracy of EMG onset detection independent of signal-to-noise ratio, Acta Bioeng Biomech. 2008 ; 10(2): 65–68
  
-3. [solnik s, devita p, rider p, long b, and hortobágyi t (2008) teager–kaiser operator improves the accuracy of emg onset detection independent of signal-to-noise ratio, acta bioeng biomech. 2008 ; 10(2): 65–68] 
  
  
-}}}}}}}} 
visual3d/tutorials/emg/automatic_emg_events.1718801657.txt.gz · Last modified: 2024/06/19 12:54 by sgranger