Customizing the ADS Environment

The Advanced Design System suite of tools uses a number of configuration files. The files contain definitions for configuration variables and environment variables.

Customizing Environment Variables

Environment variables are usually initialized in a shell start-up file such as .cshrc (C-shell) or .profile (Bourne-shell) in your home directory. The following table describes the most common environment variables used by the Advanced Design System. On the PC, these environment variables get set automatically at installation.

Name	Default Value	Description
HPEESOF_DIR	/hpeesof	The location where the software has been installed (also called the root location).
AGILEESOFD_LICENSE_FILE	$HPEESOF_DIR/licenses/license.lic	Specifies the location of the FLEXlm security license files.
EESOF_64BIT	Not set by default.	Specifies whether 64-bit systems use the default 64-bit simulators or 32-bit simulators. Set EESOF_64BIT=0 to force 64-bit systems to use the 32-bit simulators.
PRINTER	lpr	Specifies the printer used by the hpeedit program.
EESOF_BROWSER	Not set by default. Example setting: EESOF_BROWSER=/usr/bin/firefox	Specifies the browser to use for viewing online help.
CDS_INST_DIR	Not set by default. The Connection Manager Client does not use the value. The presence or absence of this variable determines which online help to display.	Specifies whether the Connection Manager Client uses ADS or RFDE online help. If CDS_INST_DIR is not set, ADS online help is used. If CDS_INST_DIR is set, RFDE online help is used.

The environment variable HPEESOF_DIR is used extensively throughout Advanced Design System. It does not need to be set if Advanced Design System has been installed in the directory /hpeesof.

Customizing Configuration Variables

The default values of the configuration variables should get you up and running, but they can be customized to better reflect your work environment. By default, the program searches for these configuration files in the following order, and uses the first one found:

Your current project directory
Define configuration variables here that apply only to this project.
Your personal directory = $HOME/hpeesof/config
Define configuration variables here that apply to all your projects.

Note
On the PC, %HOME% represents the path you specified as the Home Folder during installation (by default, C:\users\default)

Your site's customized site directory $HPEESOF_DIR/custom/config
Define configuration variables here that apply to all projects of all users on a site-wide basis. Configuration variables defined here will not be overwritten by installation of subsequent program patches or updates.
The ADS installation directory $HPEESOF_DIR/config
Define the default installed configuration variables here that apply to all projects of all users. Configuration variables should not be customized here.

Each of the individual Advanced Design System tools has its own configuration file. The supplied configuration files can be found in the directory $HPEESOF_DIR/config (where $HPEESOF_DIR represents the complete installation path). The filenames for each of the tools are shown in the following table.

Product/Tool	Filename
Design Environment	de_sim.cfg
Digital Filter	dfilter.cfg
Digital Synthesis	dsynthesis.cfg
Data Displays	hpeesofdds.cfg
Data Sets	hpeesofdss.cfg
Instrument Server	hpeesofinstrio.cfg
Momentum	momentum.cfg
Browser (Vendor and component parts)	hpeesofbrowser.cfg
Simulation and Synthesis Message Window	hpeesofsess.cfg
Layered A.P.I.	eeapi.cfg
Ptolemy models and MATLAB	hpads.cfg
Colors	hpeecolor.cfg
Fill patterns	hpeefill.cfg
GUI search paths	hpeesof.cfg
Online help system	hpeesofhelp.cfg
AEL search paths	hpeesofsim.cfg
Library translator	hplibtrans.cfg
Ptolemy	hptolemy.cfg
SMG search path	smg_ui.cfg
Spice to IFF	spctoiff.cfg
Spice translator	spice_xlator.cfg
LineCalc	linecalc.cfg

Configuration File Format

Configuration variables are defined using standard assignment syntax:

<variable>=<value>

where variable is the configuration variable name and value is the string that is assigned to the variable. This value can be a directory, search path, numeric value, or other value defined by the program. For example, the location of the preferences could be set by:

PREFERENCES_DIR={$HPEESOF_DIR}/de/defaults

where $HPEESOF_DIR is an environment variable representing the complete installation path.

Note the following details about file format, illustrated in the accompanying example:

Any line starting with # is a comment line and is ignored
Blank lines are ignored
Blank spaces to the left or right of the equal sign are ignored
Empty assignments are acceptable (as shown by env_var_2)

Example

#
# This is a sample configuration file
#
env_var_1 = first_value
env_var_1a = value-1a
#
env_var_2 =
env_var_3 = 17
env_var_4 = $SYSTEM/%HOME/ex4
env_var_4a = {$HPEESOF_DIR}/de/defaults/{%env_var_1a}.ex4a

References to environment variables $name and ADS configuration variables %name can appear in any order; they are resolved inside each ADS program. A reference to an environment variable or configuration variable name may be enclosed in braces { } when their use is not followed by a punctuation character. The braces are not included in an expanded value.

Configuration Variable Description

ADS configuration variables are identified by a case-insensitive string of 1 to 31 alphanumeric characters (an underscore is allowed). Variables that are longer than 31 characters are automatically truncated when the configuration file is read. When a variable is set from a configuration file, the line

<variable>=<value>

is parsed and variable is set to the value.

A configuration variable can contain a reference. A reference may be enclosed in braces and the text is preceded by either a $ or % (see ADS Configuration Variables). For example,

PREFERENCES_DIR={$HPEESOF_DIR}/de/defaults

assigns the string $HPEESOF_DIR/de/defaults to the configuration variable PREFERENCES_DIR, and $HPEESOF_DIR is defined in a start-up file.

ADS Configuration Variables

Configuration variable	Description
$name	The configuration variable is replaced by the text string assigned to name in the environment.
%name	The configuration variable is replaced by the text string assigned to name in the ADS configuration file. Certain ADS variables have a pre-defined meaning in a given program. All of the special ADS configuration variables that are recognized are given in the shipped {$HPEESOF_DIR}/config/<app-name>.cfg file.

Most ADS configuration variables are assigned a single value. This text can represent a number, string, file, or path as in the following examples.

STATUS_DISP = 0
EESTATUS_LOG_FILE = Off
HPEESOF_KEY = $HPEESOF_DIR/licenses/hpeesof.key
PREFERENCES_DIR={$HPEESOF_DIR}/de/defaults

Note that when the file is outside of a project configuration, it is necessary to include the full path with the filename to ensure that the file is found.

Some ADS configuration variables accept a path assignment. A path is a list of one or more directories, where each directory is separated by a colon.

variable=directory:directory: ....

These variables can represent search paths or load paths, depending on the variable and the program. Ordering of the list is significant. When treated as a search path, the list is only scanned until the item needed is found. For loading, the entire list is sequentially examined with the last directory usually taking precedence.

The documentation for each specific variable indicates the type of value allowed. Some variables may have a limited type, such as a range of numbers or list of specific strings.

Configuration Variable Expansion

Configuration variable expansion refers to the process of replacing all references and variables that make up the configuration variable with their text equivalents until the complete value of the configuration variable is known. (There are no limits to the levels of referencing you can use.) Note that this expansion is done internally by the program; the file that contains the variable assignments is not modified.

For example, assume that the environment variable HPEESOF_DIR is set to /hpeesof/mysite and the following two lines exist in the file de_sim.cfg.

PROJECT3 = de
SYSTEM_CUSTOM_DE_SYMBOLS = {$HPEESOF_DIR}/custom/{%PROJECT3}/symbols

After expansion within hpeesof tool:

SYSTEM_CUSTOM_DE_SYMBOLS = /hpeesof/mysite/custom/de/symbols

