awips2/cave/com.raytheon.viz.gfe/help/TextProductUserGuideNarrative/notes148.txt
root e2ecdcfe33 Initial revision of AWIPS2 11.9.0-7p5
Former-commit-id: a02aeb236c [formerly 9f19e3f712] [formerly a02aeb236c [formerly 9f19e3f712] [formerly 06a8b51d6d [formerly 64fa9254b946eae7e61bbc3f513b7c3696c4f54f]]]
Former-commit-id: 06a8b51d6d
Former-commit-id: 8e80217e59 [formerly 3360eb6c5f]
Former-commit-id: 377dcd10b9
2012-01-06 08:55:05 -06:00

2 lines
775 B
Text

Often at this point, the solution will be obvious. If not, we have several resources available to help us. First, see if you can find documentation describing the feature with which you are having a problem. Make sure that you are following all the set-up instructions. You can also put in print statements to further isolate the problem and give information about data values that may be problematic. Often this will lead to other methods which you can pull from the Infrastructure adding more print statements. When you do this, you'll feel like a detective hot on the trail of the culprit! You will also come to understand the logic of the code. If you still need assistance, formulate a listserver message complete with local file and print statements results.