Basic SCAN Information
If your problem is not mentioned in the Troubleshooting Tips below, please try our Field Reports page, which contains communications between the developers and the field.
Version # and
Symptom Potential Solution 5.0+
Turning Off Alarms
The attached files provide users with a reference on what thresholds they should use to turn OFF the alarms. The new file should be put the /data/fxa/tstorm directory, replacing the old default config file. You will also have to stop/start any D2Ds running for the alarms to be turned off. Also - this will not affect "new" alarms - it will only affect Rate of Change and Absolute Alarms.
5.0+ The SCAN Storm Cell Table is a volume scan behind the Storm Cell Identifications in the D2D. Clear the pane and make sure that, when you load SCAN into the D2D, it is the first item you load into the pane, thus all other products will time match to the SCAN products and not the other way around. 5.0+ I have set the Rate of Change (RoC) alarms threshold high in my personal configuration file, so the RoC alarms will not be issued, but the RoC alarms continue to be issued. After retrieving your personal configuration data and ingesting it into SCAN, click on the "Configurations" menu and select "D2D Display . . .". Then click on the "OK" button on the GUI that appears. 5.0+ The Rate of Change alarms keep going off and they are getting annoying. We'd like to turn them off. You can set the thresholds for the rate of Change alarms via the Storm Cell Table. Under the "Configurations" menu, select "Alarm Thresholds". This will bring up a GUI in which you can set the rate of change threshold for the alarms. If you provide a sufficiently large value, or a value impossible to attain (ie: 150% for Percent chance of Hail (poh)), the Rate of Change alarms should never be issued, the workstation won't beep at you, and the Alarm button on the Cell Table will not flash. 5.0 The SCAN loading window appears for an instant then disappears. This repeats over and over until the D2D frame is cleared. Check for an old configuration file: /awips/fxa/data/working.cdp. If it is the old format (or if you don't know for sure), remove it and re-start the D2D. You may also want to check the default configuration as well: $FXA_DATA/tstorm/default.cdp. If it is old (or if you don't know), remove it and re-start the D2D. 5.0 SCAN loads, and storm cell tracks are seen, but no storm cell IDs are visible on the D2D and the Storm Cell Table does not show up. Check for an old configuration file: /awips/fxa/data/working.cdp. If it is the old format (or if you don't know for sure), remove it and re-start the D2D. You may also want to check the default configuration as well: $FXA_DATA/tstorm/default.cdp. If it is old (or if you don't know), remove it and re-start the D2D. 5.0 After trying to load SCAN, a window pops up saying that the configuration is bad and that you should clear the D2D and re-load SCAN. Doing this doesn't fix the problem. Remove the configuration files: /awips/fxa/data/working.*dp and $FXA_DATA/tstorm/default.*dp. Re-start the D2D. If this does not fix the problem, please contact your troubleshooting authority. All The last frame (most current) in the D2D does not have storm cell identifiers, site locations, or storm tracks. None. If you loaded a radar product first (like base reflectivity), all subsequent products loaded into that pane will try to time match with the time of that radar product. Since SCAN processes data at the end of the volume scan, it will always lag one volume scan behind something like base reflectivity. All General troubleshooting tip Check the products on the RPS list (this can be accomplished through the Data Monitor). The following products should be on the RPS list for SCAN to run optimally:
Name Identifier Product
Importance to the
Composite Reflectivity: 1km CZ 37 Vital VIL VIL 57 Vital Base Reflectivity: 1km Z 19 Vital Storm Track and Identification STI 58 Suggested Mesocyclone M 60 Strongly Suggested Tornado Vortex Signature TVS 61 Strongly Suggested