Project Bundle Files

A project in may be collected into a single file referred to as a bundle file. The file contains the project file, all input files (data files, FISH files, etc.), a state record file for all model states (though not the state (SAV) files themselves), and any files that were used in the process of creating any of the model states.

Any project can become extensive and include a significant number of file dependencies and interrelations that are difficult to follow or remember. It is possible, even likely, that users who attempt project transfer “by hand” will introduce errors due to omission or other incompleteness. The “Bundle” utility provides a less error-prone way for the program itself to package all of a project and its dependencies together, thus increasing the chances of achieving successful project transfer.

Bundles do not contain model state (SAV) files. Thus they provide a compact means of storing a project. If used for this purpose, users should remember several details.

  • Only the version of the program that created a bundle file should be used when unpacking it.

  • The saved model (SAV) states of the project will need to be recreated. This may be done by re-running data files in the appropriate sequence. Alternatively, model states can be recreated from the record files in the bundle using the program playback command (see the section “State Record pane” for more information on record files). Neither is more efficient than the other in recreating model states and either — depending on the size of the project — may be time consuming.


Projects can manifest a very complex interweaving of commands and scripting via FISH. In such cases it is virtually impossible to ensure that the “Bundle” command will allow completely unerring restoration of project data. Users are encouraged to keep this consideration in mind when using the “Bundle” command for project transfer or storage.