My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_05-23_CRDSSFileOrganization
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_05-23_CRDSSFileOrganization
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:53 AM
Creation date
5/30/2008 2:57:06 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.05-23 - Study of System Integration Issues Software - File Organization for CRDSS
Description
This memorandum discusses issues related to file organization for the CRDSS.
Decision Support - Doc Type
Task Memorandum
Date
5/10/1994
DSS Category
DMI Utilities
DSS
Colorado River
Basin
Colorado Mainstem
Contract/PO #
C153658, C153727, C153752
Grant Type
Non-Reimbursable
Bill Number
SB92-87, HB93-1273, SB94-029, HB95-1155, SB96-153, HB97-008
Prepared By
Riverside Technology inc.
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
4
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
to remember. It also allows the system to be installed on different machines such that users need <br />only remember a single file structure. <br />RTi proposes placing short files in each major CRDSS directory to explain the contents of <br />README <br />that directory. This technique has worked well on past projects both to explain directory contents to <br />developers and users. <br />Source code for individual programs and libraries are placed in separate directories under the <br /> directory. Although an intervening directory could be used (e.g., <br />/crdss src/ <br />), this sometimes leads to the confusing path such as <br />/crdss/src/modsim <br />. The convention for storing source is debatable and may change <br />/crdss/src/modsim/src <br />depending on the file structure for existing code (e.g., MODSIM). <br />Each library has a separate directory for source code but all linkable libraries are stored in a single <br />directory ( ). This allows all developers to know exactly where libraries are. <br />/crdss/lib <br />The directory contains include files for libraries. Additionally, libraries may <br />/crdss/include <br />require including files under specific libraries (e.g., ). <br />/crdss/libdmi/include <br />Important CRDSS configuration files will be stored in . These are files that may <br />/crdss/system <br />be accessed by more than one CRDSS application. <br />Executable programs for the CRDSS will be stored in . This directory should be <br />/crdss/bin <br />placed in the PATH for each user who runs the CRDSS programs. <br />Programs that are not developed within the CRDSS (e.g., public domain software and general <br />utilities) are placed in the directory. This directory is used for the same purpose on <br />/usr/local <br />many UNIX systems. The directory contains the executable programs for each <br />/usr/local/bin <br />of the utility programs whose source code exists in . <br />/usr/local <br />X Window System resource files for programs that have GUIs are stored in <br />/usr/lib/X11/app- <br />, which is the standard location for such files. <br />defaults <br />General documentation will exist in the directory, which will have many <br />/crdss/doc <br />mosaic <br />subdirectories for documents and other general documents. Documentation for programs <br />and libraries will exist as files under revision control in a subdirectory under the source code <br />directory. This documentation will be installed into more appropriate system locations. <br />System Configuration File <br />The file structure for the CRDSS will be described in a configuration file in the <br />/crdss/system <br />(e.g., ). The purpose of this file will be to specify directory names <br />/crdss/system/crdss.cfg <br />and other information that is important to the CRDSS. The file will allow the system to be <br />reconfigured without having to recompile the CRDSS applications. The general syntax of the file <br />will be: <br /># crdss.cfg - configuration file for CRDSS <br /># <br />CRDSS = /crdss <br />CRDSS_LIB = $(CRDSS)/lib <br />3 <br />A275 05.10.94 1.05-23 Malers <br />
The URL can be used to link to this page
Your browser does not support the video tag.