By Fran Ridge


On Monday mornings I print out the current Active Nodes Report. It lists all the operating MADAR-III DataProbes in numerical node order. I also print out a LAN Report (List All Nodes) which gives us all the nodes and the settings for each node. I have a 3-ring binder that has spreadsheets for each node showing the last week's AlertStarts, if any. Using this as a guide I pull up on computer the current AlertStarts to see if anything was detected in the last 7 days. Operators sometimes know when they have caused MADAR to trigger and they send me a heads up email which is what we call a false target report. Whenever I flip the pages of the binder and also see a new AlertStart on my monitor I replace the spreadsheet with the new one and fill out a handprinted CG Form (Alert & Potential Sighting Correlation Guide). The guide lists the node number, the city & state, the date of the anomaly and the UTC (Universal Time Code). I have a chart on the wall that converts the UTC to local time. After going through all the nodes and filling out the CG Forms I pull up the Project MATCH database file and enter the new potential anomalies. Here is what a typical dataline looks like:

20190118 19:08  01 08 03 IN  Indianapolis 07 (19:08 is military local time or 7:08 PM. The UTC is hours minutes and seconds and in Coordinated Universal Time)

This database is where the weekly "hit list" is created and has many important analytical functions. I sort the files by date and UTC to see if anything happened somewhere else at the same time or to see if a device is triggered at the same time very often. This has exposed some system checks that we have taken note of. The file can also be sorted by Node so that we can see what nodes had the most hits. I also update a database called the Node Inventory Report. This shows what nodes are running, and if not, why. The why not can be: "stopped 12/16", "NOL" [not online], "shipped", "recalled", "being moved", "test node", etc. It also shows the current "limits" (trigger) settings on each and what version of sensor and software is being used.

We'll tell you about Tuesdays at MADAR HQ next month. 
Tuesday can be especially exciting.
MADAR now has 53 sites in 22 states and 5 foreign countries.

To see MADAR "hits" and potential monthly correlations one can go to the Project MATCH site at
Check out the full MADAR site or order a MADAR-III DataProbe at