this is for holding javascript data
Nick Konidaris added Trace.tex
about 9 years ago
Commit id: 95b4d45ed25a92e38a9387528eb7bcaf70ec8416
deletions | additions
diff --git a/Trace.tex b/Trace.tex
new file mode 100644
index 0000000..b7acd38
--- /dev/null
+++ b/Trace.tex
...
\subsection{Trace finder}
\subsubsection{Purpose}
This piece of code identifies the location of all the traces on the detector. The traces are identified via sextractor. For each trace store the bounding box, the ridgeline of the trace (Chebyshev polynomial),
\subsubsection{Input}
\begin{itemize}
\item dome.fits -- bias subtracted flat field field (float).
\item \verb{seg_dome.fits} -- segmentation map of flat field file (int).
\end{itemize}
\subsubsection{Output}
dome.fits\_segments.npy contains a list (length the number of segments) of dictionaries. Each dictionary contains information about the location of each segment.
\begin{itemize}
\item ok (boolean) -- The segment has more than 50 illuminated pixels
\item mean\_ys ([float]) -- The mean Y location of each pixel in the trace. It's length is usually between 200 to 270 pixels long.
\item xs ([float]) -- The X location of each pixel. It's length is the same as means. The ridgeline of the trace is constructed from the points in (xs, means).
\item trace\_sigma (float) -- The 1 $\sigma$ width of the trace. An in focus image should have a FWHM of about 2.5 pixels and thus sigma should be about 1.06.
\item \verb{coeffs_y} ([float]) -- A list of polynomial coefficients of order len(poly)-1 that is the best fit line to (xs, means). The bulk of this step's work is to derive poly.
\end{itemize}
