Once you have some product files and/or batch processing files defined, you can use some of the command-line keyword options of PaPCo . These options are there for ease of use and speeding up things, and to enable batch processing in the background.
Note: You still need to have access to a X-Windows display from your session. Even though no widgets are displayed, they are created but never mapped.
If you know the product file name you want to start PaPCo with, type
papco, PROD='product_filename'
at the IDL prompt once PaPCo has been compiled. PaPCo will start up and automatically load that product file. It is searched for in the last product file directory that PaPCo used (which is saved in the defaults file).
You are left inside an interactive PaPCo session.
If the keyword PROD is also used then the product is not only loaded, but also drawn automatically.
You are left inside an interactive PaPCo session.
If you know both the product name and the batch file name, you can run PaPCo ``quietly'' to process a batch of files without entering into an interactive session. Type
papco, PROD='product_filename', BATCH='batch_filename'
PaPCo will run without opening any X-windows but still provide diagnostic output in the IDL window. It will start up, load the product and then process it for the times defined in the batch file. It outputs postscript or gif files using the last set filename template. So, before running a batch make sure that you've set the output options you want from the printer window interactively.
Note: You still need to have access to a Windows display from your session. Even though no windows will be opened, PaPCo internally still creates widgets but does not realize them. For this IDL requires access to a windows device. In other words, you can't do this from a dumb terminal...
You never enter an interactive PaPCo session.
Used in conjunction with BATCH to also output to file if the modules used support that option.
Used to set up all the PaPCo common blocks and module environmental variables. Useful if you want to work in the ``PaPCo environment'' and have access to all the PaPCo routines and module routines for other purposes than running PaPCo .