How to compare peak height, area and retention time across many runs

Is the retention time drifting? Is the area of the standard stable over the sequence? Both questions need the same peak, in every run, in one table. The window table does that for a whole folder of runs at once.

Pro tool, free during early access. Verify your email address and it unlocks in your browser, for a limited time. What is included · Get free early access

What the window table does

You choose a trace and set one or more time windows around the peaks you follow. For every run, Nagura Lab reports the highest point in each window, its retention time and the area. It is plain arithmetic over the data points, with no automatic peak detection, so every number can be checked by hand. For automatic peak finding and boundaries you adjust on the chart, see how peak integration works.

Make the table

  1. Open the runs, for example a whole folder (see export a whole sequence). Scroll to Batch tools and the Window table.
  2. Choose the Trace. The list shows every signal found in the runs and in how many of them. You can also pick a chromatogram at a wavelength from diode-array data (type the wavelength in nm), the total ion chromatogram, or an extracted ion chromatogram (type the m/z and the ± window). Runs that do not have the trace are left out, and the card says how many.
  3. Click Add window and type the start and end in minutes, or zoom the chart onto a peak and click Add zoomed range of the chart to copy the time range you see. Rename a window to the compound. Add one window per peak.
  4. Click Calculate. Every run gets one row per window.
  5. Click Download window table (CSV) to save nagura-window-table.csv for Excel, Origin, Python or R.

What the columns mean

The CSV also has the sample, the trace name and the window start and end next to each row.

Keep windows tight

A window counts everything inside it, not only the peak. If it is wide, or the baseline drifts across it, the plain area can even come out negative. Keep each window just around its peak, and check one or two runs against your data system before you rely on the numbers. This is not validated software: for regulated work, use your validated system.

Good to know