this is for holding javascript data
Ewan D. Barr edited PeriodLimir.tex
over 8 years ago
Commit id: c7d38eaa57a47ef2bb1ace165a46ea8af13ed9e5
deletions | additions
diff --git a/PeriodLimir.tex b/PeriodLimir.tex
index 00d7498..e5f574f 100644
--- a/PeriodLimir.tex
+++ b/PeriodLimir.tex
...
By re-writing $t_{\rm res}$ in equation \ref{eqn:limiting_dm} in terms of spin period ($P_0$) and number of bins across the pulse profile ($n_{\rm bins}$), we can use equation \ref{eqn:limiting_dm} to now determine the maximum DM that must be supported for pulsar timing (specifically using coherent dedispersion) with
SKA1: SKA:
\begin{equation}
\label{eqn:limiting_dm_p}
t_{\rm res}(P_0) = \max
\left(200\ {\rm ns}, \left(t_{\rm min}, \frac{P_0}{\min (n_{\rm bins},2048)} \right).
\end{equation}
Here shorter periods mean larger computational and memory costs, but also lower maximum DMs due to the effect of scattering. As we move to higher periods, Here, $t_{\rm min}$ is the
computational minimum effective time resolution as described by requirements 2961 and
memory cost drop significantly 2962 (200~ns and
the maximum DM rises. 1.6~$\mu$s for SKA1\_Mid and SKA1\_Low, respectively).