INFORMATION SERIES                                                                       

Node Inventory & Updated "Hit" List

Updated 20210121
The MADAR Operations Center gets all sorts of automated daily and weekly reports for anomalies, and daily reports on dataProbes offline. Monday is the first day after a previous week of work on the MADAR Project and where we look at the data on the spreadsheets. There are three things on the Monday list that sometimes carry over into Tuesdays:

1) Conduct a weekly inventory of devices running and make necessary adjustments.
2) Analyze the reports of alerts that occurred since the last weekly inventory
3) Update the Project MATCH "Hit List" for MADAR Ops and MATCH UFO Officers in order for them to search for PSOI (Potential Sightings Of Interest)

Item number one is running the Active Nodes Report, which lists nodes in numerical order that are actually running. Using that report we update the Node Report database showing "running" or "x-nol" (not online) devices. Most x-nol's are either new devices not yet online or devices temporarily offline for various reasons. These x-nols range from COVID-related issues, devices in for repair, devices being re-positioned for better results, etc,. Knowing how many devices we have in the field, the active nodes are subtracted, giving us the number of devices offline. Then each day we also get a report on what nodes are still offline. The last inventory showed 115 in the field, with 94 online.

Each Sunday, prior to the start of the new week, we get an automated "MADAR Weekly Alert" printout, which lists all the alerts that were received the previous week. These are "raw" reports, and the number can vary each week from less than a hundred to more than 200 hits. The most recent MWA shows 134 nodes had been on some form of alert the previous week. The graphic below shows the top of the page. The link below it shows the full printout. Ops don't receive this version.

See complete list of hits for week ending 1/25/2021

These  raw hits are then processed.
1) As they occur, Node ops file a very short email or alibi report for known cases where the device was accidentally triggered. These are the first to be eliminated.
2) Any node which has more than 2 anomalies that week is considered as having excessive hits and the data is not tabulated. The data is retained on the server and can be accessed at any time, but the anomaly is not submitted to nor listed with NUFORC. A search at any time using the SightingSearch Tool will show the data for that event whether legitimate or not.
3) Field readings (column 5) in excess of 150 milligaus are considered problematic and not used.
4) Average Ambient readings (column 7) in excess of 950 milligaus are considered too high, and in some cases dangerously high and a possible fire hazard.
5) Alert times of 11:25 UTC in the fall/winter, or 10:25 UTC spring/summer are considered as computer errors of some kind, and occur about a half-dozen times each week. We're reminded of the Apollo 11 "501 and 502 alarms" that almost aborted the landing. Someone had bumped the radar switch and the LEM's computer was overloaded which caused the computer to reboot.

After these five steps of eliminations are taken, there remains a still sizeable group that remains to be processed further. 

Full version of the above

There were 11 anomalies that made it through steps 1-5.  Step six involves a Multi-Sensor Verification protocol requiring at least a 3-degree deviation in the compass heading (column 3).  This report is the Unevaluated MADAR Anomalies that goes out to Ops every Monday.

With 134 raw hits to begin with we are left with 5 candidates that are submitted for the NUFORC database.  However, the week prior had 17 candidates, the largest total in many weeks. Below is the MATCH Database printout that goes out on Tuesdays.

Normally it takes a day or two to get this far. By Wednesdays we have the MATCH Database entries inputted to NUFORC and the search for potential sightings of interests had already begun the day before.