Laserfiche WebLink
<br />001175 <br /> <br />Table 1 -- FILEjDIRECTORY STRUCTURE <br /> <br />le24/pro gram/ gks/ sre: <br />LC24RUN - script program which runs the 24ADSS <br />*.f, *.c - source and object f1les for the routines of 24ADSS <br />CRSM24 - executable of the 24MSM <br />files24mo - directory containing INPUT and OUTPUT files <br />The file conventions here must be maintained, for example: <monthyear>.IN like <br />APR90.IN for April 1990 <br />*.IN - is the INPUT file (formerly CFTA YPK) <br />*.HIS - is the history file (formerly HISTORY) <br />*.LB - is the LB24MO file <br />*.OUT - is the OUlPUT file (formerly UNFORMA T.OUT?) <br />*.POW - is the power file (formely POWER) <br />*.WES - is the western file (formerly WESTERN) <br />NOTE: To the user, the file name is only the prefix. For example APR90 would <br />be the filename seen by the user, thus the suffix .IN, .OUT, etc. is appended <br />automatically. <br /> <br />official- a directory to store the "official" files <br />These files have been agreed upon to be the operational file for the month. This <br />provides a location to store these files somewhat "hidden" from view, as to access these <br />files, the path "official/" must prefix the file name <br /> <br />seript- directory containing script files <br />The file conventions are similar to the f1les24mo except that the filename (e.g. APR90) <br />is appended to the script filename given interactively by the user. Thus, a legal script <br />file name would be "test", and would be referenced by the user as "test", while it is <br />stored in this directory as "test.APR90". <br />NOTE: This means that every different file (in the files24mo sense) has different script <br />files associated with them. This stems from the fact that depending upon the month <br />currently being run, there are different combinations of possible water years, calendar <br />years, April- July ranges, etc. Thus, the script files must have the beginning and ending <br />date associated with each parameter to be plotted (month and year) so that each script <br />file is specific to a certain ,main file. <br /> <br />setup file - file which provides for user customization <br /> <br />. working <br />This directory stores the files that the CRSM24 executable file (the 24MSM) uses for <br />its input and output. One of the constraints in designing the file input/output was the <br />desire to keep the original 24MSM intact as possible. Therefore, to allow the user to <br />interactively define a file, it was necessary to have a separate location where the file (to <br />the user it looks like one file, internally represented it is a series of six files) could be <br /> <br />24 Month Study Proicct Documentation Volwne IT <br /> <br />618/91 <br /> <br />IS <br />