## Troubleshooting and support

Version 2.32

Manual page for Troubleshooting_and_support(PL)

## Troubleshooting

- Be sure that the `pl` executable can be located via your command PATH.``
- Set and export `PLOTICUS_PREFABS` environment variable.`` It must contain the full path name of the directory (`./prefabs`) where prefab files reside. (Note: some installations hard-code this at build time, making this step unnecessary).``
- To run an initial quick test, go into the `pltestsuite` directory.`` If you're on a Unix/linux system with X11, just type: `pl stock.htm`
  Otherwise, create a GIF file by typing this: `pl -gif stock.htm`
  ..or create a PNG file by typing this: `pl -png stock.htm`
  You can run a series of examples by typing: `run_script_test`
  ...and: `run_prefabs_test`
- Verify that your data are being read and parsed correctly.`` For tab-delimited or comma-delimited data be sure that you have specified delim appropriately.`` Prefab users can verify the data by specifying `echodata=yes`.`` Script writers can use specify `showresults: yes` within `proc getdata`.``
- Use the -debug command line option.`` If you're using direct CGI mode, there are some additional debugging tips.``
- If your script uses variables (etc.), try the -echo command line option to see the post-evaluation script source.``
- Be sure you know which version you are executing (you might have earlier ploticus versions on your system and not realize it).`` Use `pl -version` to print the ploticus version; use the unix command `which pl` to print the file that you are actually executing when you type `pl`.``
- Unix builds prior to 2.11 do not read native PC text files. This problem occurs if pl is compiled on a unix machine and you feed it native PC text files, either as scripts or data files. Symptoms may include truncated multi-line text items, or garbage characters appearing at the end of text items.
- If you're attempting to create a large PNG/GIF/JPEG image (greater than 8" in either dimension) a sufficient pagesize must be specified, either on the command line or via proc page.`` Failure to do this results in the top or side of an image result being cut off or obliterated.``
- If viewing result images in a browser, remember that image caching is usually being done, and that you might not be seeing the most recently generated image, even when you Reload or Refresh.``
- If you're using a ploticus config file and want to confirm that it's being found and processed correctly, put the following line at the top of your config file: `option: -debug` .`` This is because the config file is processed before command line args are evaluated, so a `-debug` on the command line won't take effect in time.`` (Note: this trick doesn't work if you're using direct CGI mode)
- Use proc print or #write to print out variable contents.`` Use #exit to stop script execution prematurely, so that you can "step thru" your script.``
- Check to be sure you aren't exceeding one of the program limitations

## Support

Please follow all of the steps listed below when sending a support request.`` Requests that are incomprehensible or incomplete will be given lowest priority.
1. First, make a fair effort towards learning the tool and solving the problem yourself.. You should know your way around the ploticus documentation and examples.`` Be sure to follow the troubleshooting procedures from this page (and the CGI page if appropriate).``
2. Include a stripped-down self-contained example that exhibits the problem. Often the first thing I do is attempt to reproduce the problem here. Isolate the problem to the least amount of code possible, but send enough data that I can generate real results. Describe the problem succinctly and clearly. If you make it easy for me to understand I'll tend to address it sooner.``
3. Use the -debug option .. and send the diagnostic results
4. Indicate computing platform (Red Hat 7.2? Solaris 8? NT 4.0?)
5. Indicate the exact pl command you used and describe exactly how you invoked pl (command line? CGI?) If you use a config file please attach this as well.``
6. Double check to be sure everything is correct. Did you attach the correct script and data set? Did you describe the problem clearly and succinctly?``
Send support requests to the ploticus news group or to me at `stevegrubb at gmail dot com`
Much of the incremental improvement in this package has been due to the careful reports that have been sent in by attentive users. Thanks!``

Steve Grubb is the author of ploticus.

If you have interesting examples or web sites that use ploticus, please send the URLs or script files.``
data display engine
Copyright Steve Grubb

Markup created by unroff 1.0, `` `` August 23, 2005.