This is an old revision of the document!
Table of Contents
Getting project specific paths
This method was originally constructed to allow for the export of data for different projects to be grouped together in one common spot. For example in caness there is an export directory /models/caness/exportData and under that there are sub-directories, one for each project and appended to the project name is the model family name from which the data was exported and finally that directory is subdivided by subject area of the files like commercial, industrial etc. One particular example:
</code>/space/models/caness/exportData/YourEnergyStory_CANESS_Ver5/elecProd</code>
A view may want to read and write parameter type data for it's running which is specific to a particular project.
Background
How To
There is a sub routine called getProjectExportPath_v2.t (potentially updated version number over time). That subroutine takes the following as inputs/outputs:
- inputStringSet - this is a string set with 3 entries in ORDER:
- exportDataDir - this is the root of where the returned path starts - you must ensure this part of the path is previously made
- subjectArea - this is actually the last part of the path which divide's the project's data in to
- projectAppendText -
