8.3. Project Running Directory

The modeFRONTIER Project File^TM (filename.prj) contains all the data the user was requested to enter during the project building process. It is a binary compressed file which includes all the external and template files included in the Work Flow. It also includes all the previous calculated designs, the DOE Initial Table and all the different Response Surfaces associated with the designs database.

All these data are used by modeFRONTIER Project File^TM during the analysis loop unpacking them in the Project Running Directory. modeFRONTIER Project File^TM will create a directory called with the same name as the project file name and will postfix it with a progressive number to avoid any project overlap. For example if the user runs a project named test.prj the project running directory will be test_0000. Let us see how the structure of this new created directory looks.

	test_0000
		\
		| log
		| proc
		|     \
		|      | DES_00001
		|      |       \
		|      |        | applicationA_0000
		|      |        | applicationB_0000
		|      |
		|      | DES_00002
		|      | DES_00003
		|      | DES_00004
		|      | DES_00005
		|
		| usrdata

Here follows a short description of the Project Running Directory structure and the data stored in it.

test_0000 This is the main project running directory, it has the same name of the project (test.prj) and a postfix (_0000) to avoid the overlapping of the already present directories.
log This directory stores all the project run logs. All the logs are in the HTML form an can be viewed by the most common browsers. Browsing this directory you can easily spot the index.html file which can be used as the starting point for the log examination.
proc The directory contains all the running directories related to the designs being evaluated in the analysis cycle.
DES_00001 The design directory stores all the external applications directories. The number(_00001) postfixed to the DES_ label matches the Design id in the modeFRONTIER^TM design data base. Every user application defined in the Work Flow during the analysis loop will be associated to a independent directory. Each design is evaluated in a separate directory to preserve its outputs for possible post processing activities and to separate the different designs data during the concurrent designs evaluation.
applicationA_0000 This directory is where the applicationA actually is running during the design evaluation. All the input and output files will be present in this directory together with the log.out and the log.err files which contains the redirection of the application's standard output and standard error streams.
applicationB_0000 Same as for the applicationA_0000 directory.
usrdata All the input/template files and all the external application scripts defined in the Work Flow are stored in this directory.