Directory hierarchy

 

The PIPS main directory hierarchy is mainly organized with the following concepts [8]:

Production:

contains the last coherent version of the PIPS software (Bin, Runtime), documentation (Doc, Html), examples of validation (Validation) and sources (Src). The production directory is pointed by $PIPS_ROOT;

Development

(PIPS_DIR/Development) is used to develop all the pieces of PIPS . By default, a part of PIPS in development is tested with all the other parts from the Production directory to avoid as much as possible the interactions between concurrent developments of different parts at the same time ($PIPS_DEVEDIR). Important directories of Development are Libs (the internal parts of PIPS , such as each phase ), Passes (the various PIPS executable with the different user interfaces pips , tpips and wpips ), Documentation (the documentation itself of course but also many configuration files), Runtimes (support for HPF , message passing and graphics) and Scripts. Installing a part of PIPS (with a classical GNU make install) is done in fact by copying the needed files and directory in the ad hoc directories of Production;

For portability purpose, an architectural hierarchy à la PVM has been reused in PIPS with the $PIPS_ARCH variable to compile and store different binary architectures.