Commit 4af4136f authored by Grzegorz Daniluk's avatar Grzegorz Daniluk

make all documents,presentations and papers use _graphicspath_ instead of long path to each figure

parent 09bb6cb7
......@@ -30,7 +30,7 @@ Neutrinos to Gran Sasso project \cite{cngs}. It requires:
\begin{figure}[ht]
\begin{center}
\includegraphics[width=.8\textwidth]{../../figures/calibration/loopback_fibre.ps}
\includegraphics[width=.8\textwidth]{calibration/loopback_fibre.ps}
\caption{Measuring 1-PPS offset using a loop-back fiber}
\label{fig:loopback}
\end{center}
......
......@@ -101,11 +101,11 @@ round-trip delay changes over time for the two fiber cables: 5km and 5m.
\begin{figure}[ht]
a)
\begin{minipage}{.5\textwidth}
\includegraphics[width=\textwidth]{../../figures/calibration/rtt_long.ps}
\includegraphics[width=\textwidth]{calibration/rtt_long.ps}
\end{minipage}
b)
\begin{minipage}{.5\textwidth}
\includegraphics[width=\textwidth]{../../figures/calibration/rtt_short.ps}
\includegraphics[width=\textwidth]{calibration/rtt_short.ps}
\end{minipage}
\caption{$delay_{MM}$ of 5 km (a) and 5 m (b) fiber logged for almost 12 hours using two WR Switches}
\label{fig:errors:deltemp}
......@@ -183,7 +183,7 @@ from a signal generator (e.g. Agilent 33250A) or it can be also a 62.5MHz clock
output taken from a WR Switch.
\begin{figure}[ht]
\begin{center}
\includegraphics[width=\textwidth]{../../figures/calibration/oscil_meas.ps}
\includegraphics[width=\textwidth]{calibration/oscil_meas.ps}
\caption{Measuring internal jitter of an oscilloscope}
\label{fig:errors:osc_jitter}
\end{center}
......@@ -193,7 +193,7 @@ oscilloscope using a 62.5MHz clock output from a free-running WR Switch is
presented in figure \ref{fig:errors:lecroy_jitter}.
\begin{figure}
\begin{center}
\includegraphics[width=.8\textwidth]{../../figures/calibration/lecroy_7300_jitter.ps}
\includegraphics[width=.8\textwidth]{calibration/lecroy_7300_jitter.ps}
\caption{Uncertainty of LeCroy Wavepro 7300A oscilloscope}
\label{fig:errors:lecroy_jitter}
\end{center}
......
......@@ -8,7 +8,7 @@ hardware delays and fiber propagation latencies presented in figure
\begin{figure}[ht]
\begin{center}
\includegraphics[width=\textwidth]{../../figures/calibration/link-model.ps}
\includegraphics[width=\textwidth]{calibration/link-model.ps}
\caption{White Rabbit link model}
\label{fig:intro:link-model}
\end{center}
......
......@@ -23,7 +23,7 @@ It is a few kilometers long and its parameters will be measured.
\begin{figure}[ht]
\begin{center}
\includegraphics[width=.6\textwidth]{../../figures/calibration/fiber_1.ps}
\includegraphics[width=.6\textwidth]{calibration/fiber_1.ps}
\caption{Measuring total fiber propagation latency}
\label{fig:refiber:latency}
\end{center}
......@@ -100,7 +100,7 @@ $f_1$, $f_2$ as presented in figure \ref{fig:fiasym}.
\begin{figure}[ht]
\begin{center}
\includegraphics[width=.9\textwidth]{../../figures/calibration/fiber_2.ps}
\includegraphics[width=.9\textwidth]{calibration/fiber_2.ps}
\caption{Measuring fiber $f_2$ asymmetry}
\label{fig:fiasym}
\end{center}
......@@ -178,7 +178,7 @@ $\Delta_{RX}$) of the WR Calibrator, the connection shown in figure
\begin{figure}[ht]
\begin{center}
\includegraphics[width=.5\textwidth]{../../figures/calibration/calibrator.ps}
\includegraphics[width=.5\textwidth]{calibration/calibrator.ps}
\caption{Measuring Calibrator latencies}
\label{fig:calibrator}
\end{center}
......@@ -243,7 +243,7 @@ will later create a White Rabbit Network (fig.\ref{fig:devices}).
\begin{figure}[ht]
\begin{center}
\includegraphics[width=.5\textwidth]{../../figures/calibration/wr_device.ps}
\includegraphics[width=.5\textwidth]{calibration/wr_device.ps}
\caption{WR Device calibration with WR Calibrator and known
fiber $f_1$}
\label{fig:devices}
......
......@@ -9,7 +9,7 @@ already-deployed network.
\begin{figure}[ht]
\begin{center}
\includegraphics[width=.5\textwidth]{../../figures/calibration/recover_calibrator.ps}
\includegraphics[width=.5\textwidth]{calibration/recover_calibrator.ps}
\caption{Calibrating a new WR Calibrator for an already-existing WR network}
\label{fig:recover_calibrator}
\end{center}
......
......@@ -19,6 +19,7 @@
\usepackage{listings}
\usepackage{cancel}
\graphicspath{ {../../figures/} }
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% creating subsubsubsection notation
......@@ -61,7 +62,7 @@
\begin{figure}[ht!]
\centering
\vspace{1.3cm}
\includegraphics[width=0.50\textwidth]{../../figures/logo/WRlogo.ps}
\includegraphics[width=0.50\textwidth]{logo/WRlogo.ps}
\label{fig:wr_logo}
\end{figure}
......
......@@ -129,7 +129,7 @@ value has to be incremented). The format of data word is presented in figure
\ref{fig:ep:inject_data}:
\begin{figure}[ht]
\begin{center}
\includegraphics[width=.8\textwidth]{../../../../figures/switch/ep_inject.ps}
\includegraphics[width=.8\textwidth]{switch/ep_inject.ps}
\caption{Format of data word for programming the injection engine}
\label{fig:ep:inject_data}
\end{center}
......
......@@ -33,7 +33,7 @@ read to get the event which caused the interrupt.
\begin{figure}[ht]
\begin{center}
\includegraphics[width=\textwidth]{../../../../figures/switch/nic_txdesc.ps}
\includegraphics[width=\textwidth]{switch/nic_txdesc.ps}
\caption{Tx descriptor}
\label{fig:nic:tx_desc}
\end{center}
......@@ -57,7 +57,7 @@ read to get the event which caused the interrupt.
\begin{figure}[ht]
\begin{center}
\includegraphics[width=\textwidth]{../../../../figures/switch/nic_rxdesc.ps}
\includegraphics[width=\textwidth]{switch/nic_rxdesc.ps}
\caption{Rx descriptor}
\label{fig:nic:rx_desc}
\end{center}
......
......@@ -8,7 +8,7 @@ Real-Time Subsystem.
\begin{figure}[ht]
\begin{center}
\includegraphics[width=.8\textwidth]{../../../../figures/switch/rt_sub.ps}
\includegraphics[width=.8\textwidth]{switch/rt_sub.ps}
\caption{Internal layout of Real-Time Subsystem block}
\label{fig:rts:hdl}
\end{center}
......
......@@ -113,7 +113,7 @@ figure \ref{fig:rtu:htab_adr}.
\begin{figure}[ht]
\begin{center}
\includegraphics[width=.7\textwidth]{../../../../figures/switch/rtu_mfifo_adr.ps}
\includegraphics[width=.7\textwidth]{switch/rtu_mfifo_adr.ps}
\end{center}
\caption{Structure of HTAB address}
\label{fig:rtu:htab_adr}
......
......@@ -24,6 +24,7 @@
\usepackage{hyperref}
\usepackage[none]{hyphenat}
\usepackage{listings}
\graphicspath{ {../../../../figures/} }
%\usepackage{draftwatermark}
%\usepackage{cancel}
......@@ -87,7 +88,7 @@
\begin{figure}[ht!]
\centering
\vspace{1.3cm}
\includegraphics[width=0.50\textwidth]{../../../../figures/logo/WRlogo.ps}
\includegraphics[width=0.50\textwidth]{logo/WRlogo.ps}
\label{fig:wr_logo}
\end{figure}
......
......@@ -12,7 +12,7 @@ and Network Interface \linebreak Controller.
\begin{figure}[ht]
\begin{center}
\includegraphics[width=\textwidth]{../../../../figures/switch/switch_hdl_v4.0.ps}
\includegraphics[width=\textwidth]{switch/switch_hdl_v4.0.ps}
\caption{Top HDL design of the WR Switch}
\label{fig:switch_top}
\end{center}
......
......@@ -9,7 +9,7 @@ prerequisite for achieving the required synchronization accuracy. The model
of a WR optical link is depicted in Figure~\ref{fig:link_model}.
\begin{figure}[ht!]
\centering
\includegraphics[width=15cm]{../../../figures/protocol/link_model.eps}
\includegraphics[width=15cm]{protocol/link_model.eps}
\caption{Model of a WR link (a) and relations between master and slave
clocks (b)}
\label{fig:link_model}
......@@ -61,7 +61,7 @@ recovered clock (deriving $phase_{S}$ from $offset_{MS}$) to match the phase
of the master clock, completing the synchronization.
\begin{figure}[ht!]
\centering
\includegraphics[width=15cm]{../../../figures/protocol/sync_flow.eps}
\includegraphics[width=15cm]{protocol/sync_flow.eps}
\caption{WR synchronization flow (DMTD is explained in Appendix~\ref{s:dmtd})}
\label{fig:sync_flow}
\end{figure}
......@@ -85,7 +85,7 @@ During the first two steps of the synchronization flow
and message exchanges which result in a syntonized link.
\begin{figure}[ht!]
\centering
\includegraphics[width=7cm]{../../../figures/protocol/link_detect_and_syntonization.eps}
\includegraphics[width=7cm]{protocol/link_detect_and_syntonization.eps}
\caption{WR Link detection and syntonization}
\label{fig:link_detect_and_syntonization}
\end{figure}
......@@ -121,7 +121,7 @@ single-cycle timestamping accuracy, which is necessary for reliably merging the
coarse delay with the $phase_{MM}$ phase shift during fine delay calculation.
\begin{figure}[ht!]
\centering
\includegraphics[width=17cm]{../../../figures/protocol/coarse_measurement.eps}
\includegraphics[width=17cm]{protocol/coarse_measurement.eps}
\caption{Structure of a WR timestamping unit (TSU)}
\label{fig:coarse_measurement}
\end{figure}
......@@ -159,7 +159,7 @@ clocks are jittery, the transitions may sometimes occur in reverse order,
producing an erroneous timestamp of value 1.
\begin{figure}[ht!]
\centering
\includegraphics[width=10cm]{../../../figures/protocol/ts_jitter.eps}
\includegraphics[width=10cm]{protocol/ts_jitter.eps}
\caption{Timestamping errors caused by clock jitter}
\label{fig:ts_jitter}
\end{figure}
......@@ -174,7 +174,7 @@ ensures that at least one of the timestamps is valid at any moment
current phase shift between clocks (see section \ref{s:fine_delay}).
\begin{figure}[ht!]
\centering
\includegraphics[width=12cm]{../../../figures/protocol/ts_dualedge.eps}
\includegraphics[width=12cm]{protocol/ts_dualedge.eps}
\caption{Dual-edge timestamping in WR}
\label{fig:ts_dualedge}
\end{figure}
......@@ -200,7 +200,7 @@ The fine delay measurements in WR are based on a Dual Mixer Time Difference
DMTD technology will be presented.
\begin{figure}[ht!]
\centering
\includegraphics[width=11cm]{../../../figures/misc/analog_dmtd.eps}
\includegraphics[width=11cm]{misc/analog_dmtd.eps}
\caption{Structure of an analog DMTD phase detector}
\label{fig:analog_dmtd}
\end{figure}
......@@ -238,7 +238,7 @@ analog mixing operation can be transformed into a digital sampling operation,
resulting in a digital DMTD detector, shown on fig. \ref{fig:digital_dmtd}.
\begin{figure}[ht!]
\centering
\includegraphics[width=12cm]{../../../figures/misc/dmtd.eps}
\includegraphics[width=12cm]{misc/dmtd.eps}
\caption{Structure of a digital DMTD phase detector}
\label{fig:digital_dmtd}
\end{figure}
......@@ -250,7 +250,7 @@ equivalent to analog mixing (\ref{eq:mixing2}), but the principle of a DDMTD
can be explained in a more intuitive way.
\begin{figure}[ht!]
\centering
\includegraphics[width=15cm]{../../../figures/misc/dmtd_vernier.eps}
\includegraphics[width=15cm]{misc/dmtd_vernier.eps}
\caption{A vernier (a) and signals generated by DDMTD (b)}
\label{fig:dmtd_vernier}
\end{figure}
......@@ -282,7 +282,7 @@ required, even a PLL integrated inside an FPGA can be used, eliminating all
external components.
\begin{figure}[ht!]
\centering
\includegraphics[width=8cm]{../../../figures/misc/dmtd_glitches.eps}
\includegraphics[width=8cm]{misc/dmtd_glitches.eps}
\caption{Glitches in the DMTD output caused by clock jitter}
\label{fig:dmtd_glitches}
\end{figure}
......@@ -336,7 +336,7 @@ delay was simulated using the slave's phase shifter.
\end{table}
\begin{figure}[ht!]
\centering
\includegraphics[width=13cm]{../../../figures/protocol/merging_timestamps.eps}
\includegraphics[width=13cm]{protocol/merging_timestamps.eps}
\caption{Algorithm for enhancing coarse timestamps with DMTD phase.}
\label{fig:merging_timestamps}
\end{figure}
......@@ -373,7 +373,7 @@ final output of the merging algorithm is shown in \ref{fig:merging_example}
as the thick navy trace.
\begin{figure}[ht!]
\centering
\includegraphics[width=12cm]{../../../figures/protocol/merging_example.eps}
\includegraphics[width=12cm]{protocol/merging_example.eps}
\caption{Example of $t_{4p}$ timestamp enhancing.}
\label{fig:merging_example}
\end{figure}
......@@ -416,7 +416,7 @@ asymmetry),
\end{itemize}
\begin{figure}[ht!]
\centering
\includegraphics[width=\textwidth]{../../../figures/protocol/asymmetries.eps}
\includegraphics[width=\textwidth]{protocol/asymmetries.eps}
\caption{Delay asymmetries in WR optical link.}
\label{fig:asymmetries}
\end{figure}
......@@ -540,7 +540,7 @@ because of these optimizations, PHYs may not keep constant transmit/receive
latencies. The problem is illustrated in Figure~\ref{fig:phy_asymmetry}.
\begin{figure}[ht!]
\centering
\includegraphics[width=11cm]{../../../figures/protocol/phy_asymmetry.eps}
\includegraphics[width=11cm]{protocol/phy_asymmetry.eps}
\caption{Random delays in gigabit SerDes devices (a) and blocks causing them
(b).}
\label{fig:phy_asymmetry}
......@@ -573,7 +573,7 @@ switch) is shown in Figure~\ref{fig:phy_latency_measurement}.
\begin{figure}[ht!]
\centering
% \includegraphics[width=\textwidth]{fig/tomeksDrawings/phy_latency_measurement.eps}
\includegraphics[width=0.60\textwidth]{../../../figures/misc/calibration_1.ps}
\includegraphics[width=0.60\textwidth]{misc/calibration_1.ps}
\caption{PHY latency measurement using calibration patterns.}
\label{fig:phy_latency_measurement}
\end{figure}
......@@ -647,7 +647,7 @@ of Sync-E and only the clock offset needs to be corrected. Offset correction
is split into 3 steps:
\begin{figure}[ht!]
\centering
\includegraphics[width=\textwidth]{../../../figures/protocol/adjustment_and_servo.eps}
\includegraphics[width=\textwidth]{protocol/adjustment_and_servo.eps}
\caption{WR slave offset adjustment (a) and clock servo (b)}
\label{fig:adjustment_and_servo}
\end{figure}
......
......@@ -28,6 +28,8 @@
\usepackage{times,mathptmx}
\usepackage{chngcntr}
\graphicspath{ {../../../figures/} }
%%%%%5% used in Tomeks %%%%%%%
\usepackage{listings}
\usepackage{cancel}
......@@ -81,7 +83,7 @@
\begin{figure}[ht!]
\centering
\vspace{1.3cm}
\includegraphics[width=0.50\textwidth]{../../../figures/logo/WRlogo.ps}
\includegraphics[width=0.50\textwidth]{logo/WRlogo.ps}
\label{fig:wr_logo}
\end{figure}
......@@ -225,7 +227,7 @@ and time retrieved from the upstream link to all the downstream links.
\begin{figure}[ht!]
\centering
% \vspace{-1.3cm}
\includegraphics[width=0.60\textwidth]{../../../figures/network/wrTopology.eps}
\includegraphics[width=0.60\textwidth]{network/wrTopology.eps}
\caption{White Rabbit network; it forms a hierarchical topology.}
\label{fig:wrNetwork}
\end{figure}
......@@ -262,7 +264,7 @@ which is the case in White Rabbit.
\begin{figure}[ht!]
\centering
\includegraphics[width=0.30\textwidth]{../../../figures/protocol/ptpMSGs.ps}
\includegraphics[width=0.30\textwidth]{protocol/ptpMSGs.ps}
\caption{PTP messages used by WRPTP.}
\label{fig:wrPTPmsgs}
\end{figure}
......@@ -353,7 +355,7 @@ section~\ref{sec:physcorr} provides such an equation obtained empirically for on
\begin{figure}[ht!]
\centering
\includegraphics[width=0.95\textwidth]{../../../figures/protocol/delaymodel.eps}
\includegraphics[width=0.95\textwidth]{protocol/delaymodel.eps}
\caption{Delay model of a WR link. The timestamps are accurately corrected
for link asymmetries by the usage of the four fixed delays
$\Delta_{\{tx_m, rx_s, tx_s, rx_m\}}$ and the relationship
......@@ -463,7 +465,7 @@ An example hardware implementation is described in detail in Appendix~\ref{sec:s
\begin{figure}[ht!]
\centering
\includegraphics[width=0.9\textwidth]{../../../figures/protocol/clocksHwSpec.ps}
\includegraphics[width=0.9\textwidth]{protocol/clocksHwSpec.ps}
\caption{WR protocol and WR Hardware overview.}
\label{fig:clocksHwSpec}
\end{figure}
......@@ -578,7 +580,7 @@ the standard PTP protocol will be used for synchronization.
\begin{figure}[ht!]
\centering
% \vspace{-1.3cm}
\includegraphics[width=0.8\textwidth]{../../../figures/network/hybrid.ps}
\includegraphics[width=0.8\textwidth]{network/hybrid.ps}
\caption{Hybrid WR/IEEE1588 network. White Rabbit nodes work
transparently with PTP nodes. WR ordinary clock 3 is more accurately
synchronized to the grandmaster than WR ordinary clock 2, which
......@@ -590,7 +592,7 @@ the standard PTP protocol will be used for synchronization.
\begin{figure}[ht!]
\centering
% \vspace{-1.3cm}
\includegraphics[width=0.99\textwidth]{../../../figures/protocol/wrptpMSGs_1.ps}
\includegraphics[width=0.99\textwidth]{protocol/wrptpMSGs_1.ps}
\caption{Simplified overview of the message flow in WRPTP.}
\label{fig:wrptpMSGs}
\end{figure}
......@@ -1069,7 +1071,7 @@ backupParentDS data set.
\begin{figure}[ht!]
\centering
\includegraphics[width=0.85\textwidth]{../../../figures/protocol/SDA.ps}
\includegraphics[width=0.85\textwidth]{protocol/SDA.ps}
\caption{Modified State Decision Algorithm (modifications in red).}
\label{fig:modifiedSDA}
\end{figure}
......@@ -1520,7 +1522,7 @@ WR Master and WR Slave.
\begin{figure}[ht!]
\centering
\includegraphics[width=0.85\textwidth]{../../../figures/protocol/modifiedPtpFSM.ps}
\includegraphics[width=0.85\textwidth]{protocol/modifiedPtpFSM.ps}
\caption{Modified PTP Finite State Machine.}
\label{fig:modifiedPtpFSM}
\end{figure}
......@@ -1676,7 +1678,7 @@ WR\_LINK\_ON & Upon entering this state, the WR Master sends the WR\_LINK
\begin{figure}[ht!]
\centering
% \vspace{-1.3cm}
\includegraphics[width=1.00\textwidth]{../../../figures/protocol/wrFSM.eps}
\includegraphics[width=1.00\textwidth]{protocol/wrFSM.eps}
\caption{White Rabbit state machine.}
\label{fig:wrFSM}
\end{figure}
......@@ -2020,7 +2022,7 @@ WRPTP shall implement the following implementation-specific features:
\begin{figure}[ht!]
\centering
\includegraphics[width=0.8\textwidth]{../../../figures/protocol/ptpFSM.ps}
\includegraphics[width=0.8\textwidth]{protocol/ptpFSM.ps}
\caption{State machine for a full implementation of PTP (Figure 23, IEEE1588).}
\label{fig:ptpFSM}
\end{figure}
......@@ -2181,7 +2183,7 @@ The citation is approved by the author.
\begin{figure}[ht!]
\centering
% \vspace{-1.3cm}
\includegraphics[width=1.0\textwidth]{../../../figures/protocol/wrMSGsExchangeFlow.ps}
\includegraphics[width=1.0\textwidth]{protocol/wrMSGsExchangeFlow.ps}
\caption{Typical flow of events (no exceptions) during WR Link Setup.}
\label{fig:wrFSMcommun}
\end{figure}
......@@ -2194,7 +2196,7 @@ The citation is approved by the author.
\begin{figure}[ht!]
\centering
% \vspace{-1.3cm}
\includegraphics[width=1.0\textwidth]{../../../figures/protocol/ptpAndWrFSMs.ps}
\includegraphics[width=1.0\textwidth]{protocol/ptpAndWrFSMs.ps}
\caption{PTP and WR FSMs from POWER ON use case}
\label{fig:wrFSMcommun}
\end{figure}
......
......@@ -2,7 +2,7 @@
\label{appH}
\begin{center}
\includegraphics[scale=0.30]{../../../../figures/robustness/switchRouting.ps}
\includegraphics[scale=0.30]{robustness/switchRouting.ps}
\captionof{figure}{WR Switch routing using Swcore and RTU (not to
scale).}
\label{fig:swRouting}
......
......@@ -80,7 +80,7 @@ Backup & Designated \\ \hline
\end{table}
\begin{center}
\includegraphics[scale=0.20]{../../../../figures/robustness/wrRSTP.ps}
\includegraphics[scale=0.20]{robustness/wrRSTP.ps}
\captionof{figure}{WR RSTP for HP Traffic}
\label{fig:wrRSTP}
\end{center}
......@@ -13,7 +13,7 @@ Designated Switched, which forwards packets from the LAN toward the root bridge,
and vice versa.
\begin{center}
\includegraphics[scale=0.20 ]{../../../../figures/robustness/network_beginning.ps}
\includegraphics[scale=0.20 ]{robustness/network_beginning.ps}
\captionof{figure}{Redundant Network with Loops}
\label{fig:redunt_net}
\end{center}
......@@ -53,7 +53,7 @@ Alternate or Backup Port.
\begin{center}
\includegraphics[scale=0.20 ]{../../../../figures/robustness/network_spanning.ps}
\includegraphics[scale=0.20 ]{robustness/network_spanning.ps}
\captionof{figure}{Free-Loops Network}
\label{fig:free_loops}
\end{center}
......@@ -92,7 +92,7 @@ Designated Switched, which forwards packets from the LAN toward the root bridge,
and vice versa.
\begin{center}
\includegraphics[scale=0.20 ]{../../../../figures/robustness/network_beginning.ps}
\includegraphics[scale=0.20 ]{robustness/network_beginning.ps}
\captionof{figure}{Redundant Network with Loops}
\label{fig:redunt_net}
\end{center}
......@@ -132,7 +132,7 @@ Alternate or Backup Port.
\begin{center}
\includegraphics[scale=0.20 ]{../../../../figures/robustness/network_spanning.ps}
\includegraphics[scale=0.20 ]{robustness/network_spanning.ps}
\captionof{figure}{Free-Loops Network}
\label{fig:free_loops}
\end{center}
......@@ -219,7 +219,7 @@ out its ports. Though not strictly necessary in this case, they cause no ill
effects.
\begin{center}
\includegraphics[scale=0.70 ]{../../../../figures/robustness/dual_link.ps}
\includegraphics[scale=0.70 ]{robustness/dual_link.ps}
\captionof{figure}{Convergence Dual Link Topology}
\label{fig:idual_link}
\end{center}
......@@ -239,7 +239,7 @@ bounces back and goes till C to adapt to the new information and will declare
the designated port as root port.
\begin{center}
\includegraphics[scale=0.70 ]{../../../../figures/robustness/indirect_change_explamation.ps}
\includegraphics[scale=0.70 ]{robustness/indirect_change_explamation.ps}
\captionof{figure}{Convergence Indirect Change of Topology}
\label{fig:indirect_change}
\end{center}
......@@ -247,44 +247,44 @@ the designated port as root port.
\section{White Rabbit RSTP Use Cases}
\begin{center}
\includegraphics[scale=0.40]{../../../../figures/robustness/WRRSTPforHP.ps}
\includegraphics[scale=0.40]{robustness/WRRSTPforHP.ps}
\captionof{figure}{Some topology of the network and the bit we are
considering.}
\label{fig:WRRSTPforHP}
\end{center}
\begin{center}
\includegraphics[scale=0.40]{../../../../figures/robustness/WRRSTPforHP2.ps}
\includegraphics[scale=0.40]{robustness/WRRSTPforHP2.ps}
\captionof{figure}{The considered fragment of the network.}
\label{fig:WRRSTPforHP2}
\end{center}
\begin{center}
\includegraphics[scale=0.40]{../../../../figures/robustness/WRRSTPcase1.ps}
\includegraphics[scale=0.40]{robustness/WRRSTPcase1.ps}
\captionof{figure}{Link failure Use Case.}
\label{fig:WRRSTPcase1}
\end{center}
\begin{center}
\includegraphics[scale=0.40]{../../../../figures/robustness/WRRSTPcase2.ps}
\includegraphics[scale=0.40]{robustness/WRRSTPcase2.ps}
\captionof{figure}{Switch failure Use Case.}
\label{fig:WRRSTPcase2}
\end{center}
\begin{center}
\includegraphics[scale=0.40]{../../../../figures/robustness/WRRSTPcase3.ps}
\includegraphics[scale=0.40]{robustness/WRRSTPcase3.ps}
\captionof{figure}{Link failure Use Case.}
\label{fig:WRRSTPcase3}
\end{center}
\begin{center}
\includegraphics[scale=0.40]{../../../../figures/robustness/WRRSTPcase4.ps}
\includegraphics[scale=0.40]{robustness/WRRSTPcase4.ps}
\captionof{figure}{Failure of the switch connected to Data Master Node
(assuming flawless switching to backup Data Master.}
\label{fig:WRRSTPcase4}
\end{center}
\begin{center}
\includegraphics[scale=0.40]{../../../../figures/robustness/WRRSTPcase5.ps}
\includegraphics[scale=0.40]{robustness/WRRSTPcase5.ps}
\captionof{figure}{Link Failure between switches connected to
Master Node and backup Master Node}
\label{fig:WRRSTPcase5}
......
......@@ -254,7 +254,7 @@ it is necessary to multiply the received vector of $n$ block code by the $n \tim
\subsection{WR FEC Graps in CERN Network}
\begin{center}
\includegraphics[scale=0.60]{../../../../figures/robustness/P_error_control_msg_CERN.ps}
\includegraphics[scale=0.60]{robustness/P_error_control_msg_CERN.ps}
\captionof{figure}{Probability of Losing a Control Message}
\label{fig:wrRSTPtopologies}
\end{center}
......@@ -263,7 +263,7 @@ The Figure ~\ref{fig:wrRSTPtopologies} compares the FEC scheme proposed with a s
\begin{center}
\includegraphics[scale=0.60]{../../../../figures/robustness/overhead_cern.ps}
\includegraphics[scale=0.60]{robustness/overhead_cern.ps}
\captionof{figure}{Overhead introduced by the WR FEC Scheme}
\label{fig:wrRSTPtopologies}
\end{center}
......@@ -274,7 +274,7 @@ The Figure ~\ref{fig:wrRSTPtopologies} compares the FEC scheme proposed with a s
\begin{center}
\includegraphics[scale=0.60]{../../../../figures/robustness/P_error_control_msg_GSI.ps}
\includegraphics[scale=0.60]{robustness/P_error_control_msg_GSI.ps}
\captionof{figure}{Probability of Losing a Control Message}
\label{fig:wrRSTPtopologies}
\end{center}
......@@ -283,7 +283,7 @@ The Figure ~\ref{fig:wrRSTPtopologies} compares the FEC scheme proposed with a s
The Figure ~\ref{fig:wrRSTPtopologies} compares the FEC scheme proposed with a simple repetition code.
\begin{center}
\includegraphics[scale=0.60]{../../../../figures/robustness/overhead_gsi.ps}
\includegraphics[scale=0.60]{robustness/overhead_gsi.ps}
\captionof{figure}{Overhead introduced by the WR FEC Scheme}
\label{fig:wrRSTPtopologies}
\end{center}
......
......@@ -42,7 +42,7 @@ implementation of WR Switches and suggest improvements to help achieve the
demanding requirements.
\begin{center}
\includegraphics[scale=0.30]{../../../../figures/robustness/switchRouting.ps}
\includegraphics[scale=0.30]{robustness/switchRouting.ps}
\captionof{figure}{WR Switch routing using Swcore and RTU (not to
scale).}
\label{fig:swRouting}
......@@ -70,7 +70,7 @@ minimum level. The same applies to the rest of CoS.
\begin{figure}[!ht]
\centering
\includegraphics[scale=0.30]{../../../../figures/robustness/VLAN_Tag_GigaPeek.ps}
\includegraphics[scale=0.30]{robustness/VLAN_Tag_GigaPeek.ps}
\caption{VLAN Tags}
\label{fig:VLAN_Tag}
\end{figure}
......@@ -181,7 +181,7 @@ of \HP\ Packages}& \textbf{Transmission Time of \HP\ Package}\\ \hline
\end{table}
\begin{center}
\includegraphics[scale=0.35]{../../../../figures/robustness/CMdelayStandard.ps}
\includegraphics[scale=0.35]{robustness/CMdelayStandard.ps}
\captionof{figure}{Delivery Delay of \ControlMessage\ (not to scale),
for description how the numbers were obtained, see Appendix~\ref{appH}.}
\label{fig:CMdelayStandard}
......@@ -275,7 +275,7 @@ called
\StandardPriority\ Packages (\SP\ Packages).
\begin{center}
\includegraphics[scale=0.30]{../../../../figures/robustness/SWhpRouting.ps}
\includegraphics[scale=0.30]{robustness/SWhpRouting.ps}
\captionof{figure}{Difference between \HP\ and \SP\ Routing (not to
scale).}
\label{fig:swhprouting}
......@@ -329,7 +329,7 @@ Master, thus they have precedence over \HP\ Packages received from downlink
port.
\begin{center}
\includegraphics[scale=0.30]{../../../../figures/robustness/hpRouting.ps}
\includegraphics[scale=0.30]{robustness/hpRouting.ps}
\captionof{figure}{Algorithm for routing \HP\ Traffic.}
\label{fig:timePaths}
\end{center}
......@@ -360,7 +360,7 @@ Delivery Delay}}\\
\begin{center}
\includegraphics[scale=0.30]{../../../../figures/robustness/CMdelayHP.ps}
\includegraphics[scale=0.30]{robustness/CMdelayHP.ps}
\captionof{figure}{Delivery Delay of \ControlMessage\ using \HP\
Bypass.}
\label{fig:CMdelayHP}
......
......@@ -57,7 +57,7 @@ mentioned before, WR Timing Slave Switch can be connected to up to two links
to up to two WR Timing Master Switches.
\begin{center}
\includegraphics[scale=0.30]{../../../../figures/robustness/timePaths.ps}
\includegraphics[scale=0.30]{robustness/timePaths.ps}
\captionof{figure}{Possible Timing Paths between WR Switches}
\label{fig:timePaths}
\end{center}
......@@ -75,7 +75,7 @@ White Rabbit network will work normally without redundancy
\begin{center}
\includegraphics[scale=0.20]{../../../../figures/robustness/layer1redundancy.ps}
\includegraphics[scale=0.20]{robustness/layer1redundancy.ps}
\captionof{figure}{Clock Path Redundancy}
\label{fig:clockRedundancy}
\end{center}
......
......@@ -170,7 +170,7 @@ The above restrictions greatly overlap with restrictions imposed by the
Timing Path Redundancy.
\begin{center}
\includegraphics[scale=0.30]{../../../../figures/robustness/wrRSTPtopologies.ps}
\includegraphics[scale=0.30]{robustness/wrRSTPtopologies.ps}
\captionof{figure}{Example of topologies including WR restrictions to
RSTP, highlighting connections between Backup Root Switch, Root Switch and Data
Master(s) Nodes.}
......@@ -302,7 +302,7 @@ bit was not received ("erased"). To overcome the loss of frames and erasures in
the frames, two concatenated FECs should be used.
\begin{center}
\includegraphics[scale=0.40]{../../../../figures/robustness/channels.ps}
\includegraphics[scale=0.40]{robustness/channels.ps}
\captionof{figure}{PEC and BEC in a WR Network}
\label{fig:wr_channels}
\end{center}
......@@ -371,7 +371,7 @@ For the shortest payload of an Ethernet frame, 46 bytes, the code will introduce
9 parity bits, and for the longest, 1500 bytes, 14 bits.
\begin{center}
\includegraphics[scale=0.50]{../../../../figures/robustness/hamming.ps}
\includegraphics[scale=0.50]{robustness/hamming.ps}
\captionof{figure}{Number of Parity-Check bits for a given Control Message }
\label{fig:Hamming}
\end{center}
......@@ -510,7 +510,7 @@ of the payload of the Ethernet frame a header with the following field:
\end{itemize}
\begin{center}
\includegraphics[scale=0.80]{../../../../figures/robustness/fec_header.ps}