This document contains current planning information for THOR-North.

Table of Contents:

• 1.0 General Information
• 2.0 Data Ingest
• 3.0 Possible Auto-Nowcaster Set-ups
• 4.0 Satellite Algorithms
• 5.0 Miscellaneous Data Processing
• 6.0 Data Distribution
• 7.0 Issues

1.0 General Information

2.0 Data Ingest

3.0 Possible Auto-Nowcaster Set-ups

4.0 Satellite Algorithms

5.0 Miscellaneous Data Processing

6.0 Data Distribution

7.0 Issues

• How does MIT/LL receive Nexrad data and how will NCAR access it?
• What radars will we use for the Auto-Nowcast system?
• When will radar domains be combined in the Auto-Nowcast forecast?
• Where will Colide run? At SPC where boundaries are being entered or at MIT/LL?

If we run Colide at Lincoln, we will have a single instance of the Colide setup, but will have timing issues associated with receiving the human-inserted boundaries late. If we run Colide at SPC, we will also have to run Colide at RAP and have to synchronize somehow between the two versions.

• Will we use NSSL mosaics? What data quality processing is done upstream of the mosaic?
• For that matter, will MIT/LL data quality algorithms run on data prior to distribution to NCAR and, if so, which ones?
• Can we get MIT/LL motion vectors for use in algorithms?
• How do we access other datasets and what do we need?
• How many instances of CIDD do we need to plan? What are the issues with displaying "all the data, all the time"?
• What are the configurations for satellite, mesonet, sounding and model data?
• How much bandwidth do we need between sites?