2 \documentclass[10pt, peerreview, compsocconf]{IEEEtran}
5 \usepackage[utf8]{inputenc}
6 %\usepackage[cyr]{aeguill}
7 %\usepackage{pstricks,pst-node,pst-text,pst-3d}
16 \usepackage{subfigure}
21 \usepackage[ruled,lined,linesnumbered]{algorithm2e}
23 %%%%%%%%%%%%%%%%%%%%%%%%%%%% LyX specific LaTeX commands.
24 \newcommand{\noun}[1]{\textsc{#1}}
26 \newcommand{\tab}{\ \ \ }
33 %% \author{\IEEEauthorblockN{Authors Name/s per 1st Affiliation (Author)}
34 %% \IEEEauthorblockA{line 1 (of Affiliation): dept. name of organization\\
35 %% line 2: name of organization, acronyms acceptable\\
36 %% line 3: City, Country\\
37 %% line 4: Email: name@xyz.com}
39 %% \IEEEauthorblockN{Authors Name/s per 2nd Affiliation (Author)}
40 %% \IEEEauthorblockA{line 1 (of Affiliation): dept. name of organization\\
41 %% line 2: name of organization, acronyms acceptable\\
42 %% line 3: City, Country\\
43 %% line 4: Email: name@xyz.com}
48 \title{Using FPGAs for high speed and real time cantilever deflection estimation}
49 \author{\IEEEauthorblockN{Raphaël Couturier\IEEEauthorrefmark{1}, Stéphane Domas\IEEEauthorrefmark{1}, Gwenhaël Goavec-Merou\IEEEauthorrefmark{2} and Michel Lenczner\IEEEauthorrefmark{2}}
50 \IEEEauthorblockA{\IEEEauthorrefmark{1}FEMTO-ST, DISC, University of Franche-Comte, Belfort, France\\
51 \{raphael.couturier,stephane.domas\}@univ-fcomte.fr}
52 \IEEEauthorblockA{\IEEEauthorrefmark{2}FEMTO-ST, Time-Frequency, University of Franche-Comte, Besançon, France\\
53 \{michel.lenczner@utbm.fr,gwenhael.goavec@trabucayre.com}
73 FPGA, cantilever, interferometry.
77 \IEEEpeerreviewmaketitle
79 \section{Introduction}
81 Cantilevers are used inside atomic force microscope (AFM) which provides high
82 resolution images of surfaces. Several technics have been used to measure the
83 displacement of cantilevers in litterature. For example, it is possible to
84 determine accurately the deflection with different mechanisms.
85 In~\cite{CantiPiezzo01}, authors used piezoresistor integrated into the
86 cantilever. Nevertheless this approach suffers from the complexity of the
87 microfabrication process needed to implement the sensor in the cantilever.
88 In~\cite{CantiCapacitive03}, authors have presented an cantilever mechanism
89 based on capacitive sensing. This kind of technic also involves to instrument
90 the cantiliver which result in a complex fabrication process.
92 In this paper our attention is focused on a method based on interferometry to
93 measure cantilevers' displacements. In this method cantilevers are illuminated
94 by an optic source. The interferometry produces fringes on each cantilevers
95 which enables to compute the cantilever displacement. In order to analyze the
96 fringes a high speed camera is used. Images need to be processed quickly and
97 then a estimation method is required to determine the displacement of each
98 cantilever. In~\cite{AFMCSEM11}, the authors have used an algorithm based on
99 spline to estimate the cantilevers' positions.
101 The overall process gives
102 accurate results but all the computation are performed on a standard computer
103 using labview. Consequently, the main drawback of this implementation is that
104 the computer is a bootleneck in the overall process. In this paper we propose to
105 use a method based on least square and to implement all the computation on a
108 The remainder of the paper is organized as follows. Section~\ref{sec:measure}
109 describes more precisely the measurement process. Our solution based on the
110 least square method and the implementation on FPGA is presented in
111 Section~\ref{sec:solus}. Experimentations are described in
112 Section~\ref{sec:results}. Finally a conclusion and some perspectives are
117 %% quelques ref commentées sur les calculs basés sur l'interférométrie
119 \section{Measurement principles}
129 \subsection{Architecture}
131 %% description de l'architecture générale de l'acquisition d'images
132 %% avec au milieu une unité de traitement dont on ne précise pas ce
135 In order to develop simple, cost effective and user-friendly cantilever arrays,
136 authors of ~\cite{AFMCSEM11} have developped a system based of
137 interferometry. In opposition to other optical based systems, using a laser beam
138 deflection scheme and sentitive to the angular displacement of the cantilever,
139 interferometry is sensitive to the optical path difference induced by the
140 vertical displacement of the cantilever.
142 The system build by authors of~\cite{AFMCSEM11} has been developped based on a
143 Linnick interferomter~\cite{Sinclair:05}. It is illustrated in
144 Figure~\ref{fig:AFM}. A laser diode is first split (by the splitter) into a
145 reference beam and a sample beam that reachs the cantilever array. In order to
146 be able to move the cantilever array, it is mounted on a translation and
147 rotational hexapod stage with five degrees of freedom. The optical system is
148 also fixed to the stage. Thus, the cantilever array is centered in the optical
149 system which can be adjusted accurately. The beam illuminates the array by a
150 microscope objective and the light reflects on the cantilevers. Likewise the
151 reference beam reflects on a movable mirror. A CMOS camera chip records the
152 reference and sample beams which are recombined in the beam splitter and the
153 interferogram. At the beginning of each experiment, the movable mirror is
154 fitted manually in order to align the interferometric fringes approximately
155 parallel to the cantilevers. When cantilevers move due to the surface, the
156 bending of cantilevers produce movements in the fringes that can be detected
157 with the CMOS camera. Finally the fringes need to be
158 analyzed. In~\cite{AFMCSEM11}, the authors used a LabView program to compute the
159 cantilevers' movements from the fringes.
163 \includegraphics[width=\columnwidth]{AFM}
165 \caption{schema of the AFM}
170 %% image tirée des expériences.
172 \subsection{Cantilever deflection estimation}
175 As shown on image \ref{img:img-xp}, each cantilever is covered by
176 interferometric fringes. The fringes will distort when cantilevers are
177 deflected. Estimating the deflection is done by computing this
178 distortion. For that, (ref A. Meister + M Favre) proposed a method
179 based on computing the phase of the fringes, at the base of each
180 cantilever, near the tip, and on the base of the array. They assume
181 that a linear relation binds these phases, which can be use to
182 "unwrap" the phase at the tip and to determine the deflection.\\
184 More precisely, segment of pixels are extracted from images taken by a
185 high-speed camera. These segments are large enough to cover several
186 interferometric fringes and are placed at the base and near the tip of
187 the cantilevers. They are called base profile and tip profile in the
188 following. Furthermore, a reference profile is taken on the base of
189 the cantilever array.
191 The pixels intensity $I$ (in gray level) of each profile is modelized by :
195 I(x) = ax+b+A.cos(2\pi f.x + \theta)
198 where $x$ is the position of a pixel in its associated segment.
200 The global method consists in two main sequences. The first one aims
201 to determin the frequency $f$ of each profile with an algorithm based
202 on spline interpolation (see section \ref{algo-spline}). It also
203 computes the coefficient used for unwrapping the phase. The second one
204 is the acquisition loop, while which images are taken at regular time
205 steps. For each image, the phase $\theta$ of all profiles is computed
206 to obtain, after unwrapping, the deflection of
207 cantilevers. Originally, this computation was also done with an
208 algorithm based on spline. This article proposes a new version based
209 on a least square method.
211 \subsection{Design goals}
214 The main goal is to implement a computing unit to estimate the
215 deflection of about $10\times10$ cantilevers, faster than the stream of
216 images coming from the camera. The accuracy of results must be close
217 to the maximum precision ever obtained experimentally on the
218 architecture, i.e. 0.3nm. Finally, the latency between an image
219 entering in the unit and the deflections must be as small as possible
220 (NB : future works plan to add some control on the cantilevers).\\
222 If we put aside some hardware issues like the speed of the link
223 between the camera and the computation unit, the time to deserialize
224 pixels and to store them in memory, ... the phase computation is
225 obviously the bottle-neck of the whole process. For example, if we
226 consider the camera actually in use, an exposition time of 2.5ms for
227 $1024\times 1204$ pixels seems the minimum that can be reached. For
228 100 cantilevers, if we neglect the time to extract pixels, it implies
229 that computing the deflection of a single
230 cantilever should take less than 25$\mu$s, thus 12.5$\mu$s by phase.\\
232 In fact, this timing is a very hard constraint. Let consider a very
233 small programm that initializes twenty million of doubles in memory
234 and then does 1000000 cumulated sums on 20 contiguous values
235 (experimental profiles have about this size). On an intel Core 2 Duo
236 E6650 at 2.33GHz, this program reaches an average of 155Mflops.
238 %%Itimplies that the phase computation algorithm should not take more than
239 %%$155\times 12.5 = 1937$ floating operations. For integers, it gives $3000$ operations.
241 Obviously, some cache effects and optimizations on
242 huge amount of computations can drastically increase these
243 performances : peak efficiency is about 2.5Gflops for the considered
244 CPU. But this is not the case for phase computation that used only few
247 In order to evaluate the original algorithm, we translated it in C
248 language. Profiles are read from a 1Mo file, as if it was an image
249 stored in a device file representing the camera. The file contains 100
250 profiles of 21 pixels, equally scattered in the file. We obtained an
251 average of 10.5$\mu$s by profile (including I/O accesses). It is under
252 are requirements but close to the limit. In case of an occasional load
253 of the system, it could be largely overtaken. A solution would be to
254 use a real-time operating system but another one to search for a more
257 But the main drawback is the latency of such a solution : since each
258 profile must be treated one after another, the deflection of 100
259 cantilevers takes about $200\times 10.5 = 2.1$ms, which is inadequate
260 for an efficient control. An obvious solution is to parallelize the
261 computations, for example on a GPU. Nevertheless, the cost to transfer
262 profile in GPU memory and to take back results would be prohibitive
263 compared to computation time. It is certainly more efficient to
264 pipeline the computation. For example, supposing that 200 profiles of
265 20 pixels can be pushed sequentially in the pipelined unit cadenced at
266 a 100MHz (i.e. a pixel enters in the unit each 10ns), all profiles
267 would be treated in $200\times 20\times 10.10^{-9} =$ 40$\mu$s plus
268 the latency of the pipeline. This is about 500 times faster than
271 For these reasons, an FPGA as the computation unit is the best choice
272 to achieve the required performance. Nevertheless, passing from
273 a C code to a pipelined version in VHDL is not obvious at all. As
274 explained in the next section, it can even be impossible because of
275 some hardware constraints specific to FPGAs.
278 \section{Proposed solution}
281 Project Oscar aims to provide an hardware and software architecture to
282 estimate and control the deflection of cantilevers. The hardware part
283 consists in a high-speed camera, linked on an embedded board hosting
284 FPGAs. By the way, the camera output stream can be pushed directly
285 into the FPGA. The software part is mostly the VHDL code that
286 deserializes the camera stream, extracts profile and computes the
287 deflection. Before focusing on our work to implement the phase
288 computation, we give some general informations about FPGAs and the
293 A field-programmable gate array (FPGA) is an integrated circuit designed to be
294 configured by the customer. A hardware description language (HDL) is used to
295 configure a FPGA. FGPAs are composed of programmable logic components, called
296 logic blocks. These blocks can be configured to perform simple (AND, XOR, ...)
297 or complex combinational functions. Logic blocks are interconnected by
298 reconfigurable links. Modern FPGAs contains memory elements and multipliers
299 which enables to simplify the design and increase the speed. As the most complex
300 operation operation on FGPAs is the multiplier, design of FGPAs should not used
301 complex operations. For example, a divider is not an available operation and it
302 should be programmed using simple components.
304 FGPAs programming is very different from classic processors programming. When
305 logic block are programmed and linked to performed an operation, they cannot be
306 reused anymore. FPGA are cadenced more slowly than classic processors but they can
307 performed pipelined as well as parallel operations. A pipeline provides a way
308 manipulate data quickly since at each clock top to handle a new data. However,
309 using a pipeline consomes more logics and components since they are not
310 reusable, nevertheless it is probably the most efficient technique on FPGA.
311 Parallel operations can be used in order to manipulate several data
312 simultaneously. When it is possible, using a pipeline is a good solution to
313 manipulate new data at each clock top and using parallelism to handle
314 simultaneously several data streams.
316 %% parler du VHDL, synthèse et bitstream
317 \subsection{The board}
319 The board we use is designed by the Armadeus compagny, under the name
320 SP Vision. It consists in a development board hosting a i.MX27 ARM
321 processor (from Freescale). The board includes all classical
322 connectors : USB, Ethernet, ... A Flash memory contains a Linux kernel
323 that can be launched after booting the board via u-Boot.
325 The processor is directly connected to a Spartan3A FPGA (from Xilinx)
326 via its special interface called WEIM. The Spartan3A is itself
327 connected to a Spartan6 FPGA. Thus, it is possible to develop programs
328 that communicate between i.MX and Spartan6, using Spartan3 as a
329 tunnel. By default, the WEIM interface provides a clock signal at
330 100MHz that is connected to dedicated FPGA pins.
332 The Spartan6 is an LX100 version. It has 15822 slices, equivalent to
333 101261 logic cells. There are 268 internal block RAM of 18Kbits, and
334 180 dedicated multiply-adders (named DSP48), which is largely enough
337 Some I/O pins of Spartan6 are connected to two $2\times 17$ headers
338 that can be used as user wants. For the project, they will be
339 connected to the interface card of the camera.
341 \subsection{Considered algorithms}
343 Two solutions have been studied to achieve phase computation. The
344 original one, proposed by A. Meister and M. Favre, is based on
345 interpolation by splines. It allows to compute frequency and
346 phase. The second one, detailed in this article, is based on a
347 classical least square method but suppose that frequency is already
350 \subsubsection{Spline algorithm}
351 \label{sec:algo-spline}
352 Let consider a profile $P$, that is a segment of $M$ pixels with an
353 intensity in gray levels. Let call $I(x)$ the intensity of profile in $x
356 At first, only $M$ values of $I$ are known, for $x = 0, 1,
357 \ldots,M-1$. A normalisation allows to scale known intensities into
358 $[-1,1]$. We compute splines that fit at best these normalised
359 intensities. Splines are used to interpolate $N = k\times M$ points
360 (typically $k=4$ is sufficient), within $[0,M[$. Let call $x^s$ the
361 coordinates of these $N$ points and $I^s$ their intensities.
363 In order to have the frequency, the mean line $a.x+b$ (see equation \ref{equ:profile}) of $I^s$ is
364 computed. Finding intersections of $I^s$ and this line allow to obtain
365 the period thus the frequency.
367 The phase is computed via the equation :
369 \theta = atan \left[ \frac{\sum_{i=0}^{N-1} sin(2\pi f x^s_i) \times I^s(x^s_i)}{\sum_{i=0}^{N-1} cos(2\pi f x^s_i) \times I^s(x^s_i)} \right]
372 Two things can be noticed :
374 \item the frequency could also be obtained using the derivates of
375 spline equations, which only implies to solve quadratic equations.
376 \item frequency of each profile is computed a single time, before the
377 acquisition loop. Thus, $sin(2\pi f x^s_i)$ and $cos(2\pi f x^s_i)$
378 could also be computed before the loop, which leads to a much faster
379 computation of $\theta$.
382 \subsubsection{Least square algorithm}
384 Assuming that we compute the phase during the acquisition loop,
385 equation \ref{equ:profile} has only 4 parameters :$a, b, A$, and
386 $\theta$, $f$ and $x$ being already known. Since $I$ is non-linear, a
387 least square method based an Gauss-newton algorithm must be used to
388 determine these four parameters. Since it is an iterative process
389 ending with a convergence criterion, it is obvious that it is not
390 particularly adapted to our design goals.
392 Fortunatly, it is quite simple to reduce the number of parameters to
393 only $\theta$. Let $x^p$ be the coordinates of pixels in a segment of
394 size $M$. Thus, $x^p = 0, 1, \ldots, M-1$. Let $I(x^p)$ be their
395 intensity. Firstly, we "remove" the slope by computing :
397 \[I^{corr}(x^p) = I(x^p) - a.x^p - b\]
399 Since linear equation coefficients are searched, a classical least
400 square method can be used to determine $a$ and $b$ :
402 \[a = \frac{covar(x^p,I(x^p))}{var(x^p)} \]
404 Assuming an overlined symbol means an average, then :
406 \[b = \overline{I(x^p)} - a.\overline{{x^p}}\]
408 Let $A$ be the amplitude of $I^{corr}$, i.e.
410 \[A = \frac{max(I^{corr}) - min(I^{corr})}{2}\]
412 Then, the least square method to find $\theta$ is reduced to search the minimum of :
414 \[\sum_{i=0}^{M-1} \left[ cos(2\pi f.i + \theta) - \frac{I^{corr}(i)}{A} \right]^2\]
416 It is equivalent to derivate this expression and to solve the following equation :
419 2\left[ cos\theta \sum_{i=0}^{M-1} I^{corr}(i).sin(2\pi f.i) + sin\theta \sum_{i=0}^{M-1} I^{corr}(i).cos(2\pi f.i)\right] \\
420 - A\left[ cos2\theta \sum_{i=0}^{M-1} sin(4\pi f.i) + sin2\theta \sum_{i=0}^{M-1} cos(4\pi f.i)\right] = 0
423 Several points can be noticed :
425 \item As in the spline method, some parts of this equation can be
426 computed before the acquisition loop. It is the case of sums that do
427 not depend on $\theta$ :
429 \[ \sum_{i=0}^{M-1} sin(4\pi f.i), \sum_{i=0}^{M-1} cos(4\pi f.i) \]
431 \item Lookup tables for $sin(2\pi f.i)$ and $cos(2\pi f.i)$ can also be
434 \item The simplest method to find the good $\theta$ is to discretize
435 $[-\pi,\pi]$ in $nb_s$ steps, and to search which step leads to the
436 result closest to zero. By the way, three other lookup tables can
437 also be computed before the loop :
439 \[ sin \theta, cos \theta, \]
441 \[ \left[ cos 2\theta \sum_{i=0}^{M-1} sin(4\pi f.i) + sin 2\theta \sum_{i=0}^{M-1} cos(4\pi f.i)\right] \]
443 \item This search can be very fast using a dichotomous process in $log_2(nb_s)$
447 Finally, the whole summarizes in an algorithm (called LSQ in the following) in two parts, one before and one during the acquisition loop :
449 \caption{LSQ algorithm - before acquisition loop.}
450 \label{alg:lsq-before}
452 $M \leftarrow $ number of pixels of the profile\\
453 I[] $\leftarrow $ intensities of pixels\\
454 $f \leftarrow $ frequency of the profile\\
455 $s4i \leftarrow \sum_{i=0}^{M-1} sin(4\pi f.i)$\\
456 $c4i \leftarrow \sum_{i=0}^{M-1} cos(4\pi f.i)$\\
457 $nb_s \leftarrow $ number of discretization steps of $[-\pi,\pi]$\\
459 \For{$i=0$ to $nb_s $}{
460 $\theta \leftarrow -\pi + 2\pi\times \frac{i}{nb_s}$\\
461 lut$_s$[$i$] $\leftarrow sin \theta$\\
462 lut$_c$[$i$] $\leftarrow cos \theta$\\
463 lut$_A$[$i$] $\leftarrow cos 2 \theta \times s4i + sin 2 \theta \times c4i$\\
464 lut$_{sfi}$[$i$] $\leftarrow sin (2\pi f.i)$\\
465 lut$_{cfi}$[$i$] $\leftarrow cos (2\pi f.i)$\\
469 \begin{algorithm}[ht]
470 \caption{LSQ algorithm - during acquisition loop.}
471 \label{alg:lsq-during}
473 $\bar{x} \leftarrow \frac{M-1}{2}$\\
474 $\bar{y} \leftarrow 0$, $x_{var} \leftarrow 0$, $xy_{covar} \leftarrow 0$\\
475 \For{$i=0$ to $M-1$}{
476 $\bar{y} \leftarrow \bar{y} + $ I[$i$]\\
477 $x_{var} \leftarrow x_{var} + (i-\bar{x})^2$\\
479 $\bar{y} \leftarrow \frac{\bar{y}}{M}$\\
480 \For{$i=0$ to $M-1$}{
481 $xy_{covar} \leftarrow xy_{covar} + (i-\bar{x}) \times (I[i]-\bar{y})$\\
483 $slope \leftarrow \frac{xy_{covar}}{x_{var}}$\\
484 $start \leftarrow y_{moy} - slope\times \bar{x}$\\
485 \For{$i=0$ to $M-1$}{
486 $I[i] \leftarrow I[i] - start - slope\times i$\\
489 $I_{max} \leftarrow max_i(I[i])$, $I_{min} \leftarrow min_i(I[i])$\\
490 $amp \leftarrow \frac{I_{max}-I_{min}}{2}$\\
492 $Is \leftarrow 0$, $Ic \leftarrow 0$\\
493 \For{$i=0$ to $M-1$}{
494 $Is \leftarrow Is + I[i]\times $ lut$_{sfi}$[$i$]\\
495 $Ic \leftarrow Ic + I[i]\times $ lut$_{cfi}$[$i$]\\
498 $\delta \leftarrow \frac{nb_s}{2}$, $b_l \leftarrow 0$, $b_r \leftarrow \delta$\\
499 $v_l \leftarrow -2.I_s - amp.$lut$_A$[$b_l$]\\
501 \While{$\delta >= 1$}{
503 $v_r \leftarrow 2.[ Is.$lut$_c$[$b_r$]$ + Ic.$lut$_s$[$b_r$]$ ] - amp.$lut$_A$[$b_r$]\\
505 \If{$!(v_l < 0$ and $v_r >= 0)$}{
506 $v_l \leftarrow v_r$ \\
507 $b_l \leftarrow b_r$ \\
509 $\delta \leftarrow \frac{\delta}{2}$\\
510 $b_r \leftarrow b_l + \delta$\\
512 \uIf{$!(v_l < 0$ and $v_r >= 0)$}{
513 $v_l \leftarrow v_r$ \\
514 $b_l \leftarrow b_r$ \\
515 $b_r \leftarrow b_l + 1$\\
516 $v_r \leftarrow 2.[ Is.$lut$_c$[$b_r$]$ + Ic.$lut$_s$[$b_r$]$ ] - amp.$lut$_A$[$b_r$]\\
519 $b_r \leftarrow b_l + 1$\\
522 \uIf{$ abs(v_l) < v_r$}{
523 $b_{\theta} \leftarrow b_l$ \\
526 $b_{\theta} \leftarrow b_r$ \\
528 $\theta \leftarrow \pi\times \left[\frac{2.b_{ref}}{nb_s}-1\right]$\\
532 \subsubsection{Comparison}
534 We compared the two algorithms on the base of three criterions :
536 \item precision of results on a cosinus profile, distorted with noise,
537 \item number of operations,
538 \item complexity to implement an FPGA version.
541 For the first item, we produced a matlab version of each algorithm,
542 running with double precision values. The profile was generated for
543 about 34000 different values of period ($\in [3.1, 6.1]$, step = 0.1),
544 phase ($\in [-3.1 , 3.1]$, step = 0.062) and slope ($\in [-2 , 2]$,
545 step = 0.4). For LSQ, $nb_s = 1024$, which leads to a maximal error of
546 $\frac{\pi}{1024}$ on phase computation. Current A. Meister and
547 M. Favre experiments show a ratio of 50 between variation of phase and
548 the deflection of a lever. Thus, the maximal error due to
549 discretization correspond to an error of 0.15nm on the lever
550 deflection, which is smaller than the best precision they achieved,
553 For each test, we add some noise to the profile : each group of two
554 pixels has its intensity added to a random number picked in $[-N,N]$
555 (NB: it should be noticed that picking a new value for each pixel does
556 not distort enough the profile). The absolute error on the result is
557 evaluated by comparing the difference between the reference and
558 computed phase, out of $2\pi$, expressed in percents. That is : $err =
559 100\times \frac{|\theta_{ref} - \theta_{comp}|}{2\pi}$.
561 Table \ref{tab:algo_prec} gives the maximum and average error for the two algorithms and increasing values of $N$.
565 \begin{tabular}{|c|c|c|c|c|}
567 & \multicolumn{2}{c|}{SPL} & \multicolumn{2}{c|}{LSQ} \\ \cline{2-5}
568 noise & max. err. & aver. err. & max. err. & aver. err. \\ \hline
569 0 & 2.46 & 0.58 & 0.49 & 0.1 \\ \hline
570 2.5 & 2.75 & 0.62 & 1.16 & 0.22 \\ \hline
571 5 & 3.77 & 0.72 & 2.47 & 0.41 \\ \hline
572 7.5 & 4.72 & 0.86 & 3.33 & 0.62 \\ \hline
573 10 & 5.62 & 1.03 & 4.29 & 0.81 \\ \hline
574 15 & 7.96 & 1.38 & 6.35 & 1.21 \\ \hline
575 30 & 17.06 & 2.6 & 13.94 & 2.45 \\ \hline
578 \caption{Error (in \%) for cosinus profiles, with noise.}
579 \label{tab:algo_prec}
583 These results show that the two algorithms are very close, with a
584 slight advantage for LSQ. Furthemore, both behave very well against
585 noise. Assuming the experimental ratio of 50 (see above), an error of
586 1 percent on phase correspond to an error of 0.5nm on the lever
587 deflection, which is very close to the best precision.
589 Obviously, it is very hard to predict which level of noise will be
590 present in real experiments and how it will distort the
591 profiles. Nevertheless, we can see on figure \ref{fig:noise20} the
592 profile with $N=10$ that leads to the biggest error. It is a bit
593 distorted, with pikes and straight/rounded portions, and relatively
594 close to most of that come from experiments. Figure \ref{fig:noise60}
595 shows a sample of worst profile for $N=30$. It is completly distorted,
596 largely beyond the worst experimental ones.
600 \includegraphics[width=9cm]{intens-noise20-spl}
602 \caption{Sample of worst profile for N=10}
608 \includegraphics[width=9cm]{intens-noise60-lsq}
610 \caption{Sample of worst profile for N=30}
614 The second criterion is relatively easy to estimate for LSQ and harder
615 for SPL because of $atan$ operation. In both cases, it is proportional
616 to numbers of pixels $M$. For LSQ, it also depends on $nb_s$ and for
617 SPL on $N = k\times M$, i.e. the number of interpolated points.
619 We assume that $M=20$, $nb_s=1024$, $k=4$, all possible parts are
620 already in lookup tables and a limited set of operations (+, -, *, /,
621 <, >) is taken account. Translating the two algorithms in C code, we
622 obtain about 430 operations for LSQ and 1550 (plus few tenth for
623 $atan$) for SPL. This result is largely in favor of LSQ. Nevertheless,
624 considering the total number of operations is not really pertinent for
625 an FPGA implementation : it mainly depends on the type of operations
627 ordering. The final decision is thus driven by the third criterion.\\
629 The Spartan 6 used in our architecture has hard constraint : it has no
630 built-in floating point units. Obviously, it is possible to use some
631 existing "black-boxes" for double precision operations. But they have
632 a quite long latency. It is much simpler to exclusively use integers,
633 with a quantization of all double precision values. Obviously, this
634 quantization should not decrease too much the precision of
635 results. Furthermore, it should not lead to a design with a huge
636 latency because of operations that could not complete during a single
637 or few clock cycles. Divisions are in this case and, moreover, they
638 need an varying number of clock cycles to complete. Even
639 multiplications can be a problem : DSP48 take inputs of 18 bits
640 maximum. For larger multiplications, several DSP must be combined,
641 increasing the latency.
643 Nevertheless, the hardest constraint does not come from the FPGA
644 characteristics but from the algorithms. Their VHDL implentation will
645 be efficient only if they can be fully (or near) pipelined. By the
646 way, the choice is quickly done : only a small part of SPL can be.
647 Indeed, the computation of spline coefficients implies to solve a
648 tridiagonal system $A.m = b$. Values in $A$ and $b$ can be computed
649 from incoming pixels intensity but after, the back-solve starts with
650 the lastest values, which breaks the pipeline. Moreover, SPL relies on
651 interpolating far more points than profile size. Thus, the end
652 of SPL works on a larger amount of data than the beginning, which
653 also breaks the pipeline.
655 LSQ has not this problem : all parts except the dichotomial search
656 work on the same amount of data, i.e. the profile size. Furthermore,
657 LSQ needs less operations than SPL, implying a smaller output
658 latency. Consequently, it is the best candidate for phase
659 computation. Nevertheless, obtaining a fully pipelined version
660 supposes that operations of different parts complete in a single clock
661 cycle. It is the case for simulations but it completely fails when
662 mapping and routing the design on the Spartan6. By the way,
663 extra-latency is generated and there must be idle times between two
664 profiles entering into the pipeline.
666 %%Before obtaining the least bitstream, the crucial question is : how to
667 %%translate the C code the LSQ into VHDL ?
670 %\subsection{VHDL design paradigms}
672 \section{Experimental tests}
674 \subsection{VHDL implementation}
676 % - ecriture d'un code en C avec integer
677 % - calcul de la taille max en bit de chaque variable en fonction de la quantization.
678 % - tests de quantization : équilibre entre précision et contraintes FPGA
679 % - en parallèle : simulink et VHDL à la main
681 \subsection{Simulation}
684 % au mieux : une phase tous les 33 cycles, latence de 95 cycles.
685 % mais routage/placement impossible.
686 \subsection{Bitstream creation}
688 % pas fait mais prévision d'une sortie tous les 480ns avec une latence de 1120
695 \section{Conclusion and perspectives}
698 \bibliographystyle{plain}
699 \bibliography{biblio}