ifference between revisions of "EMO:Data Storage Directory Structure"

From EMO Wiki
Jump to navigation Jump to search
Line 88: Line 88:
  
 
===The Inputs Folder===
 
===The Inputs Folder===
[[File:Inputs_Folder.PNG|400px|thumb|right|Figure 1 - Inputs Folder Directory]]
+
[[File:Inputs_Folder.PNG|400px|thumb|right|Figure 2 - Inputs Folder Directory]]
 
The Inputs folder contains several sub-folders:
 
The Inputs folder contains several sub-folders:

Revision as of 15:12, 18 December 2012

EMarketOffer creates two separate directory structures during installation:

  • Program files
  • Data files


Program Files

During the installation process you can choose where EMarketOffer places its program files (default C:\Program Files\Ellsoft\EMO). This folder contains the EMarketOffer executable and the dlls (dynamic link libraries) required by the program.

Warning! You should not attempt to modify or move the location of any of these files after installation - doing so will cause the program to malfunction.

Data Files

File:Data Files.PNG
Figure 1 - The Directory Structure

During installation EMarketOffer creates a data directory structure containing the folders to the right:

You can select the location for the data folders during the installation process. For performance reasons it is recommended that the data folder be located on the same computer as the EMarketOffer executable.

The Connection Folder

The information required to connect EMarketOffer to external databases is stored here.

File Purpose Comment
<Configuration_Name>.xml
Where <Configuration_Name> is the name of a previously created Database Connectivity Configuration.
Stores database connectivity data referred to during program launch
Editing, deleting or moving this file may cause EMarketOffer to malfunction.

The Forecast Folder

This folder stores the definitions of Forecasts and Powerflow Cases (.xml format), and the results of Forecasts, Powerflow Cases and Scenarios (binary form).

Sub-Folder File Purpose Comment
Forecasts
<My_Forecast>.ibn
Contains the output in binary form of the last run of the 'My_Forecast' Forecast Definition
One .ibn file will exist for each currently available Forecast Definition that has been run.

NOTE: Deleting a Forecast Definition using the 'Main Window Data Source Manager will delete the associated .ibn file.
Forecasts.xml
Contains the latest Definitions for all current Forecasts.
In editing or deleting this file you run the risk of losing all current Forecast Definitions and associated results data.
Powerflows
<My_Powerflow>.ibn
Contains the output in binary form of the last run of the 'My_Powerflow' Powerflow Case Definition
One .ibn file will exist for each currently available Powerflow Case Definition that has been run.

NOTE: Deleting a Powerflow Case Definition using the 'Main Window Data Source Manager will delete the associated .ibn file.
Powerflows.xml
Contains the latest Definitions for all current Powerflow Cases.
In editing or deleting this file you run the risk of losing all current Powerflow Case Definitions and associated results data.
Scenarios
<My_Scenario>.scn
Contains the output in binary form of the 'My_Scenario' Scenario
One .scn file will exist for each currently available Scenario
Library
<My_Component>.xml
Contains the definition for a saved Powerflow Case or Forecast Component.


The Inputs Folder

File:Inputs Folder.PNG
Figure 2 - Inputs Folder Directory

The Inputs folder contains several sub-folders: