this is for holding javascript data
Ewan D. Barr edited considerations.tex
over 8 years ago
Commit id: eab4bfd7b02f10f64d7f51c6fcd6e237d6610a02
deletions | additions
diff --git a/considerations.tex b/considerations.tex
index 5137cd7..df7a01b 100644
--- a/considerations.tex
+++ b/considerations.tex
...
\section{Implementation Considerations} \section{DM Limit Requirements}
Ideally the upper DM limit for each band should be defined by the top frequency of that band. While practically speaking this is feasible for SKA1\_Mid, the large amount of memory required to do this across the whole SKA1\_Low band ($>100$ GB) is restrictive and would have unnecessary cost implications for pulsar timing with the SKA. We therefore suggest that for SKA1\_Low, the maximum DM required to be supported should be defined by equations \ref{eqn:limiting_dm} and \ref{eqn:limiting_dm_p} with the value of $\nu$ set by the bottom frequency of the observing band. For SKA1\_Mid we suggest that the maximum DM to be supported by each frequency band is given by equations \ref{eqn:limiting_dm} and \ref{eqn:limiting_dm_p} with the value of $\nu$ set by the highest frequency in the band. For both SKA1\_Low and SKA1\_Mid, the value of $n_{\rm bins}$ will be user defined on a per-observation basis. This leads to two new requirements for pulsar timing with SKA1: