CRDSS_Task1_05-29_PCAccessOfCRDSS

Home Browse Search

definite danger that the programs developed for the CRDSS, if not maintained properly, will multiply into different variations. This is the classic problem with public domain software: open access to the source code allows anyone to ?improve? on the product and market the improved product. A strong maintenance plan will allow the improvements to be incorporated into the master copy of the code which can then be distributed to users. If such a plan is not implemented, then improvements to the CRDSS will be more difficult to make available to users because they will not be using official copies of the software. Products that are Produced for PC Users One of the biggest unknowns in providing PC access to the CRDSS is that no firm guidelines exist detailing the products that PC users expect from the CRDSS. If PC users expect to be able to run most of the CRDSS applications on their PC, then they will be disappointed because PC technology simply does not provide enough functionality. However, if PC users would like to query the database, access a CRDSS workstation, and/or retrieve the results of analyses performed on a workstation, then there are options available. The identification of products is being further studied in the User Involvement Program (see Task Memorandum 1.05-27). RTi would like to explore the issue of using a PC spreadsheet as one of he primary tools for PC access to the CRDSS. Data from the CRDSS database could be retrieved onto the PC using one of the communications methods discussed in this memorandum and could then be pulled into a standard spreadsheet for viewing. For example, time series data (or program output) could be retrieved in a standard ASCII format. The PC user could pull that information into a spreadsheet and plot the data. A macro for creating the plot could be written by the CRDSS development team or by the user (any such work done by users would hopefully be incorporated into the CRDSS knowledge base for distribution to other users). The use of the PC in this scenario allows the user to implement a procedure that is familiar and widely used a nd allows CRDSS team members to concentrate on developing the core functionality of the CRDSS. The products produced for PC users must be clearly identified before work to create those products is initiated. This is important for the CRDSS because a desired ?product? may not be a simple thing; it may require that the user be an intimate part of the solution procedure. For example, if the desired product for a user is the release flows from a reservoir, then a graph of the data (or the time series data needed to produce the graph) may be sufficient. However, if the user wants to perform separate analyses to generate such flows, then the user either needs to have access to the model, or the user's concerns need to be reflected in the results that are distributed. Because the State currently maintains a database that is accessed by water users, the consultant recommends that the basic access features of that database be available from the CRDSS database. For example, if users are able to retrieve historic diversions from the existing database, then such capabilities should be available from the CRDSS database. If this is not a goal of the State, then a concern exists that the CRDSS database will not be fully supported and utilized by users. The consultant is aware that the State's database was previously maintained at Colorado State University and was accessible by both State personnel and private consultants via modem. Although this system was not particularly ?high-tech? and was perhaps difficult to use, the ability of all water users to access the information was a bonus. RTi suggests that any investigations in determining users' needs in accessing the CRDSS database address whether a user has previously used the database at CSU and is currently using the State's database. 5 A275 06.29.94 1.05-29 Malers