3.3 papco_startup.pro

This is the main PaPCo startup file. You should not need to edit this file.

This file is written as an IDL batch file, which itself calls a series of batch files described below.

3.3.1 papco_set_variables.pro

This batch file is called from papco_startup.pro and sets up all the IDL search paths and environmental variables needed by the PaPCo core (excluding modules).

NB!! YOU WILL NEED TO EDIT THIS FILE to set the correct paths to your papco_XX and papco_user_XX directories.

   
3.3.2 papco_include_modules.pro

This batch file is called from papco_startup.pro and expands the IDL search path to include the modules selected. You should never need to edit this file, as it is automatically written by the papco_configure widget (see Section 3.4).

This file will always reflect the last state of PaPCo, containing all the paths to modules last chosen.

The distribution comes without this file. It will be created the first time you configure PaPCo when you exit the papco_configure widget.

   
3.3.3 papco_include_addins.pro

This batch file is called from papco_startup.pro and is an empty batch file included to enable the user to add in any initialization needed for further add-in IDL applications called from PaPCo.

You should never need to edit this file, as it can be edited through the papco_configure widget (see Section 3.4).

Typically you would include one line each for the batch file which ``adds in'' your application, eg:

@my_IDL_application.pro

The batch file my_IDL_application.pro typically expands the IDL search path to point to where your applications .pro files reside, and then compiles all routines needed.

Such add-ins are considered advanced PaPCo and should not be attempted by the casual user.

Often this add-in facility can be used to compile other code in the PaPCo environment, even if one does not intend to use PaPCo itself. This is useful if you want to make use of PaPCo and PaPCo modules routines for other applications!

   
3.3.4 papco_restore.pro and papco_compile.pro

These batch files are called from papco_startup.pro. Which one is called is determined by the papco_setup batch file (see Section 3.4).

3.3.4.1 papco_compile.pro

This batch file compiles PaPCo core and module procedures and functions, which can take some time. It has to be called each time you modify any procedure in PaPCo core (which you shouldn't) or any of the modules (which you may), or if you setup PaPCo with a new set of modules.

Here the batch file papco_init is called, which compiles (.run) all the procedures and functions needed by PaPCo core. It resides in the PaPCo core directory papco_XX\papco.

Before compiling the procedures needed for all chosen modules, the routine find_modules is called. This routine searches the IDL search path for all the initialization files contained in each module directory. All these init file paths are written to the batch file papco_add_init.pro in the users papco_user_XX directory, which is then executed.

3.3.4.2 papco_restore.pro

This batch file restores a previously saved set of procedures and functions from an IDL saveset file. This file of course has to exist for this: It is made when you exit PaPCo using the ``Save&Done'' button, which writes a file papco_routines.save to your papco_user_XX directory.

This startup mode is exceedingly quick, and should be used whenever you work with a static PaPCo setup. Using this saveset file also allows you to run a given PaPCo setup from an IDL ``runtime'' license (which is a lot cheaper than the full IDL license).

Here previously saved procedures and functions are restored utilizing the IDL save/restore procedures. The routine find_modules needs to be called since it also generates a common block of module names needed by the PaPCo main routine.