1. Storm tracking and scan scheduling

2. Processing tree (in minutes) 05:00 Nimrod rainfall data produced 10:00 Nimrod data from BADC now at Chilbolton 10:30 Nimrod data cut to size on 400x400km grid 0:00 Met Office Radar network Volume scan 11:00 Tracking done. File with storm props and labels produced. 11:30 New scan procedure submitted to Chilbolton radar

3. Scan Scheduling

4. Prioritize storms that are already being tracked

5. Scan Scheduling Prioritize storms that are already being tracked

6. Scan Scheduling Issue when storms cross 0 azimuth line Prioritize storms that are already being tracked

7. Scan Scheduling Issue when storms cross 0 azimuth line Prioritize storms that are already being tracked

8. Scan Scheduling Issue when storms cross 0 azimuth line Prioritize storms that are already being tracked

9. Scan Scheduling Issue when storms cross 0 azimuth line Prioritize storms that are already being tracked

10. Scan Scheduling Issue when storms cross 0 azimuth line Prioritize storms that are already being tracked

11. Scan Scheduling Issue when storms cross 0 azimuth line Prioritize storms that are already being tracked

12. 64 Pulse pairs per ray Scan at 1deg/second 32 Pulse pairs per ray Scan at 2deg/second Rays are equal width (azimuth) 32 Pulse pairs = less data per ray (more noise?) 2deg/second = faster scanning Scan Options

13. 64 Pulse pairs per ray Scan at 0.2deg/second 32 Pulse pairs per ray Scan at 0.2deg/second Scan Options

14. Further work Automate process – John Nicol’s code waits for new Nimrod file to arrive at Chilbolton, then cuts it to size – Add “wait” command to tracking code that looks at list of filenames and waits for new Nimrod files to process – Link tracking and scan scheduler Test code at Chilbolton Test remote scanning display