Portability of Snapshots

Pegasus Interactive snapshots are portable between different locations. It means that if rule deck contains the include statements of additional rule deck files, then in case you create snapshots and copy it to different location from which old paths are not visible, Pegasus Interactive will generate results for given snapshot.

However, if rule deck contains reference to an additional data like GOLDEN GDSII/OASIS files, you will need to use environment variable PegasusInt_Data to make snapshot portable between different location. This is because Pegasus Interactive snapshot stores absolute paths which may be not visible from other locations.

Example:

> setenv Pegasus_DK /usr/dk/Pegasus_data

Rule deck contains line:

layout_path $Pegasus_DK/GOLDEN_GDS/golden1.gds GOLDEN;

layout_path $Pegasus_DK/GOLDEN_GDS/golden2.gds GOLDEN;

In the Pegasus Interactive snapshot these lines will be stored as:

layout_path /usr/dk/Pegasus_data/GOLDEN_GDS/golden1.gds

layout_path /usr/dk/Pegasus_data/GOLDEN_GDS/golden2.gds

Thus, if path /usr/dk/Pegasus_data/GOLDEN_GDS/ is not visible from end-user location, Pegasus Interactive will issue an error and will not generate any results.

To make snapshot portable, perform the following steps:

1. User, who generates snapshot should set:
   1. setenv PegasusInt_Data /usr/dk/Pegasus_data
   2. Generate snapshot. Paths to golden GDS files will be stored as:
      

      ${PegasusInt_Data}/GOLDEN_GDS/golden1.gds.

      ${PegasusInt_Data}/GOLDEN_GDS/golden2.gds.

2. End-user:
   1. Install design kit in local directory. For example: /usr/user/Pegasus_data
   2. setenv PegasusInt_Data /usr/user/Pegasus_data
   3. Run Pegasus Interactive.

Return to top