How is the project information stored on my computer?
The Sonnet project stores your circuit geometry, analysis controls, response data, and current density data all in one place eliminating the need to keep track of separate files. The project can store the data from multiple analyses as long as there are no changes in the circuit so that the data is still consistent with the input circuit. There is a project menu available in every program in Sonnet which allows you to easily access all the Sonnet products and features making for a more seamless and integrated Sonnet environment. The project menu on the Sonnet task bar has a ”Manage” menu which allows you to manipulate your project files. Commands include Move, Copy, Pack, Unpack, Delete and Clean, which removes pre-existing response data from the project.
We suggest that you do not use the Windows or UNIX environment to move your projects; instead, the Project => Manage command on the Sonnet Task Bar should be used to manipulate your projects. The Sonnet project files are set up as described below.
The structure of the project file consists of the main ”.son” file which appears in the highest level directory. Residing in this directory is a folder ”sondata” which retains all the response data for all the ”.son” files in the parent directory. You can create a separate response file using the Analysis => Output Files command in the project editor or by using the Output menu in the response viewer, but by default, no external files are produced by an analysis. You have an option to set up a default external response data file in the Preferences dialog box in the project editor. However, under normal circumstances all analysis data is stored as part of the project. In the directory ”sondata” is a directory for each ”.son” file, with the basename of the project. Please note that the data files in the ”sondata” directory use an internal file format and are not meant to be read by the user.
The analysis control settings are also stored in the project file. It is possible to save your analysis control settings including the frequency sweeps in an external frequency file (.eff) that can be loaded into a project file so that the sweep may be used multiple times.
For example, you have a working directory c:/myfilters. You use the project editor to create three projects in this directory: steps, filter1 and filter2. These projects would produce the directory structure pictured below:
