.cadence Hierarchy
The .cadence hierarchy contains local customizations for files that Cadence provide. For each location specified in the setup.loc file, the program first searches for .cadence directories.
The following structure is used for .cadence:
<directory>/.cadence/[<user>]/<product>/<tool>/[<version>]/<files>
Where:
-
Prior to saving for the first time, the
user directory is optional and not likely to exist in system areas. Whenever data is saved however, it is always saved under a user-specific directory. -
The
version number is also optional, but should always be used when saving. This setting is optional in order to support the loading of default settings from an installation hierarchy.
This hierarchy structure provides for solid file management when multiple versions of Cadence tools are installed in a common directory.
When CDMS (Cadence Directory Management System) is used by an application, it is expected that user data gets transferred. CDMS implicitly uses .cadence as the top-level directory name.
Your local .cadence directory can contain the following file and subdirectories of information:
|
File or Directory
|
Description
|
|
history/userName.history
|
Maintains information that appears in the History tree on the ADE Explorer Data assistant pane.
You must not edit this file.
|
|
Navigator
|
Contains Options.xml where the program stores any options you specify on the Navigator Options form.
You must not edit this file.
|
|
toolbars
|
Contains custom toolbar definition files.
|
|
workspaces
|
When you save a custom workspace, the program creates this directory along with an application-specific subdirectory containing your custom .workspace file; your workspaces directory might contain several application-specific subdirectories and each application-specific subdirectory might contain several .workspace files.
.workspace files are binary files that you cannot edit.
|
|
workspace.default
|
If you specified a default workspace for an application, the program writes the name of the default workspace to this file.
|
If you save any job policies, the program creates a jobpolicy subdirectory in your .cadence directory to maintain job policy definitions.
Files and directories in the your_install_dir/share/cdssetup/dfII hierarchy include:
|
File or Directory
|
Content
|
|
VLS-EXL
|
Modgen.patterns pattern file for Modgen.
|
|
cds.lib file
|
Default library definitions.
|
|
ci
|
config.xml file defining constraint types for layout as well as a mapping between constraint type and parameter names and what the program displays for these.
|
|
default.drf file
|
Default display resource settings.
|
|
toolbars
|
byApplication subdirectory of Cadence-provided .toolbars files.
|
|
workspaces
|
Application subdirectories containing Cadence-provided .workspace definition files and workspace.default file.
|
Related Topics
Working with Patterns
Cadence Library Definition
Display Resource Development and Usage
Virtuoso Workspaces
Using and Resetting Toolbars
Return to top
