This section contains some troubleshooting tips and notes. It is meant to serve as suggested actions based on particular events. On some occasions, the events may be symptoms due to interaction from multiple problems, where the first thing to do will be to look for some root causes and then back up the system chain. The Test Plan is generally a useful tool to figure out what is to be the expected behavior.
It is always in your best interest to keep backup copies of configuration files and locally generated/changed scripts somewhere safe.
Solutions to potential MSAS problems.
It's possible that MSAS grids can become corrupted. In these cases, persistence grids need to be eliminated to give the system a clean start. To do so, "restart" through the LDAD Monitoring and Control System (see Section 8.1), or log into as2 and execute the following commands:
cd /awips/fxa/ldad/MSAS WFOA_MSAS_Restart
MSAS utilizes observation quality control information provided by the AWIPS Quality Control and Monitoring System (QCMS) (described in the D2D User's Manual, section 10). Occasionally, a bad observation will pass through the automated quality control checks provided by the QCMS, without being flagged as bad. In these cases, bullseyes may appear in the MSAS grids. To eliminate the bullseyes, add the offending station to the QCMS reject list (see Section 9.6; edit via the LDAD monitor - see Section 8.1.1), and follow the procedures in 12.1.1 to provide a clean start.
Good observations can sometimes be incorrectly labeled as bad by the QCMS, and therefore not be considered by the MSAS analyses. In these cases, the analyses may not contain the detail reflected in the observational database. To force the ingest of an observation, add the desired station to the QCMS accept list, via the LDAD Admin interface.
| |
|
|