this is for holding javascript data
Ewan D. Barr deleted scat5.tex
over 8 years ago
Commit id: f012641a54a951e548d7f7d1b4d38e5a801376db
deletions | additions
diff --git a/layout.md b/layout.md
index 0bc22c4..9525a89 100644
--- a/layout.md
+++ b/layout.md
...
scattering part2.tex
scattering part3.tex
figures/scattering_timescales2/scattering_timescales2.png
scat5.tex
scattering part4.tex
figures/limiting_dm_200ns_resolution/limiting_dm_200ns_resolution.png
scattering part5.tex
diff --git a/scat5.tex b/scat5.tex
deleted file mode 100644
index 5a8e8a8..0000000
--- a/scat5.tex
+++ /dev/null
...
All of the above discussion on scattering timescales would seem to suggest that the best-case scattering time could be taken into account when addressing requirements SKA1-SYS\_REQ-2961 and SKA1-SYS\_REQ-2962. However, there are reasons why we may wish to resolve the scattering tail of a given pulsar and so somewhat arbitrarily imposing a time resolution limit based on scattering is viewed as undesirable. This being said, we do not want requirements that imply extremely computationally expensive operational modes and as such a limit must be determined on the minimum time resolution as a function of DM. In the next section we will attempt to provide such a limit based on keeping the computational cost of coherent dedispersion to a reasonable level.