As in the environment, you may redefine and add your own ADS variables in any ADS configuration files to help manage system- and user-specific configurations. However, a given ADS program only uses certain expanded ADS configuration variables, but the unexpanded value could contain any number of user-defined and/or ADS variables.

How a Configuration is Determined

Each configuration is distinguished by its name. Each named configuration contains all of the variables needed for describing that particular setup. At the topmost level is the configuration file named hpeesof.cfg, which is associated with all ADS programs. Other named configurations are associated with specific programs.

Each named configuration is determined by the location and content of any related configuration files. For example, the complete hpeesof configuration could consist of:

The file hpeesof.cfg, located in the install directory $HPEESOF_DIR/config
An edited copy of this same file, located in the customized site directory $HPEESOF_DIR/custom/config
An edited copy of this same file located under your home directory $HOME/hpeesof/config
An edited copy of this same file located in a particular project directory

As noted earlier, configurations in the user directory take precedence over the installation directory, and configurations in the project directory take precedence over the user directory. This is because the search order for configuration information is: project directory, user directory, site directory, and installation directory.

Note that variables in each successive file override any previously set value. You can even put two lines in the same configuration that assign values to the same variable, as in:

MY_VAR1 = entry_a
MY_VAR1 = entry_b

When expanded, MY_VAR1 will always have the value of entry_b.

The following table shows a list of named configurations used in the programs.

Named Configurations

Activity	Configuration
Design entry	hpeesof
Fill patterns	hpeefill
Online Help	hpeesofhelp
Colors	hpeecolor
Simulation	hpeesof de de_sim comms_ckt (Communications Design Suite only)
Status/Synthesis Messages	hpeesof eestatus
Data Displays	hpeesof eehelp hpeefill hpeecolor eegraph

Special Variables

There are two configuration files that have a different syntax than the others: hpeecolor and hpeefill. Their formats are presented here. Note that the naming convention and loading of system-wide, site-wide, home directory, and project-specific configurations still apply. Only the internal file format differs.

Color Definitions, hpeecolor.cfg

The design windows (Schematic and Layout), Data Display windows, and plotters use the colors defined in the hpeecolor configuration. By default, these colors are read from {$HPEESOF_DIR}/config/hpeecolor.cfg, but can be overridden at the site, user, or project level (any of which can have an hpeecolor file).

The hpeecolor file format differs from the variable=value syntax. Each line contains these major fields:

RGB color values
Color name
Plotter pen number

The syntax for each line is as follows:

<Red #> <Green #> <Blue #> : <Color name> : <Pen number>

The following example illustrates the format of a typical color definition file:

