Selecting integration periods automatically (Part 1)

For anyone trying to process an even moderately sized dataset, the ability to select integration periods automatically is a huge timesaver. In addition, if you’re trying for reproducibility in the way you’re selecting each analysis, using an automated approach makes this a lot easier than trying to manually select exactly the same intervals over and over again.

Iolite has several ways for you to select integrations automatically, and these will be the focus of a couple of separate blog posts. In this post, I’m going to show you how to use the “information from import” option, which is most useful for sessions consisting of numerous discrete analyses (either in separate files or within a single file). For those of you acquiring laser log files, you can use the “laser log file” option, and the actual selection of integration periods will be virtually identical to what’s presented here (there’s a bit of extra stuff for synchronising your laser log file with your acquired data, but I’m not going to go into that here).

If your analyses were all acquired in large files, you won’t get much benefit from this approach, but luckily for you we’ve just added a 3rd option called “detect from beam intensity”. It’s quite a powerful tool that uses channels from your DRS to discriminate time periods of interest, but it will have an entire post to itself in the near future, so I won’t go into it more here…

So now to the main event – I’ve put together the following video to walk you through the process of selecting integration periods automatically:


  1. A question regarding the automatic integrations option.
    We are using the latest version of Iolite and FIN2 data files created by Glitter export from an Element2 ICP, and file labels show up with correct file names in the different Iolite windows. However, in the automatic integrations window, all data files have the name of the Element2 sequence file, which means we cannot perform text match or readily identify standards, secondary standards and unknowns.

    Any idea how to fix this?