With Empower 3, tailed peaks detected even when the Inhibit Integration event is configured in ApexTrack - WKB90838

SYMPTOMS

• Processed by the processing method with the following settings, the peak tails to about 5.3 min; want to add a drop line at 4.9 min
  - Integration Algorithm "ApexTrack"
  - Inhibit Integration event configured from 4.9 min
  

ENVIRONMENT

• Empower 3

CAUSE

In the case of ApexTrack, if the peak elution continues to the time when the Inhibit Integration event is input, that peak will not be subject to the Inhibit Integration event.

FIX or WORKAROUND

1. Processing methods that use ApexTrack as the Integration Algorithm do not have events that separate peaks by time.
   If you want to narrow the peak detection range with ApexTrack as it is, set the "Set Touchdown %" event within the peak detection time,
   and specify a value in the "Value" column that is larger than the "Touchdown %" of the current processing method. This enables you to narrow the peak detection range.
   * Unlike the “Inhibit Integration” event, the End Time cannot be specified, so if another Touchdown setting is required after the set time,
   set the same event on another row and change the value.
   * In this case, because the slope of the peak end point is specified, it is not possible to end the peak detection exactly at 4.9 min.

2. With the Traditional Integration Algorithm, the peak detection ends within the range specified by the Inhibit Integration event even though peak elution continues, so select the Traditional integration.

ADDITIONAL INFORMATION