Chromatography Peak Integration: Using Chromperfect Timed Events for Repeatable Results
- Chromperfect
- 2 days ago
- 5 min read
Chromatography peak integration is one of the most important parts of any chromatography data system workflow. A chromatogram may contain clean, well-separated peaks, but it may also contain baseline disturbances, closely spaced peaks, rider peaks, negative peaks, noise, or regions that should not be integrated at all.
Manual integration can be useful when reviewing or correcting a single chromatogram. However, when the same integration behavior is required repeatedly, it is better to define that behavior in the method. This is where Chromperfect timed events become especially useful.
Timed events allow the method to control integration behavior at specific points in the chromatogram. Once added to the method file, these events can be applied automatically and consistently in future runs.
Why Timed Events Matter in Chromatography Peak Integration
In routine chromatography, consistency matters. If a laboratory repeatedly adjusts the same peak start point, stop point, split point, or baseline manually, the process becomes slower and less consistent. It also places more responsibility on the individual user reviewing the chromatogram.
Timed events help solve this problem by moving the integration instruction into the method file.
Instead of manually correcting the same problem again and again, the method can be configured to apply the appropriate integration behavior automatically. This makes timed events a practical tool for repeatable chromatography peak integration.
Examples include:
Turning integration off during a solvent disturbance
Turning integration back on after an unwanted region
Forcing a baseline point at a specific time
Setting a baseline at the next valley
Creating a horizontal baseline over a defined region
Splitting a peak at a specific point
Summing adjacent peaks across a region
Applying skimming to rider peaks
Changing peak detection sensitivity during the run
Showing or hiding display-related labels and tic marks
Controlling relay outputs on compatible Tigre acquisition hardware
Manual Integration Versus Timed Events
Manual integration changes apply to the chromatogram currently being reviewed. This is useful when a result needs individual attention, but it is not normally the best approach when the same correction is needed every time the method is used.
Timed events are different. They are stored in the method and applied during integration. This means they are better suited to repeatable chromatographic behavior.
Use manual integration when you need to review or correct one chromatogram.
Use timed events when you want the method to apply the same behavior automatically in future runs.
This distinction is important. Timed events are not simply a faster way to make a manual edit.
They are part of the method-based integration strategy.
Integration On and Off
The simplest timed events control whether integration is active.
INT+ turns integration on.
INT- turns integration off.
These events are useful when a region of the chromatogram should be ignored during integration. For example, the early part of a run may contain solvent disturbance, injection disturbance, or another signal that should not produce integrated peaks.
In that situation, INT- can be placed before the unwanted region, and INT+ can be placed where normal integration should resume.
Baseline Control Events
Baseline placement is one of the most common reasons for using timed events.
SBN sets the baseline at the event point.
SBNV sets the baseline at the next valley after the event.
SBAV+ and SBAV- control baseline behavior across a region by applying baseline handling at valleys.
These events can help when the automatic baseline decision does not match the intended integration. They are especially useful when the chromatographic pattern is repeatable, but the baseline requires guidance from the method.
Horizontal Baseline Events
HORZ+ and HORZ- are used when a horizontal baseline is required over a defined section of the chromatogram.
HORZ+ starts horizontal baseline behavior.
HORZ- stops horizontal baseline behavior.
This can be useful when the automatic baseline follows a slope or drift that is not appropriate for the peak group being integrated.
Peak Width, Threshold, and Detection Sensitivity
Some timed events affect how peaks are detected.
PW+ and PW- adjust peak width behavior.
TH+ and TH- adjust the threshold.
MUT measures baseline noise and updates the threshold.
NEG+ and NEG- control negative peak detection.
These events are useful when different parts of the chromatogram have different peak shapes, peak widths, noise levels, or detection requirements.
For example, early peaks may be narrow, while later peaks may be broader. In that case, peak width events can help the integration algorithm respond more appropriately in different parts of the run.
Peak Splitting and Peak Summing
SPLIT is used when one detected peak needs to be divided into two peaks. It is placed at the point where the split should occur.
SUM+ and SUM- are used when adjacent peaks need to be treated together across a defined region.
These events are directly related to how peaks are interpreted and reported. They should be used carefully, and the chromatogram should always be reintegrated and reviewed after the event is added.
Skimming and Rider Peaks
Skimming events are used where a smaller rider peak appears on the side of a larger peak.
SKIM forces skimming for the relevant peak or cluster.
SKIM+ and SKIM- control automatic skimming behavior across a region.
These events are useful where rider peaks occur regularly and the method needs to handle them consistently.
Display, Reporting, and Selection Events
Not every timed event changes core peak integration behavior. Some affect how information is displayed or selected.
TIC shows peak boundary tic marks.
POINTS shows individual data points.
RET+ and RET- control retention time labels.
SEL1 through SEL9 control peak selection behavior.
These events are useful when the issue is mainly display, review, or reporting rather than peak detection itself.
Relay Events for Tigre Acquisition Hardware
Relay timed events are different from normal integration events. They are used for hardware relay control on compatible Tigre acquisition interfaces.
The relay events follow a simple pattern.
R1O opens relay 1.
R1C closes relay 1.
The same pattern continues through relay 8.
These events should be thought of as hardware control events, not peak integration events. They are included in the timed event list, but they are not normally the events a user would choose when adjusting peak starts, peak stops, baselines, splitting, skimming, or tic marks.
Best Practice When Using Timed Events
Timed events are powerful because they are part of the method. That also means they should be used carefully.
A good workflow is to make one change at a time, reintegrate the chromatogram, and confirm the result before adding more events.
This makes it much easier to understand which event caused which change.
In practice:
Start with the problem you are trying to solve.
Choose the simplest timed event that addresses the issue.
Add the event to the method.
Reintegrate the chromatogram.
Review the result carefully.
Only add another event if it is still needed.
The goal is not to fill the method with timed events. The goal is to use the fewest events necessary for reliable, repeatable chromatography peak integration.
Summary
Chromperfect timed events provide a method-based way to control chromatography peak integration. They allow repeatable integration behavior to be saved in the method instead of relying on repeated manual changes to individual chromatograms.
Manual integration is useful when one chromatogram needs review or correction.
Timed events are useful when the same behavior should be applied automatically in future runs.
By using timed events carefully, laboratories can improve consistency, reduce repeated manual work, and make chromatography peak integration more repeatable across routine methods.
Comments