Colors are described in the first and/or second fields of this file. You can enter three RGB color values (in the range 0-255) in the first field and/or you can enter the X color name from the RGB color database (found in /usr/lib/X11/rgb.txt for Motif or /usr/openwin/lib/rgb.txt for Sun's Open Windows) in the second field. If both are entered, the RGB values take precedence, and the color name is ignored.

The last field specifies which pen number to use for hard-copy output when performing HPGL plotting. An entry in this field is required and pen numbers may be recycled and repeated.

By default, the current implementation uses shared server colors from the RGB color database and uses no privately allocated color cells for X Window displays. This is done to simplify the color specification and to promote sharing of colors. Sharing of color cells can only happen if two clients allocate read-only color cells with the same X color name or RGB values.

Important
On UNIX, we strongly recommend that you only use the names given in the RGB color database instead of explicit RGB values; on the PC, only RGB values are supported.

Because of differences in screen hardware, the same RGB values may generate different colors on different hardware. By using names from the color database, you are more likely to get colors close to the ones requested across different hardware platforms.

It is also important to note that values corresponding to color names are not fixed. Therefore, they may not be exactly the same across all platforms or correspond to an exact RGB value.

Note
Some platforms have limited color resources and some platforms may use non-shared colors, resulting in color exhaustion problems. When ADS programs run into these types of color problems, the solution is to reduce the number of requested colors until color conflicts stop occurring. As an example, truncating the list of colors in hpeecolor.cfg to 64 colors may be a good start.

An example hpeecolor configuration file is shown:

If the ADS configuration file cannot be found or the hpeesof configuration does not contain an HPEESOF_COLOR variable (which determines the location of the ADS color definition file), a set of ten basic default server colors are automatically loaded as follows:

1 = black	5 = cyan	9 = white
2 = red	6 = blue	10 = medium blue
3 = yellow	7 = magenta
4 = green	8 = gray

Fill Pattern Configuration, hpeefill.cfg

Besides colors, the design windows (Schematic and Layout), Data Display windows, and plotters also use the fill patterns defined by the hpeefill configuration. By default, these patterns are read from {$HPEESOF_DIR}/config/hpeefill.cfg, but can be overwritten at the site, user, or project level (any of which can have an hpeefill file).

The hpeefill file format differs from the variable=value syntax. Each line contains two major fields.

Path and filename of the fill pattern
HPGL/2-pattern-specification

The syntax for each line is as follows:

<Bitmap_file_location> : <Fill type> <Line spacing> <Angle>

where

Fill type-is the pattern inside an object's border
Line spacing-is the distance between the hatched lines in plotter units (where a plotter unit is typically 1/72-inch).
Angle-is the angle of hatch lines in the fill pattern, expressed in degrees (for fill type 3 or 4 only).

The following example illustrates the format of a typical fill pattern definition file:

Fill patterns use standard X-bitmap files that can be easily created with the X bitmap utility. The first field specifies the path to the X-bitmap file, which is used for pattern fills, while the remaining fields are the HPGL/2 fill pattern specification.

Fill type description	Fill type number
Solid bidirectional	1
Solid unidirectional	2
Hatched	3
Cross hatched	4

Note
Solid bidirectional fill is faster than solid unidirectional fill, but is not supported by all plotters.

An hpeefill configuration file is shown in the following example:

If the ADS configuration file cannot be found or the hpeesof configuration does not contain an HPEESOF_FILL variable (which determines the location of the ADS fill definition file), a single, unidirectional, solid fill pattern is automatically loaded.

Viewing Details of the Current Configuration

The Configuration Explorer enables you to search, view, save to file, and print the current settings of ADS configuration files. You can browse the configuration files in the following locations:

Installation directory
Site-wide customization directory
User directory
Current project

To launch the Configuration Explorer:

From the ADS Main window, choose Tools > Configuration Explorer.

To view the properties of a given file:

Select the desired configuration directory from the drop-down list.
Click the desired filename. The file location, size, date, and permissions are displayed in the Status pane, as well as the location of any additional files by that same name.

To access the pop-up menu:

Position the pointer over any filename and click right.

Use the uppermost group of commands to quickly expand and collapse the tree.

Use Load variables from selected file to explicitly load into memory changes you have made to a configuration file since launching ADS.

Use Refresh to view changes you have made to a configuration file since launching ADS.

To view the list of variables in a given file:

Click once on the plus sign (expand) in front of the filename to display the list.

To view the current setting of a given variable:

Click once on the variable name to display the value in the Status pane, or
Click once on the plus sign in front of the variable to display its value in the browser pane

To search for a specific variable name and/or value:

Select Variable in the Search pane.
Optionally, refine your search by selecting Variable Name and/or Variable Value.
Optionally, refine your search by selecting Exact Match.
Type the search string in the Search for field and click Search. The results are displayed in the Status pane.

To search for a specific filename:

Select File in the Search pane.
Optionally, refine your search by selecting Exact Match.
Type the search string in the Search for field and click Search. The results are displayed in the Status pane.

To retain the results of all listings and searches:

Select the Keep history option in the Status pane. Note that to retain the variable value listings, you must display the values in the Status pane, not the Browser pane. To clear the history click Clear.

To print the contents of the Status pane:

Click Print. The contents are sent to your default printer.

To save the contents of the Status panel to a file:

Click Save Status. A dialog box appears prompting you for a filename.
Change paths as desired, supply a filename, and click OK.

This information may be especially helpful when discussing configuration issues with Technical Support.

Typical Variables

The remaining variables use the variable=value syntax.

Note
The Design Kit variables are documented in the Design Kit Installation and Setup manual.

Variables in the File de.cfg, de_sim.cfg

A number of resources related to the user interface and simulation can be customized in the file de_sim.cfg. This file can be customized for individual projects, all projects, etc., as described in, Customizing Configuration Variables. You will find a default copy of this file, with a limited number of variables in it, in the following locations:

In your /hpeesof/config directory under $HOME (on UNIX) or c:\users\default (on PC, or whatever directory you chose instead during installation)
Every project directory you create

You can add to this file (or modify, if they currently exist in the file) all variables described in the table below.

Note
The variables described in the table are defined in either de.cfg or de_sim.cfg (under $ HPEESOF_DIR/config), however when you customize any of these variables, it must be done in de_sim.cfg. To minimize typing and ensure accuracy of the variable names, copy the variables you want to customize from one or both of these files to the appropriate de_sim.cfg file and modify them there .

Variable, description, and example	Value(s)
FILE_FORMAT Specifies the format for writing design files. Use ASCII for portability and upgrades; binary is faster and uses less disk space. Example: FILE_FORMAT = ascii	ascii binary
LAYERS_PATH Specifies the layer file search path. Example: LAYERS_PATH = ./:{$HPEESOF_DIR}/de/defaults	Path
PREFERENCES_PATH Specifies the preference file search path. Example: PREFERENCES_PATH = ./:{$HPEESOF_DIR}/de/defaults	Path
LOCAL_AEL Specifies the project-specific AEL files to be automatically loaded each time when a project is opened. It should be set only in the de_sim.cfg file located in the project directories. These AEL filenames may have absolute, relative, or no path specified, but since the files are generally located in the project directory, a relative path would be used beginning with a dot and slash (./). An AEL file that is already in the networks subdirectory will be automatically loaded. Any other AEL files that you would like included should be placed here. Example: LOCAL_AEL = my_file	Filenames (without extension) or Path
USER_AEL Specifies the user-specific AEL files to be automatically loaded once at startup. It should be set only in the de_sim.cfg file located in the user's personal customized directory $HOME/hpeesof/config. If you specify a path, rather than filenames, it cannot be a relative path; it must be an absolute path, or you can use an environment variable. A typical use would include $HOME to reference files in the user's home directory. Example: USER_AEL = $HOME/hpeesof/MyLibrary/ael/	Filenames (optional extension) or Path
USER_DSN_PATH Specifies the directory (or directories) separated by a colon (:) where user-specific design files are located. It should be set only in the de_sim.cfg file located in the user's home directory. This variable cannot specify a relative path; it must be an absolute path, or you can use an environment variable. A typical use would include $HOME to reference files in the user's home directory. Note: this variable should be used in conjunction with USER_AEL. Example: USER_DSN_PATH = $HOME/hpeesof/MyLibrary/designs/	Path
SITE_AEL Specifies the site-specific AEL files to be automatically loaded once at startup. It is typically set in the de_sim.cfg file located in $HPEESOF_DIR/custom/config. If you specify a path, rather than filenames, it cannot be a relative path; it must be an absolute path, or you can use an environment variable. Example: SITE_AEL = {$ADS_DESIGNS}/library1/ael/ Example: SITE_AEL = Q:\ads_designs\library1\ael\	Filenames (optional extension) or Path
SITE_DSN_PATH Specifies the directory (or directories) separated by a colon (:) where design files for site-wide use are located. It is typically set in the de_sim.cfg file located in $HPEESOF_DIR/custom/config. This variable cannot specify a relative path; it must be an absolute path, or you can use an environment variable. Note: this variable should be used in conjunction with SITE_AEL. Example: SITE_DSN_PATH = {$ADS_DESIGNS}/library1/designs/ Example: SITE_DSN_PATH = Q:\ads_designs\library1\designs\	Path
HPEESOF_LANGUAGE Specifies the language used by the PDE program. Example: HPEESOF_LANGUAGE = english	Language name
ENGLISH_MSG_EXT Specifies the language of the program messages. Example: english_MSG_EXT = eng	English = eng German = ger French = fra
ENGLISH_MSG_FONT Specifies the font supporting the selected local language. Example: ENGLISH_MSG_FONT = 9x15 bold	European = 9x15 Japanese = 8x16
PDE_MSG_FILE Specifies the full path to the PDE message directory file. Example: PDE_MSG_FILE = {$HPEESOF_DIR}/msgs/english/PDE/PDE.msg	Path
NETLIST_FILE_NAME Specifies the netlist filename. Example: NETLIST_FILE_NAME = netlist.log	Filename
EGSLIST_FILE_NAME Specifies the filename for the EGS translator option. Example: EGSLIST_FILE_NAME = ./egslist.log	Filename
EGS_OPTION_FILE: Specifies the path to the EGS translator option files. Example: EGS_OPTION FILE = ./:{$HPEESOF_DIR}/config	Path
GDSII_OPTION_FILE Specifies the path to the GDSII option files. Example: GDSII_OPTION_FILE = ./:{$HPEESOF_DIR}/config	Path
MASK_OPTION_FILE Specifies the path to the mask translator option files. Example: MASK_OPTION_FILE = ./:{$HPEESOF_DIR}/config	Path
IGES_OPTION_FILE Specifies the path to the IGES translator option files. Example: IGES_OPTION_FILE = ./:{$HPEESOF_DIR}/config	Path
SPICE_OPTION_FILE Specifies the search path for the Spice files. Example: SPICE_OPTION_FILE = ./:{HPEESOF_DIR}/config	Path
IFF_OPTION_FILE Specifies the search path for the IFF option files. Example: IFF_OPTION_FILE = ./:{HPEESOF_DIR}/config	Path
DIALOG_TIME_OUT Specifies the time before the copyright or information dialog box is automatically dismissed. Example: DIALOG_TIME_OUT = 10000	Time in milliseconds
BALLOON_HELP_TIMEOUT Time taken for balloon help to appear when icon is selected. Example: BALLOON_HELP_TIMEOUT = 600	Time in milliseconds
BALLOON_HELP_DISMISSAL_TIMEOUT Time taken for balloon help to disappear when icon is selected. Example: BALLOON_HELP_DISMISSAL_TIMEOUT = 2500	Time in milliseconds
BALLOON_HELP Sets whether balloon help exists or not. Example: BALLOON_HELP = TRUE	TRUE or FALSE
DOUBLE_CLICKS_TIME_OUT Specifies the time interval in which a double-click is registered. Example: DOUBLE_CLICKS_TIME_OUT = 200	Time in milliseconds
QUERY_PROCESS_STATUS Specifies how often PDE should query the child process status. Example: QUERY_PROCESS_STATUS =1	Time in seconds
MAX_PROCESS_READY_TIMEOUT Defines when PDE should quit waiting for the child process to be ready after it's spawned Example: MAX_PROCESS_READY_TIMEOUT = 300	Time in seconds
BOM_LIST Specifies the list of report types presented in the Bill of Materials dialog box. Example: BOM_LIST = Agilent EEsof (Agilent EEsof BOM format/de_bom	Report types
PARTS_LIST Specifies the list of report types presented in the Parts List dialog box. Example: PARTS_LIST = Agilent EEsof (Agilent EEsof PL format)/de_parts:Agilent EEsof (netlist format)/de_net	Report types
BOM_ITEM Specifies the spacing allocated for item name field in the Bill of Materials dialog box. Example: BOM_ITEM = 30	Integer
BOM_QTY Specifies the spacing allocated for quantity field in the Bill of Materials dialog box. Example: BOM_QTY = 7	Integer
BOM_DESC Specifies the spacing allocated for description field in the Bill of Materials dialog box. Example: BOM_DESC = 50	Integer
TEXT_EDITOR_PROGRAM_NAME Text editor Example: TEXT_EDITOR_PROGRAM_NAME = write.exe	Editor name
INVOKE_DDS_ON_BOOTUP Program Preference. Example: INVOKE_DDS_ON_BOOTUP = FALSE	TRUE or FALSE
INVOKE_LIB_SERVER_ON_BOOTUP Program Preference. Example: INVOKE_LIB_SERVER_ON_BOOTUP = FALSE	TRUE or FALSE
FILE_OPEN_HISTORY_COUNT Maximum number of files to be shown at the end of the File Menu in the Schematic and Layout windows. Example: FILE_OPEN_HISTORY_COUNT = 4	Integer
PROJECT_OPEN_HISTORY_COUNT Maximum number of projects to be listed at the end of the File Menu in the Schematic and Layout windows. Example: PROJECT_OPEN_HISTORY_COUNT = 4	Integer
DESIGN_LIST_COUNT Maximum number of designs to appear at the end of the Windows Menu in the Schematic and Layout windows. Example: DESIGN_LIST_COUNT = 9	Integer
SCHEMATIC_COMPONENT_PALETTE_LIST_COUNT Maximum number of palettes displayed in the component palette drop-down list on the Schematic window toolbar. Example: SCHEMATIC_COMPONENT_PALETTE_LIST_COUNT = 16	Integer
LAYOUT_COMPONENT_PALETTE_LIST_COUNT Maximum number of palettes displayed in the component palette drop-down list on the Layout window toolbar. Example: LAYOUT_COMPONENT_PALETTE_LIST_COUNT = 16	Integer
SCHEMATIC_COMPONENT_PALETTE_LIST_WIDTH Width of the component palette drop-down list on the Schematic window toolbar. Example: SCHEMATIC_COMPONENT_PALETTE_LIST_WIDTH = 16	Integer
LAYOUT_COMPONENT_PALETTE_LIST_WIDTH Width of the component palette drop-down list on the Layout window toolbar. Example: LAYOUT_COMPONENT_PALETTE_LIST_WIDTH = 16	Integer
SCHEMATIC_COMPONENT_HISTORY_LIST_COUNT Maximum number of components displayed in the component history drop-down list on the Schematic window toolbar. Example: SCHEMATIC_COMPONENT_HISTORY_LIST_COUNT = 10	Integer
LAYOUT_COMPONENT_HISTORY_LIST_COUNT Maximum number of components displayed in the component history drop-down list on the Layout window toolbar. Example: LAYOUT_COMPONENT_HISTORY_LIST_COUNT = 10	Integer
SCHEMATIC_COMPONENT_HISTORY_LIST_WIDTH Width of the component history drop-down list on the Schematic window toolbar. Example: SCHEMATIC_COMPONENT_HISTORY_LIST_WIDTH = 7	Integer
LAYOUT_COMPONENT_HISTORY_LIST_WIDTH Width of the component history drop-down list on the Layout window toolbar. Example: LAYOUT_COMPONENT_HISTORY_LIST_WIDTH = 7	Integer
LAYER_LIST_COUNT Maximum number of layers to be shown in the layer list drop-down list on the Layout window toolbar. Example: LAYER_LIST_COUNT = 10	Integer
LAYER_LIST_WIDTH Width of the drop-down layer list on the Layout window toolbar. Example: LAYER_WIDTH = 14	Integer
SIMULATION_HOST_LIST Remote simulation host names Example: SIMULATION_HOST_LIST = machine.company.com	Host names
MAIN_WINDOW_X_LOC, MAIN_WINDOW_Y_LOC The default location of the Main window. The upper left corner of the window is positioned at the specified X,Y screen coordinates, where 0,0 is the upper left corner. Example: MAIN_WINDOW_X_LOC = 0 Example: MAIN_WINDOW_Y_LOC = 0	Integer
MAIN_WINDOW_WIDTH, MAIN_WINDOW_HEIGHT The default size of the Main window in pixels (window can still be re-sized manually). Example: MAIN_WINDOW_WIDTH = 365 Example: MAIN_WINDOW_HEIGHT = 340	Integer Min. Width = 340 Min. Height = 300
SCHEMATIC_WINDOW_X_LOC, SCHEMATIC_WINDOW_Y_LOC The default location of the Schematic window. The upper left corner of the window is positioned at the specified X,Y screen coordinates, where 0,0 is the upper left corner. Example: SCHEMATIC_WINDOW_X_LOC = 260 Example: SCHEMATIC_WINDOW_Y_LOC = 0	Integer
SCHEMATIC_WINDOW_WIDTH, SCHEMATIC_WINDOW_HEIGHT The default size of the Schematic window in pixels (window can still be re-sized manually). Example: SCHEMATIC_WINDOW_WIDTH = 780 Example: SCHEMATIC_WINDOW_HEIGHT = 530	Integer Min. Width = 760 Min. Height = 500
LAYOUT_WINDOW_X_LOC, LAYOUT_WINDOW_Y_LOC The default location of the Layout window. The upper left corner of the window is positioned at the specified X,Y screen coordinates, where 0,0 is the upper left corner. Example: LAYOUT_WINDOW_X_LOC = 30 Example: LAYOUT_WINDOW_Y_LOC = 30	Integer
LAYOUT_WINDOW_WIDTH, LAYOUT_WINDOW_HEIGHT The default size of the Layout window in pixels (window can still be re-sized manually). Example: LAYOUT_WINDOW_WIDTH = 1012 Example: LAYOUT_WINDOW_HEIGHT = 500	Integer Min. Width = 760 Min. Height = 500
ELW_WINDOW_OPEN_WITH_SCHEMATIC When True, the Layers window will automatically be displayed when a schematic window is opened. Example: ELW_WINDOW_OPEN_WITH_SCHEMATIC = FALSE	TRUE or FALSE
ELW_WINDOW_OPEN_WITH_LAYOUT When True, the Layers window will automatically be displayed when a layout window is opened. Example: ELW_WINDOW_OPEN_WITH_LAYOUT = TRUE	TRUE or FALSE
ELW_WINDOW_AUTO_REDRAW_DESIGN When True, the current design representation's schematic or layout window will be redrawn whenever the Layers window changes the design representation's layers information. Example: ELW_WINDOW_AUTO_REDRAW_DESIGN = TRUE	TRUE or FALSE
ELW_WINDOW_INITIAL_X_LOC, ELW_WINDOW_INITIAL_Y_LOC The default initial location of the Layers window. The upper left corner of the window is positioned at the specified X, Y screen coordinates, where 0,0 is the upper left corner. Example: ELW_WINDOW_INITIAL_X_LOC = 0 Example: ELW_WINDOW_INITIAL_Y_LOC = 100	Integer
ELW_WINDOW_INITIAL_WIDTH, ELW_WINDOW_INITIAL_HEIGHT The default initial size of the Layers window in pixels (window can still be resized manually). Example: ELW_WINDOW_INITIAL_WIDTH = 200 Example: ELW_WINDOW_INITIAL_HEIGHT = 450	Integer
SAVE_PROJECT_STATE Sets a default to be used for any project for which no save_project_state.ael file exists. This file is created/modified when you change projects or exit the program and the Save Project State on Exit option is on. When on (TRUE), the status of every currently open Schematic and Layout window will be saved and subsequently restored, the next time you open that project. Note that only windows with named designs are saved; untitled windows are not saved. Example: SAVE_PROJECT_STATE = TRUE	TRUE, FALSE
COMMAND_DIALOG_WIDTH Sets the width, in pixels, of the Command Line dialog box ( Options > Command Line in the Main window). The default is 400; a wider setting may be helpful for viewing lengthy AEL functions. Example: COMMAND_DIALOG_WIDTH = 400	Integer
DATA_FILES Specifies the search path for data files. Example: DATA_FILES = ./data:{$HOME}/hpeesof/my_datafiles	Path
OPEN_PROJECT_AUTO_SCHEMATIC Sets a default for all projects. When TRUE, an empty Schematic window is automatically displayed when you create a project. Example: OPEN_PROJECT_AUTO_SCHEMATIC = TRUE	TRUE, FALSE
OPEN_PROJECT_AUTO_LAYOUT Sets a default for all projects. When TRUE, an empty Layout window is automatically displayed when you create a project. Example: OPEN_PROJECT_AUTO_LAYOUT = FALSE	TRUE, FALSE
SCHEMATIC_ANALOG_DEFAULT_PALETTE Sets the specified palette as the default palette for Analog/RF designs in the Schematic window. Example: SCHEMATIC_ANALOG_DEFAULT_PALETTE = Devices-MOS	Standard or custom palette name, exactly as it appears in program.
LAYOUT_ANALOG_DEFAULT_PALETTE Sets the specified palette as the default palette for Analog/RF designs in the Layout window. Example: LAYOUT_ANALOG_DEFAULT_PALETTE = TLines-Stripline	Standard or custom palette name, exactly as it appears in program.
SCHEMATIC_DSP_DEFAULT_PALETTE Sets the specified palette as the default palette for DSP designs in the Schematic window. Example: SCHEMATIC_DSP_DEFAULT_PALETTE = Timed Linear	Standard or custom palette name, exactly as it appears in program.
LAYOUT_DSP_DEFAULT_PALETTE Sets the specified palette as the default palette for DSP designs in the Layout window. Example: LAYOUT_DSP_DEFAULT_PALETTE = Block Text Fonts	Standard or custom palette name, exactly as it appears in program.
USER_MENU_FUNCTION_LIST Controls which functions are called every time a new window is opened. Example: USER_MENU_FUNCTION_LIST = app_add_user_menus	Function names
OPEN_DDS_AFTER_SIM Establishes a default state for whether or not to automatically open a Data Display window upon completion of a simulation. This setting can be overridden for any given simulation using the Simulation Setup dialog box. Note: If this variable is not defined, or is defined but set to something other than TRUE or FALSE, the initial state for Analog/RF designs is TRUE and for DSP designs is FALSE. Example: OPEN_DDS_AFTER_SIM = TRUE	TRUE or FALSE
CONFIG_EXPLORER_VARS Controls which variables are listed when you launch the Configuration Explorer. This list is delimited by semicolons. Each variable name is preceded by one of the following designations, as well as an underscore character: E_ For Environment variables Example: CONFIG_EXPLORER_VARS = E_HPEESOF_DIR C_ For Configuration variables Example: CONFIG_EXPLORER_VARS = C_SITE_AEL S_ For System variables (PC only) Example: CONFIG_EXPLORER_VARS = S_TEMP	E_<VariableName>, C_<VariableName>, S_<VariableName>
CONFIG_EXPLORER_CMP_VARS Controls whether or not the Configuration Explorer evaluates the value of every variable and compares it against the current value in the environment. If the setting of a given variable is the same as the current value in the environment, it is preceded by a green dot; if the values are different, it is preceded by a yellow dot. (Note: Setting this variable to yes is helpful for troubleshooting configuration problems but takes your system considerable time to perform the evaluations.) The default value is no. Example: CONFIG_EXPLORER_CMP_VARS = yes	Yes or No
MAKELIB_USER_AEL_PATH Complete path for .ael files (associated with .dsn files) added to a user library using the custom library tool. Multiple libraries can be defined by specifying a semicolon-delimited list. Example: MAKELIB_USER_AEL_PATH = {$HOME}/hpeesof/circuit/ael	Path
MAKELIB_USER_DSN_PATH Complete path for .dsn files added to a user library using the custom library tool. Multiple libraries can be defined by specifying a semicolon-delimited list. Example: MAKELIB_USER_DSN_PATH = {$HOME}/hpeesof/circuit/networks	Path
MAKELIB_USER_DATA_FILES Complete path for data files referenced by designs added to a user library using the custom library tool. Example: MAKELIB_USER_DATA_FILES = {$HOME}/hpeesof/datafiles	Path
MAKELIB_USER_LIBRARY_NAMES The library name(s) that are used if no Library Name was specified in the Design Parameters dialog box. Multiple libraries can be defined by specifying a semicolon-delimited list. The members of this list must have a one-to-one correspondence with the lists set for the three aforementioned variables. Example: MAKELIB_USER_LIBRARY_NAMES = User Library	Default or custom library name
MAKELIB_SITE_AEL_PATH Complete path for .ael files (associated with .dsn files) added to a site library using the custom library tool. Multiple libraries can be defined by specifying a semicolon-delimited list. Example: MAKELIB_SITE_AEL_PATH = {$HPEESOF_DIR}/custom/circuit/ael	Path
MAKELIB_SITE_DSN_PATH Complete path for .dsn files added to a site library using the custom library tool. Multiple libraries can be defined by specifying a semicolon-delimited list. Example: MAKELIB_SITE_DSN_PATH = {$HPEESOF_DIR}/custom/circuit/networks	Path
MAKELIB_SITE_DATA_FILES Complete path for data files referenced by designs added to a site library using the custom library tool. Example: MAKELIB_SITE_DATA_FILES = {$HPEESOF_DIR}/custom/datafiles	Path
MAKELIB_SITE_LIBRARY_NAMES The library name(s) that are used if no Library Name was specified in the Design Parameters dialog box. Multiple libraries can be defined by specifying a semicolon-delimited list. The members of this list must have a one-to-one correspondence with the lists set for the three aforementioned variables. Example: MAKELIB_SITE_LIBRARY_NAMES = Site Library	Default or custom library name

Variables in the File hpeesof.cfg

All programs that are part of the ADS suite read the hpeesof configuration file.

Variable, description, and example	Value(s)
HPEESOF_LM_LICENSE_FILE Complete path to FLEXlm license.lic file. Example: HPEESOF_LM_LICENSE_FILE = {$HPEESOF_DIR}/license/license.lic	Filename
HPEESOF_COLOR Complete path to system-wide color configuration file. Example: HPEESOF_COLOR = {$HPEESOF_DIR}/config/hpeecolor.cfg	Filename
HPEESOF_FILL Complete path to system-wide fill pattern configuration file. Example: HPEESOF_FILL = {$HPEESOF_DIR}/config/hpeefill.cfg	Filename
HPEESOF_FONT_FILE Directory where TrueType raster fonts are located. Example: HPEESOF_FONT_FILE = {$HPEESOF_DIR}/config	Directory
HPEESOF_OCCIDENTAL_FILE Complete path to European Hershey vector fonts. Example: HPEESOF_OCCIDENTAL_FILE = {$HPEESOF_DIR}/config/hersh.oc	Filename
HPEESOF_ORIENTAL_FILE Complete path to Asian Hershey vector fonts. Example: HPEESOF_ORIENTAL_FILE = {$HPEESOF_DIR}/config/hersh.or	Filename
HPEESOF_LANGUAGE Specifies the default language. Example: HPEESOF_LANGUAGE = english	Language name
AGILEESOFD_LICPREF Controls bundle selection for all systems on a network with access to the license server. Example: AGILEESOFD_LICPREF = bundle_a	License bundle name
AGILEESOFD_LICPREF_<hostname> Controls bundle selection specifically for the system identified by <hostname>. Example: AGILEESOFD_LICPREF_alpha = bundle_b	License bundle name

Variables in the File dfilter.cfg

This configuration file is used by the Digital Filter tool.

Variable, description, and example	Value(s)
DF_AEL_PATH The AEL path for Digital Filter designs. Example: DF_AEL_PATH = ./:$HOME/hpeesof/dfilter/ael: $HPEESOF_DIR/custom/dfilter/ael:$HPEESOF_DIR/dfilter/ael	Path
DFUI_DATA_FILE Data file, only for Digital Filter UI Example: DFUI_DATA_FILE = $HPEESOF_DIR/dfilter/ael/firdemoui.ael	Filename
DFUI_SPEC_HEADING_COLOR Foreground color for spec heading data, only for Digital Filter UI Example: DFUI_SPEC_HEADING_COLOR = BLUE	Color name
DFUI_SPEC_EDITABLE_COLOR Foreground color for spec editable data, only for Digital Filter UI Example: DFUI_SPEC_EDITABLE_COLOR = BLACK	Color name
DFUI_SPEC_NOEDITABLE_COLOR Foreground color for spec non-editable data, only for Digital Filter UI Example: DFUI_SPEC_NOEDITABLE_COLOR = GRAY	Color name
DFUI_SPEC_CELL_WIDTH Column width for spec data, only for Digital Filter UI Example: DFUI_SPEC_CELL_WIDTH = 7	Integer
DF_DDS_IDEAL_TRACE_COLOR Trace color index to be used in hpeesof data display server Example: DF_DDS_IDEAL_TRACE_COLOR = 1	Integer
DF_DDS_SCALED_TRACE_COLOR Trace color index to be used in hpeesof data display server Example: DF_DDS_SCALED_TRACE_COLOR = 3	Integer
DF_DDS_SPEC_TRACE_COLOR Trace color index to be used in hpeesof data display server Example: DF_DDS_SPEC_TRACE_COLOR = 4	Integer

Variables in the File eeapi.cfg

This configuration file is used by the layered Application Programming Interface (API).

Variable, description, and example	Value(s)
API_BALLOON_HELP_TIMEOUT Time taken for balloon help to appear when icon is selected. Example: API_BALLOON_HELP_TIMEOUT = 600	Time in milliseconds
API_BALLOON_HELP Sets whether balloon help exists or not. Example: API_BALLOON_HELP = TRUE	TRUE or FALSE
API_BALLOON_HELP_DISMISSAL_TIMEOUT Time taken for balloon help to disappear when icon is selected. Example: API_BALLOON_HELP_DISMISSAL_TIMEOUT = 6000	Time in milliseconds
API_DOUBLE_CLICKS_TIME_OUT The time between two clicks required for them to be recognized as a unit, or double-click. Example: API_DOUBLE_CLICKS_TIME_OUT = 400	Time in milliseconds
API_NO_TEAR_OFF_MENU Turn on/off Motif's tear-off menu Example: API_NO_TEAR_OFF_MENU = 0	0=allow tear-off menu 1= do not allow tear-off menu

Variables in the File hpads.cfg

This configuration file is used by PTOLEMY for locating user-compiled models and the location of MATLAB software.

Variable, description, and example	Value(s)
ADSPTOLEMY_MOD_PATH Controls where ADS Ptolemy will look for models. You must reference the ADSPTOLEMY_MODEL_PATH variable here so that user-compiled models are found. If ADS is started with the -b option, then $HPEESOF_DIR/adsptolemy/beta will be appended to load beta models. Example: ADSPTOLEMY_MOD_PATH = $HOME/hpeesof/adsptolemy: $ADSPTOLEMY_MODEL_PATH:$HPEESOF_DIR/adsptolemy	Path
MATLAB The MATLAB variable should point to the root of your Matlab 5 installation (directories bin and extern should be there). Example: MATLAB = /usr/local/matlab	Directory
MATLABCMD If the command to invoke Matlab is not matlab, you'll need to set the MATLABCMD variable. See the documentation for engOpen in the Matlab Application Programming Interface Guide for more details on what you can do here. This variable is ignored on Windows. Example: MATLABCMD = "matlab -c licensefile"	Command

Variables in the File hpeesofbrowser.cfg

This configuration file is used by the Browse and Search dialog box.

Variable, description, and example	Value(s)
HPEESOF_BROWSER_WINDOW_X_LOCATION The default X coordinate of the Component Library window relative to the upper left corner of the screen. Example: HPEESOF_BROWSER_WINDOW_X_LOCATION = 100	Integer
HPEESOF_BROWSER_WINDOW_Y_LOCATION The default Y coordinate of the Component Library window relative to the upper left corner of the screen. Example: HPEESOF_BROWSER_WINDOW_Y_LOCATION = 100	Integer
HPEESOF_BROWSER_WINDOW_WIDTH The default width of the Component Library window. Example: HPEESOF_BROWSER_WINDOW_WIDTH = 600	Integer
HPEESOF_BROWSER_WINDOW_HEIGHT The default height of the Component Library window. Example: HPEESOF_BROWSER_WINDOW_HEIGHT = 400	Integer
HPEESOF_BROWSER_TIME_OUT The default time-out for warning/information messages. Example: HPEESOF_BROWSER_TIME_OUT = 10000	Time in milliseconds
HPEESOF_BROWSER_AEL_PATH Path for the browser AEL files. Example: HPEESOF_BROWSER_AEL_PATH = $HOME/hpeesof/hpeesofbrowser/ael:$HPEESOF_DIR/hpeesofbrowser/ael	Path
HPEESOF_BROWSER_AEL Top level AEL file Example: HPEESOF_BROWSER_AEL = lbb_main	Filename
HPEESOF_BROWSER_PATH Path for the control, records and Device Libraries Binary File. Path can only have System variables. Example: HPEESOF_BROWSER_PATH = $HOME/hpeesof/hpeesofbrowser/records; $COMPL_DIR/ComponentLibs/records	Path
HPTOLEMY_BROWSER_PATH ADS Ptolemy related control, record and IDF files. All the control files and the IDF files in these directories are read to create the ADS Ptolemy related libraries and sub-libraries Example: HPTOLEMY_BROWSER_PATH = $HPTOLEMY_MODEL_AEL;$HPEESOF_DIR/CustomEncoded/records	Path
HPEESOF_BROWSER_LIBRARIES_FIELD_WIDTH The default width of the component library tree structure. Example: HPEESOF_BROWSER_LIBRARIES_FIELD_WIDTH = 30	Integer
HPEESOF_BROWSER_PARTS_DISPLAY_WIDTH The default width of the Component column. (This column is always visible.) Example: HPEESOF_BROWSER_PARTS_DISPLAY_WIDTH = 15	Integer
HPEESOF_BROWSER_FIELD_NUM_ROWS The default number of rows of components listed for any selected sub-library. Example: HPEESOF_BROWSER_FIELD_NUM_ROWS = 20	Integer
HPEESOF_BROWSER_COMPONENT_DESCRIPTION_VISIBLE The default visibility status of the Description column. Example: HPEESOF_BROWSER_COMPONENT_DESCRIPTION_VISIBLE = 1	0 = False 1= True
HPEESOF_BROWSER_PARTS_DESCRIPTION_WIDTH The default width of the Description column. Example: HPEESOF_BROWSER_PARTS_DESCRIPTION_WIDTH = 20	Integer
HPEESOF_BROWSER_COMPONENT_VENDOR_VISIBLE The default visibility status of the Vendor column. Example: HPEESOF_BROWSER_COMPONENT_VENDOR_VISIBLE = 0	0 = False 1= True
HPEESOF_BROWSER_PARTS_VENDOR_WIDTH The default width of the Vendor column. Example: HPEESOF_BROWSER_PARTS_VENDOR_WIDTH = 10	Integer
HPEESOF_BROWSER_COMPONENT_LIBNAME_VISIBLE The default visibility status of the Library column. Example: HPEESOF_BROWSER_COMPONENT_LIBNAME_VISIBLE = 0	0 = False 1= True
HPEESOF_BROWSER_PARTS_LIBNAME_WIDTH The default width of the Library column. Example: HPEESOF_BROWSER_PARTS_LIBNAME_WIDTH = 20	Integer
HPEESOF_BROWSER_COMPONENT_PLACEMENT_VISIBLE The default visibility status of the Placement column. Example: HPEESOF_BROWSER_COMPONENT_PLACEMENT_VISIBLE = 0	0 = False 1= True
HPEESOF_BROWSER_PARTS_PLACEMENT_WIDTH The default width of the Placement column. Example: HPEESOF_BROWSER_PARTS_PLACEMENT_WIDTH = 15	Integer
HPEESOF_BROWSER_COMPONENT_WEBSITE_VISIBLE The default visibility status of the Website column. Example: HPEESOF_BROWSER_COMPONENT_WEBSITE_VISIBLE = 0	0 = False 1= True
HPEESOF_BROWSER_PARTS_WEBSITE_WIDTH The default width of the Website column. Example: HPEESOF_BROWSER_PARTS_WEBSITE_WIDTH = 20	Integer
HPEESOF_BROWSER_COMPONENT_AVAILABILITY_VISIBLE The default visibility status of the Availability column. Example: HPEESOF_BROWSER_COMPONENT_AVAILABILITY_VISIBLE = 0	0 = False 1= True
HPEESOF_BROWSER_PARTS_AVAILABILITY_WIDTH The default width of the Availability column. Example: HPEESOF_BROWSER_PARTS_AVAILABILITY_WIDTH = 10	Integer
HPEESOF_BROWSER_COMPONENT_LICENSE_VISIBLE The default visibility status of the License column. Example: HPEESOF_BROWSER_COMPONENT_LICENSE_VISIBLE = 0	0 = False 1= True
HPEESOF_BROWSER_PARTS_LICENSE_WIDTH The default width of the License column. Example: HPEESOF_BROWSER_PARTS_LICENSE_WIDTH = 10	Integer
ADS_COMPONENT_SORT_ORDER The sort order for components. Example: ADS_COMPONENT_SORT_ORDER = Default	Default Ascending Descending
ADS_ANALOGRF_LIBRARY_SORT_ORDER The sort order for the analogRF library. Example: ADS_ANALOGRF_LIBRARY_SORT_ORDER = Default	Default Ascending Descending
ADS_HPTOLEMY_LIBRARY_SORT_ORDER The sort order for the Ptolemy library. Example: ADS_HPTOLEMY_LIBRARY_SORT_ORDER = Ascending	Default Ascending Descending
HPEESOF_BROWSER_COMPONENT_HIDE_OBSOLETE Hides obsolete ADS library components from view in the ADS library browser. Example: HPEESOF_BROWSER_COMPONENT_HIDE_OBSOLETE = 1	0 = False 1= True
HPEESOF_BROWSER_COMPONENT_HIDE_UNLICENSED Hides unlicensed ADS library components from view in the ADS library browser. Example: HPEESOF_BROWSER_COMPONENT_HIDE_UNLICENSED = 1	0 = False 1= True
ADS_BROWSER_DEFAULT_WEBSITE Default website for ADS library records that do not have a website defined. Example: ADS_BROWSER_DEFAULT_WEBSITE = http://www.tm.agilent.com/tmo/hpeesof	URL String
HPANALOGRF_BROWSER_PATH ADS Analog/RF libraries related control, record and IDF files. All the control files and the IDF files in these directories are read to create the ADS Analog/RF related libraries and sub-libraries. Example: HPANALOGRF_BROWSER_PATH = $HOME/hpeesof/circuit/records; $HOME/hpeesof/esyn/records;$HOME/hpeesof/rfsynthesis/records; $HOME/hpeesof/CustomEncoded/records;$HPEESOF_DIR/circuit/records; $HPEESOF_DIR/esyn/records;$HPEESOF_DIR/rfsynthesis/records; $HPEESOF_DIR/CustomEncoded/records; $HPEESOF_DIR/custom/circuit/records; $HPEESOF_DIR/custom/esyn/records; $HPEESOF_DIR/custom/rfsynthesis/records;{%DESIGN_KIT_BROWSER_PATH}	Path
HPVENDORLIB_BROWSER_PATH ADS Device libraries related control, record and IDF files. All the control files and the IDF files in these directories are read to create the ADS Vendor Component device related libraries and sub-libraries. Example: HPVENDORLIB_BROWSER_PATH = $HOME/hpeesof/hpeesofbrowser/records; $COMPL_DIR/ComponentLibs/records; $HPEESOF_DIR/CustomEncoded/records	Path
HP_TEMPLATE_BROWSER_PATH Path information for the DDS template files. Each entry is in the form of <name>\|<path> where <name> is the top level node displayed in the browser and <path> is the path to the directory containing the templates. Example: HP_TEMPLATE_BROWSER_PATH = Product\|{$HPEESOF_DIR}/circuit/templates; Customized\|{$HPEESOF_DIR}/custom/circuit/templates; User\|{$HOME}/hpeesof/circuit/templates; {%DESIGN_KIT_TEMPLATE_BROWSER_PATH}; {%MOMENTUM_TEMPLATE_BROWSER_PATH}	String\|Path

Variables in the File hpeesofdds.cfg

This configuration file is used to configure data displays.

Variable, description, and example	Value(s)
AEL_PATH Top level AEL file Example: AEL_PATH = $HOME/hpeesof/dds/ael/:$HPEESOF_DIR/custom/dds/ael /:$HPEESOF_DIR/dds/ael	Path
DDS_DEFAULTS_FILE Users default defaults file. This file gets read at start-up and written at shutdown with the current set of defaults. Example: DDS_DEFAULTS_FILE = $HOME/hpeesof/config/ddsdefaults.ael	Filename
DDS_WIN_FOREGROUND Window foreground color Example: DDS_WIN_FOREGROUND = 0	Integer
DDS_WIN_BACKGROUND Window background color Example: DDS_WIN_BACKGROUND = 8	Integer
DDS_WIN_HEIGHT Window height Example: DDS_WIN_HEIGHT = 510	Integer
DDS_WIN_WIDTH Window width Example: DDS_WIN_WIDTH = 655	Integer
DDS_HIGHLITE_LINE_TYPE System-wide highlight line type Example: DDS_HIGHLITE_LINE_TYPE = 0 [= solid]	Integer
DDS_HIGHLITE_LINE_WIDTH System-wide highlight line width Example: DDS_HIGHLITE_LINE_WIDTH = 56 [= 4 points]	Integer
DDS_HIGHLITE_LINE_COLOR System-wide highlight line color Example: DDS_HIGHLITE_LINE_COLOR = 1 [= red]	Integer
DDS_DRAWING_UNITS_PER_INCH Default graphical object characteristic: Internal database resolution Example: DDS_DRAWING_UNITS_PER_INCH = 1000	Integer
DDS_PAGE_WIDTH Default graphical object characteristic: Plotting area width Example: DDS_PAGE_WIDTH = 33000	Integer
DDS_PAGE_HEIGHT Default graphical object characteristic: Plotting area is height Example: DDS_PAGE_HEIGHT = 21000	Integer
DDS_DEFAULT_LINE_WIDTH Default graphical object characteristic: Plotting line width Example: DDS_DEFAULT_LINE_WIDTH = 7	Integer
DDS_LEFT_CLICK_SENSITIVITY A left-mouse-button press-and-hold drag must move this many pixels or else it is considered a left click Example: DDS_LEFT_CLICK_SENSITIVITY= 2	Integer
DDS_DEFAULT_PLOT_WIDTH Default width of new plots Example: DDS_DEFAULT_PLOT_WIDTH = 3750	Integer
DDS_DEFAULT_PLOT_HEIGHT Default height of new plots Example: DDS_DEFAULT_PLOT_HEIGHT = 2318	Integer
DDS_DEFAULT_FONT Default font Example: DDS_DEFAULT_FONT = HersheyRomanNarrow	Font size, in points
DDS_NUMBER_OF_TRACE_COLORS Number of trace colors Example: DDS_NUMBER_OF_TRACE_COLORS = 16	Integer
DDS_TRACE n _COLOR n th color, where n = 1 to DDS_NUMBER_OF_TRACE_COLORS Example: DDS_TRACE16_COLOR = 90	Integer

Variables in the File hpeesofhelp.cfg

This configuration file is used to locate the online documentation.

Variable, description, and example	Value(s)
TOPLEVEL_DOC Top level Index document location. Example: TOPLEVEL_DOC = $HPEESOF_DIR/doc	Directory
LOCAL_DOC_PATH List of additional paths for the Help Server to search. Example: LOCAL_DOC_PATH = C:\newpath1;C:\newpath2;{% DESIGN_KIT_DOC_PATH}	List of Paths
LOCAL_BOOK_NAMES Optional list of new books. Example: LOCAL_BOOK_NAMES = newbook1;newbook2;{% DESIGN_KIT_BOOKNAMES}	List of names

Variables in the File hpeesofinstrio.cfg

This configuration file is used by the Instrument Server.

Variable, description, and example	Value(s)
AEL_PATH Top level AEL file Example: AEL_PATH = $HOME/hpeesof/instrio/ael/: $HPEESOF_DIR/custom/instrio/ael/:$HPEESOF_DIR/instrio/ael:./	Path

Variables in the File momentum.cfg

This configuration file is used by Momentum.

Variable, description, and example	Value(s)
SUPL_GF_DATABASE Location of supplied Momentum Substrate files. Example: SUPL_GF_DATABASE = {$HPEESOF_DIR}/momentum/lib	Directory
SITE_GF_DATABASE Location of user Momentum Substrate files. Example: SITE_GF_DATABASE = {$HOME}	Directory
LOCL_GF_DATABASE Location of project Momentum Substrate files. Example: LOCL_GF_DATABASE = ./	Directory
MOM_SLM_PATH Path to search for Momentum Substrate file that is saved with design files. Example: MOM_SLM_PATH = ./networks:{%SUPL_GF_DATABASE}	Path
MOMDDS_FILE On UNIX, location of default template file for Momentum Data Display. Example: MOMDDS_FILE= {$HPEESOF_DIR}/sess/ael/momdds.ael	Filename
MOMMSH_REFACET_ARC_RESOLUTION Maximum resolution for the automatic refacetting of arcs and circles in Momentum. Setting a lower value results in a higher resolution representation with more unknowns in the mesh, resulting in a longer simulation time. Example: MOMMSH_REFACET_ARC_RESOLUTION = 45	Integer
MOM3D_USE_MATRIXSOLVER Sets solver algorithm to non-blocked or blocked. Example: MOM3D_USE_MATRIXSOLVER = 0	0 = non-blocked 1 = blocked
MOM3D_USE_MATRIXSOLVERBLOCKSIZE On UNIX, the block size used to tune the linear solver. Example: MOM3D_USE_MATRIXSOLVERBLOCKSIZE = 16	Integer

Variables in the File smg_ui.cfg

This configuration file is used by the SPICE Model Generator.

Variable, description, and example	Value(s)
SMG_AEL_PATH PATH to look for top level AEL file. Example: SMG_AEL_PATH={$HOME}/hpeesof/smg/ael: {$HPEESOF_DIR}/smg/ael: {$HPEESOF_DIR}/ael_smg_ui	Path
SMG_UI_AEL Top level AEL file. Example: SMG_UI_AEL = smg_main	Filename

Variables in the File hpeesofsim.cfg

Variable, description, and example	Value(s)
AEL_PATH Search path for locating AEL files loaded by the simulator Example: AEL_PATH = $HOME/hpeesof/circuit/ael: $HOME/hpeesof/expressions/ael:$HPEESOF_DIR/custom/circuit/ael: $HPEESOF_DIR/custom/expressions/ael:$HPEESOF_DIR/circuit/ael: $HPEESOF_DIR/expressions/ael:.	Path
USER_MODEL_PATH Path for User-Compiled models Example: USER_MODEL_PATH = /some/path/to/model/directory:/some/path/to/a/directory	Path
USER_SIM_FILE_PATH Path for user-defined simulation files Example: USER_SIM_FILE_PATH = /path/to/my/directory:/some/path/to/somewhere	Path
ADSLIBCONFIG_PATH Path for ADS library configuration file Example: ADSLIBCONFIG_PATH = $_HP_GEMINI_LIBPATH: % DKIT_ADSLIBCONFIG_PATH:$HOME/hpeesof/circuit/config: $HPEESOF_DIR/custom/circuit/config:$HPEESOF_DIR/circuit/config:.	Path

Variables in the File hpeesofsess.cfg

This configuration file is used by the Status window.

Variable, description, and example	Value(s)
STATUS_LINES_SHOWN Sets the maximum number of lines visible in the Status window. Example: STATUS_LINES_SHOWN =100	Integer
SIMEXEC_MAP_TO_FRONT Sets the default behavior of the Status window, where on (the default) means the Status window pops to the front of the screen anytime new messages are displayed in it, and off means it does not pop forward automatically. Example: SIMEXEC_MAP_TO_FRONT = on	ON or OFF
HPEESOFSIM_BIN Path to the hpeesofsim executable. Relative pathnames are evaluated relative to the current project's top-level directory. Note that using HPEESOFSIM_BIN to point to a user-defined hpeesofsim executable will cause problems with statically-linked user-compiled models since the simulator containing the models is prevented from being used. If this variable is changed, ADS must be restarted for the changes to take effect. Example: HPEESOFSIM_BIN=hpeesofsim	Path