Dbrown Hi, We have quite a large Agilent laser log file with raster data. Iolite appears to misread some of the "ON" states as ablation signal (i.e. there are multiple "ON" states for a single analysis). As a result, syncing the log file and individual csv timestamps is not possible. Is there an import procedure that deals with this kind of log file? Cheers, Dillon
Bence Hi Dillon, What sort of laser system are you using? If it would help, you can send your experiment (raw mass spec files and laser log file) to the iolite support email and we can take a look at it for you. Kind regards, -Bence
Dbrown Bence Hi Bence, we're using an ASI RESOlution 193nm system. Thanks, I'll send those files through. Dillon
Joe Dbrown There are a few competing problems here: Because each line has been recorded into its own file and the Agilent timestamps are not good (in general, not your fault), you end up in a situation where you cannot synchronize all of the data to the laser log with one offset. In the future you could avoid the worst of this by recording things into 1 data file. That means that you need to use the "sample sync" feature in the laser sync window. This looks at the data surrounding each on event in the laser log and looks for an offset for each event by maximizing the correlation of the on event with the time-local data. Unfortunately, as you mentioned, you're getting multiple on events for each line (maybe pre-ablation?), so using sample sync will make a mess of things because all of those "extra" on events will also be synchronized to the data and mess things up. To get around this, I've added some features to the laser log importer that allow you to i) skip short duration on events (doesn't work in your case because some of those extra on events are longer than real on events), and ii) only keep the last on event per sample. This second option works great for your log. Finally, due to the epic nature of your dataset, I discovered a bug with the laser log importer that still prevented things from working perfectly. That bug is now fixed. I'll send a link to the io4 in an email shortly. All the best, Joe