Storm tracking andscan scheduling

Processing tree (in minutes)

05:00 Nimrodrainfall dataproduced

10:00 Nimrod datafrom BADC nowat Chilbolton

10:30 Nimrod datacut to size on400x400km grid

0:00 Met Office Radar networkVolume scan11:00 Tracking done.

File with storm propsand labels produced.

11:30 New scanprocedure submittedto Chilbolton radar

Scan Scheduling

Scan Scheduling

Prioritize storms that are already beingtracked

Scan Scheduling

Prioritize storms that are already beingtracked

Scan Scheduling

Issue when storms cross 0 azimuth line

Prioritize storms that are already beingtracked

Scan Scheduling

Issue when storms cross 0 azimuth line

Prioritize storms that are already beingtracked

Scan Scheduling

Issue when storms cross 0 azimuth line

Prioritize storms that are already beingtracked

Scan Scheduling

Issue when storms cross 0 azimuth line

Prioritize storms that are already beingtracked

Scan Scheduling

Issue when storms cross 0 azimuth line

Prioritize storms that are already beingtracked

Scan Scheduling

Issue when storms cross 0 azimuth line

Prioritize storms that are already beingtracked

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

64 Pulse pairs per ray Scan at 0.2deg/second

32 Pulse pairs per ray Scan at 0.2deg/second

Scan Options

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