Optimization of data processing with the Akinetic swept-laser: algorithm to automatically adjust the a-scan synchronization delay

From National Research Council Canada

DOIResolve DOI: https://doi.org/10.1117/12.2254926
AuthorSearch for: 1; Search for: 1
Name affiliation
  1. National Research Council Canada. Energy, Mining and Environment
FormatText
TypeArticle
Proceedings titleOptical Coherence Tomography and Coherence Domain Optical Methods in Biomedicine XXI
Series titleProceedings of SPIE; no. 10053
ConferenceSPIE BiOS 2017
ISSN0277-786X
1996-756X
ISBN9781510605473
1510605479
Article number100532Q
Abstract
The Akinetic swept-laser (Insight, Lafayette, USA) is an all-semiconductor compact and tunable laser source for optical coherence tomography (OCT). Wavelength sweeps with this source are composed of valid data sections interleaved with invalid data sections. The source provides a precise trigger for each wavelength sweep and a “data valid vector” (DVV) file which identifies the indices of the valid data points in a recorded interferogram. In order to identify valid data in real time during acquisition, a delay must be precisely adjusted between the trigger and the wavelength sweep. Optimizing this delay becomes tedious when changing the interferometer configuration in a multi-purpose OCT system. The source provides tools to do this, but they are not automated and require a sample with a single clean reflection. We developed a simple and robust algorithm, integrated in our OCT data acquisition and treatment software, for finding the optimal delay correction that must be applied to accurately identify the valid data obtained with the Akinetic swept-laser. It can perform optimization either from the laser spectrum or from an interferogram and facilitates delay readjustment when the interferometer configuration is modified.
Publication date
PublisherSociety of Photo-optical Instrumentation Engineers
LanguageEnglish
Peer reviewedYes
NPARC number23002211
Export citationExport as RIS
Report a correctionReport a correction
Record identifierbfdb4d80-5211-493d-a77a-673634ad634b
Record created2017-09-05
Record modified2017-09-13
Report a problem on this page
Date modified: