My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_17-1_ModelDocumentation
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_17-1_ModelDocumentation
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/26/2011 8:32:32 AM
Creation date
7/11/2008 12:57:20 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.17-1 - Model Documentation
Description
This task memo describes how the CRDSS models will be documented.
Decision Support - Doc Type
Task Memorandum
Date
6/29/1994
DSS Category
Surface Water
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.
/
3
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
that information under the home page will be extracted from existing documentation or new <br />documentation that is being developed for the CRDSS. <br />It is important to rely on existing documentation as the master copy of documentation while allowing <br />updates in the master copy to be retransferred to appropriate formats within the CRDSS. This allows <br />the authors of the documentation to continue supporting the documentation, which benefits the <br />CRDSS by allowing the CRDSS to update to improved versions of the documentation (rather than <br />Mosaic <br />freezing a version that may become outdated). RTi anticipates that the use of and document <br />languages like HTML will become more important as access to information via the Internet increases <br />and because Mosaic is supported on UNIX workstations, Microsoft Windows, and Macintosh <br />computers. It is the hope of the consultant that more documentation products within the CRDSS will <br />use HTML as the master copy of the documentation. <br />Mosaic <br />Existing model manuals may not be easily transferred to the document format. For example, <br />equations that are part of the existing MODSIM WordPerfect documentation do not easily transfer to <br />other formats (nor do they easily transfer between PC word-processor software). Possible <br />alternatives in this case are to re-enter the equations in the desired document format, generate the <br />equation as a graphic that can be imported into other documents, or save the entire document in a <br />format that can be displayed on-line. Re-entering the equation will not be cost-effective because it <br />requires too much manual intervention that would have to be repeated each time the master <br />document changes. Saving equations as graphics is an option that is still being studied. Saving the <br />entire document in a format that can be viewed on-line can most easily be accomplished by saving <br />the document as a PostScript file. Public domain software and products from workstation vendors <br />(including SGI) are available to display PostScript files in WYSIWYG (What You See Is What You <br />Get) format. PostScript files viewed on the screen retain all of the information in the original <br />document (including graphics, equations, etc.); however, such documents may be more difficult to <br />read because the limited resolution of the screen cannot display very fine printing details. <br />RTi recommends that initial model documentation include as much valuable content as possible <br />without expending extensive resources on the reformatting of documentation. At a minimum, <br />documentation for each model will include a PostScript dump of the documentation that can be <br />viewed with a program and printed on a PostScript printer. For models that have hard-copy <br />documentation that is difficult to implement in the CRDSS (e.g., the USBR's CRSM and AOP <br />documentation), the minimum documentation for the CRDSS will be a UNIX man page with a <br />program overview and a reference to the hard-copy documentation. The core documentation will be <br />Mosai <br />tied together using a simple c home page, which may include graphics such as screen dumps <br />from the model interfaces. <br />The next iteration of documentation will be to develop more extensive hypertext documentation <br />Mosaic <br />within and will be pursued if funds are available. Public domain utilities for converting <br />wp2x <br />WordPerfect and FrameMaker to HTML (e.g., ) are being tested to determine their <br />effectiveness in automated translation of document formats. These utilities may allow existing <br />documentation to be implemented more effectively. The addition of content to documentation will <br />also be pursued based on the work during development of the system. The on-line documentation <br />should reflect the current state of the system. <br />The implementation of model documentation for the CRDSS will follow the guidelines specified in <br />Task Memorandum 1.05-12. The documentation for each model will be archived in the location of <br />2 <br />A275 06.29.94 1.17-1 Malers <br />
The URL can be used to link to this page
Your browser does not support the video tag.