The Columbia River Salmon Passage model (CRiSP.1) tracks the downstream migration and survival of migratory fish through the tributaries and dams of the Columbia and Snake Rivers to the estuary. CRiSP.1 describes in detail the movement and survival of individual stocks of natural and hatchery-spawned juvenile salmonids and steelhead through hundreds of miles of river and the major dams. Constructed from basic principles of fish ecology and river operation, CRiSP.1 provides a synthesis of current knowledge on how the major hydroelectric system in the country interacts with one of its major fisheries. Biologists, managers and others interested in the river system can use this interactive tool to evaluate the effects of river operations on smolt survival.
There are five major uses of the model:
There are two modes in which CRiSP.1 can be executed. Scenario Mode illustrates the interactions of model variables. Monte Carlo Mode, which is stochastic, provides measures of variability and uncertainty in predicting passage survival. Using Monte Carlo Mode, estimates of probability distributions for survival and travel time can be determined for any stock between any two points in the river system.
CRiSP.1 has advanced programming features including:
The model is designed to run on Windows 95/NT operating systems or Sun SPARC workstations running Solaris2.X operating system. CRiSP.1 has been tested in both environments.
CRiSP.1 was developed at Columbia Basin Research, School of Fisheries, University of Washington, under a contract from Environment, Fish and Wildlife, Bonneville Power Administration (BPA).
The model is being applied to the Columbia River. As a result, the files describing the river and release points of fish into the river are an essential part of the model. A list of references pertaining to model theory and calibration can be found in the Theory, Calibration and Validation Manual.
CRiSP.1 models passage and survival of multiple salmon substocks through the Snake and Columbia rivers and their tributaries and the Columbia River Estuary.
Map of Columbia and Snake Rivers
The model recognizes and accounts for the following aspects of the life-cycles of migratory fish and their interaction with the river system in which they live.
Fish survival through reservoirs depends on:
Fish migration rate depends on:
Fish passage through dams depends on:
Cross-section of a dam showing fish passage routes. Fish collected
in bypass systems are returned to the tailrace or transported downstream.
CRiSP.1 is one of several models describing the passage of juvenile salmon through the Columbia Basin system. The major mainstem passage models and their time steps are outlined below. All of these models describe fish survival through the river system but differ in the details included. The simplest model is PAM and the most complex is CRiSP.1.6. With increasing complexity, the other models fall in between. CRiSP.0 is close to PAM, FLUSH lies in the middle and CREM and RESPRED are in turn more complex.
Simple and complex models each have advantages and disadvantages and the choice depends in part on the types of questions being addressed. Simple models are easy to understand and do not require large amounts of data since they are generally developed to the degree of resolution of the available data. Unfortunately, since they are designed to fit existing data, the variables are identified from past studies and there is no formal process to assess if chosen variables are insignificant or the driving variables. Simple models, being empirical and based on existing data, typically fit the available data but it is not clear that they would still represent the system if the system were to change.
In general, complex models are based on underlying mechanisms which are inferred from analogous systems. As such, they often can be extended beyond the data of the system they are modeling. Mechanistic models are particularly useful for developing hypotheses that are to be tested through experimentation. A disadvantage of such models is that they require a considerable effort to understand and calibrate, and there is a chance that the underlying mechanisms may be misapplied or inappropriate, this can also be the case with simple empirical models.
The tags of "simple and empirical" vs. "complex and mechanistic" are, in fact, only points along a continuum. Even the simplest models have some underlying mechanism and complex models, at some level of detail, contain empirical descriptions in which the parameters have no mechanistic foundation and are applied because they fit data or a desired mathematical form. The level of detail at which a model switches to empirical formulations distinguishes its degree of mechanism.
All of the existing mainstem fish passage models leave out some variables which may be important. The simplest models, such as PAM and CRiSP.0, rely solely on flow to describe survival and are of limited value for investigating other factors. Although FLUSH and CRiSP.1.6 consider the effects of fish age on survival, none of the models considers differences in fish conditions, fish bioenergetics, or the river and tributary carrying capacities.
Version 1.6 of the CRiSP Model includes many updates, changes and new features. Yearly Input Data Files from previous versions of the model can be converted into the new version data files by reading the files into CRiSP.1.6 and writing the data out to your local system. We recommend using the CRiSP.1.6 calibrated values. Changes to the model in version 1.6 include improvements to the internal operation of the model and the graphical user interface (GUI). The following list highlights many of the improvements to the model.
The species and stocks of fish entering the river system are arbitrarily defined. Species are identified as:
Stocks are identified by their species, spawning stream, and season. The number of fish released at each site is identified on a daily basis. Each release group has a unique set of passage parameters and corresponding model results are tabulated separately.
Note. Wild and hatchery migrants do not necessarily need to be defined as separate stocks if separate tracking is not desired, but definition as separate stocks is required if you assign them different parameter values (e.g. different vulnerability to predation, swimming behavior, etc.). If you want to keep track of different stocks as different releases with the same parameters, CRiSP.1 tracks each release separately in both Monte Carlo Mode and Scenario Mode.
CRiSP.1 calculates arrival of all fish on each day to each river segment (a section of river between confluences, dams, or headwaters) before calculating passage of fish to the next downstream segment. With this set of arrival information, it is possible to assign rules for fish transportation based on a percentage of the total run that will arrive at a dam. Thus, CRiSP.1 moves fish downstream a segment at a time, adding smolts coming from tributaries or hatcheries on a daily basis. The number of fish leaving a river segment on any given day depends on:
Dam operations control important variables of CRiSP.1. The three major variables are daily total flows, spills, and fish transportation.
Dam passage survival depends on the pathway fish take through a dam. At all dams, fish arriving at the forebay can pass over the spillway or through the powerhouse. The fraction of fish entering the spillway depends on:
Fish entering the powerhouse can pass through the turbines or be guided by traveling screens. The propensity of a population to be guided is represented by a fish guidance efficiency (fge) which can be set constant or varied over a season for each project and population. (See FGE and FGE Equation sections for more details.) Mortality depends on the pathway chosen which accrues for spillway passage, collection, and turbine passage. Dam activities are calculated on a six hour basis and summed over a day to provide a daily fish input to the next reservoir.
Bypassed fish at specified dams may be transported in barges or trucks to any point in the river downstream of the collection site. Bypassed fish not transported are released into the tailrace. CRiSP.1 removes transported fish at a dam, computes a mortality, and releases fish at the transportation site at a later time as determined by a transportation velocity. Whether collected fish are transported depends on rules developed to simulate actual transportation decisions. Transportation factors are set with the Transport Tool and include:
Survival and migration of fish in CRiSP.1 can be modeled in two modes: Scenario Mode and Monte Carlo Mode.
Scenario Mode runs one year with as many releases as desired. It can be used to gain insight on the effects of changes in system parameters on the survival and migration of fish during a single water year. In this mode, natural unregulated inflows are specified. These flow into the mainstem rivers and storage reservoirs at headwaters. System operation and fish biological parameters can be varied stochastically according to user specifications.
Monte Carlo Mode runs CRiSP.1 with as many releases as desired for one or more combinations of water year and system operations. The main variable changed in each run is river flow. Flows are specified at the project (dam), not headwaters. In each run, a different flow regime and other model parameters are used. Fish survival is determined for each run and the distribution of survivals from all runs provides an estimate of the probability distribution of survival under the specified conditions. Flow is generated from runs of the hydroregulation models maintained by the Army Corps of Engineers (HYSSR) and the BPA (HYDROSIM). The hydroregulation models use historical water data and a projection of electrical demand to simulate system flows, which are designated flow.archive files. These files give period-averaged flows at operating projects which are modulated by CRiSP.1 to represent daily flows. CRiSP.1 uses the modulated flows along with yearly input data files describing the system operations and fish biological parameters to produce histograms of survival.
Interaction of hydroregulation model and CRiSP.1 in Monte Carlo Mode
CRiSP.1 integrates a number of submodels that describe interactions of isolated components. Together they represent the complete model. These elements include submodels for: fish travel time, reservoir mortality, dam passage, total dissolved gas supersaturation, and flow/velocity relationship. The structure of CRiSP.1 allows you to select different formulations of these submodels at run time. In this sense, CRiSP.1 can be configured for simple interactions or it can be set up to consider many ecological interactions. CRiSP.1, as it is presently calibrated, has an intermediate level of complexity: age dependent travel time is implemented, but other age dependent factors are switched off. A brief description of submodels follows.
Travel Time
The smolt migration submodel, which moves and spreads releases of fish down river, incorporates flow, river geometry, fish age and date of release. The arrival of fish at a given point in the river is expressed through a probability distribution. All travel time factors can be applied or they can be switched off individually, resulting in a simplified migration model.
The underlying fish migration theory was developed from ecological principles. Each fish stock travels at a particular velocity relative to the water velocity. The relative velocity can be set to vary with fish age. In addition, within a single release, fish spread as they move down the river.
Predation Rate
The predation rate submodel distinguishes mortality in the reservoir, and the forebay and tailrace of dams. The rate of predation can depend on temperature, diel distribution of light, smolt age, predator density, and reservoir elevation.
Gas Bubble Disease
CRiSP.1 incorporates a separate component of mortality due to gas bubble disease which is produced by total dissolved gas supersaturation. The mortality rate is species specific and is adjusted to reflect the effect of fish length and population depth distribution.
Dam Passage
Timing of fish passage at dams is developed in terms of a species dependent distribution factor and the distribution of fish in the forebay, which can change with daily and seasonal light levels. Fish guidance efficiency can be held constant over a season or it can vary with fish age and reservoir level.
Transportation Passage
Transportation of fish at collection dams is in accordance with the methods implemented by the U.S. Army Corps of Engineers. The start and termination of transportation and separation of fish according to species can be determined for any dam under the same rules used to manage the transportation program. Time in transportation and transportation mortality can also be set.
Total Dissolved Gas Supersaturation
Total dissolved gas supersaturation, resulting from spill at dams, can be described with gas production equations which are an empirical fit of spill data and monitoring data collected by the U.S. Army Corps of Engineers. Alternatively, supersaturation can be described by other empirical models (not calibrated) or by a mechanistic submodel that includes information on the geometry of the spill bay and physics of gas entrainment.
Flow
Flow is modeled in two ways: it can be specified at dams using results of system hydroregulation models or it can be described in terms of daily flows at system headwaters. When flow is described in headwater streams, the flow submodel generates a random set of seasonal flows that have statistical properties in accordance with the available water over a year. In this fashion, the model statistically reproduces flow for wet, average and dry years. The user controls the mainstem river flows by adjusting the outflow of the storage reservoirs within their volume constraints.
Water Velocity
Water velocity is used in CRiSP.1 as one of the elements defining fish migration. Velocity is determined from flow, reservoir geometry and reservoir elevation.
Reservoir Drawdown
Reservoir elevation is set on a daily basis from elevation information in the system hydroregulation models or from user specified files. As water levels drop, part of the reservoir may become a free-flowing stream.
Stochastic Processes
CRiSP.1 can be run in a Monte Carlo Mode in which flows and model parameters vary within prescribed limits. In this mode, survival to any point in the river can be determined as a probability distribution.
Geographical Extent
CRiSP.1 can describe a river to any desired level of detail by changing a single file containing the latitude and longitude of river segments, dams and release sites. In its present configuration, three river description files are available. One file contains an abbreviated river map with the major tributaries and about thirty representative release sites, although more can be added easily. The two other river description files contain drawdown alternatives. See the River Description File section for more information.
The CRiSP.1 submodels are individually calibrated. Thus CRiSP.1 was not directly calibrated from mark-recapture survival studies. Instead, such studies provided a check on the calibrations of the individual mechanisms of the model (model validation). Notes on the submodel calibrations are detailed below.
Travel Time
The travel time submodel was calibrated for subyearling chinook, yearling chinook, and steelhead using tagging data from the entire river system and over the entire migration season. Two separate calibration processes were applied: one to measure the spread of fish as they moved through the reservoir, and the other to measure the change in relative migration velocity with fish age. The first used marked, individual stock releases over a short period of time, and the second used marked and recaptured fish over entire seasons.
Predation Rate
Predator-prey interactions in CRiSP.1 were calibrated with information from predation studies in John Day Reservoir and information on predator densities for each of the major reservoirs.
Gas Bubble Disease
The rate of mortality due to gas bubble trauma was calibrated from dose-response studies conducted in both field and laboratory conditions.
Dam Passage
Diel passage elements of CRiSP.1 were calibrated from hydroacoustic and radio-tagging studies at dams. Fish guidance efficiency and spill efficiency were calibrated from a number of studies at a variety of dams. Fish guidance efficiency can be set to change with fish age and reservoir level or it can be set constant over the year. Mortalities in dam passage were determined from mark-recapture studies at dams.
Transportation Passage
Separation of large and small fish in transportation was applied from general information on the efficiency of the separators in the transportation facilities at dams. A transportation mortality was determined for each species, based on transport-benefit studies. In addition, time to transport fish through the river system was specified.
Total Dissolved Gas Supersaturation
Total dissolved gas supersaturation models were calibrated with data from the Army Corps and includes information collected in the 1992 drawdown study in Lower Granite and Little Goose reservoirs, as well as monitoring data from recent aggressive spill programs.
Flow
Headwater flows in Scenario Mode were calibrated from information on stream flows provided by the U.S. Geological Survey. In Monte Carlo Mode, the modulators of the period average hydroregulation model flows were calibrated against historical daily flow records at dams.
Water Velocity
Water velocity requires information on reservoir and geometry. The relationship between geometry and elevation and free stream velocities were determined from Lower Granite Reservoir drawdown studies.
Stochastic Processes
The ranges for variables used in the Monte Carlo Mode have been calibrated to available data in the above mentioned studies.
The cross-platform Help provides instructions for using Columbia River Salmon Passage model (CRiSP.1) on both Unix and Windows 95/NT operating systems. Any differences in the commands used or the operation of CRiSP.1 between the operating systems are noted in the text. Help is designed to meet the needs of a wide variety of users, from a novice user of Solaris2.X or Windows 95/NT operating systems to programmers familiar with the C++ language in which the CRiSP.1 model was written.
CRiSP.1 is designed to run on a Sun SPARC workstation running Solaris2.X or on a personal computer running Windows 95/NT operating systems. CRiSP.1 should run as expected on Windows 98, 2000, ME, and XP. The first step is to install the model on your computer.
CRiSP Passage information and files are available to users via the World Wide Web (web). Questions about CRiSP.1 can be sent to the CRiSP Passage email address listed below.
http://www.cbr.washington.edu/crisp/crisp.htmlcrisp-passage@cbr.washington.educrisp1.exe icon or launch crisp1.exe from a Run dialog box.setup.exe icon.crisp1.exe.
gunzip r1.6.0.tar.gz
tar -xf r1.6.0.tar
There are four files required to run CRiSP.1 in both Scenario and Monte Carlo modes:
columbia.desc: defines the river segments, locations of dams, and release sitescrisp1.exe: CRiSP.1 executable codebase.dat: a database file that can be read into CRiSP.1flow.archive: A file of flows, spills and reservoir elevations (elevations are given in HYSSR files) initially generated from a hydroregulation model such as SAM, HYSSR or HYDROSIM. Outputs of these models are converted to CRiSP.1 compatible flow files using a preprocessor.In the simplest file arrangement, all files are placed in the same folder (or directory). For example, the configuration below shows these files contained within the folder named CRiSP Passage. By default, output files are written to the directory from which CRiSP.1 was executed (the CRiSP.1 "home directory"). On Windows 95/NT operating systems, this is the source directory for crisp1.exe. When saving files to the local system, you can override the default directory to specify any output directory. On the Unix system, the files can be written out to any directory for which the you have write permissions. For more information about these files and other input and output files, see the CRiSP.1 Files section.
Windows 95/NT installation of CRiSP.1
There are several ways to start CRiSP.1 using the graphical interface from your Desktop.
.Wait for the CRiSP.1 Graphical User Interface and River Map to appear. Basic information about CRiSP.1, model parameters, and running CRiSP.1 are covered in later sections.
Main Panel and River Map
To start CRiSP.1 from a command prompt, the model must be in the current directory (or, on Unix only, in the path). At a command prompt, type a command with the following syntax:
crisp1 [-l{wmrd}] [-bsmi] [-r river_desc] [-f data_file] [-o output_file] [-c output_control_file] [-u]
The arguments delimited by "[ ]" are all optional and can be given in any order. If an argument is not present, the default value is used.
-l{wmrd} controls the logging level. Five separate classes of logging messages are defined: Errors which are always logged, Warnings, Messages, Raw output, and Debug output. By default, Warnings are logged and the others are not. If -l is given, then the default is ignored and the characters which follow define what is logged. For example -lwm causes Warnings and Messages to be logged, -l causes nothing (except Errors) to be logged, -ld causes only Debug output to be logged, and -lr causes Raw output to be logged.-bsmi controls the running mode. b selects Batch Mode (the default is Graphical User Interface mode). s selects Scenario Mode. m selects Monte Carlo Mode (which is the default in Batch Mode). i selects Realtime Mode. The letters can be combined in various ways and not all need to be included. -bsi would select Batch Realtime Scenario Mode. -b selects Batch Monte Carlo Mode (since Monte Carlo Mode is the default for Batch Mode). Batch Monte Carlo Mode runs depend on the existence of a .crisp-alts file which specifies which alternatives to run.realtime.dat unless an alternate yearly data file is indicated with the -f flag. Running in Realtime Mode will create a realtime subdirectory with several default files, of particular interest is realtime.real file which is the output file. For Realtime Monte Carlo mode runs, a flow file named flow.archive must reside in the run directory. In Realtime Monte Carlo Mode, the model does not depend on the .crisp-alts file to determine which alternative and which files to use.-r river_desc specifies the name of the river description file. The default file is columbia.desc.-f data_file specifies the name of the yearly data file. The default file is base.dat.-o output_file specifies the name of the parameter data file to output at the end of a batch run. This option can only be used in conjunction with the -b argument. Only one -o option is allowed for any given batch run. The extension of the output filename determines what parameter data used during the model run will be written to the file. See the Model Parameter Data Files section for further details. For example,name.dat writes out a parameter data file with all information in itname.rls writes out a parameter data file with only the release informationname.ctrl writes out a control file with "include" directives and the 8 parameter data subset files which contain the whole database between them.-c output_control_file gives the name of the parameter data configuration file to be used for the entire batch run. This option can only be used in conjunction with the -b argument. Either a file of type .dat or .cnf may be specified. If this option is given, the program as it starts up first reads columbia.desc, then it reads the "output_control_file" and turns on the Lock Output Settings feature, then it reads the yearly input data file (ignoring any output settings contained therein), and then it runs the model in batch mode, as specified by the other command line arguments. This option is intended to facilitate control of data output in batch mode processing.-u indicates that a summary.alt# file should be written for each alternative run, exactly as if the "Write Supplemental Data" check box had been checked in the GUI Monte Carlo window. Data written to the file is based on the output settings in the yearly input data file(s) specified in each alternative. This option can only be used in conjunction with the -b{mi} argument.Example commands that open the CRiSP.1 Graphical User Interface
crisp1
crisp1 -lmw -r columbia_drawdown.desc -f new.dat
crisp1 -f test.dat
Example commands that run CRiSP.1 in batch mode
crisp1 -b -o batch.ctrl
crisp1 -b -c batch.dat
crisp1 -bsi -f realtime.alt.dat
crisp1 -b -u
The CRiSP Passage model can be executed in batch mode for either Monte Carlo or Scenario runs. See the Starting from the Command Prompt section for command options. The following are special instructions on running in batch mode for both Unix and Windows 95/NT operating systems.
On the Unix system, batch mode runs can be executed from the command prompt using any of the options detailed in the Starting from the Command Prompt section. There are a few special considerations for running CRiSP.1 in batch mode on Unix systems. The CRiSP.1 Unix distribution includes the program crisp1bat, which is the simulation engine of CRiSP.1 without the graphical user interface. Using this program, you can run CRiSP.1 in batch mode without having to set the DISPLAY environment variable. This makes it possible to run the CRiSP.1 model in batch mode from a dial-up connection or from a detached process, i.e. left running after logging off the workstation. The crisp1bat program uses the same command prompt arguments as crisp1, except that the -b is assumed.
Example commands
crisp1bat -o batch.ctrl
crisp1bat -c batch.dat
crisp1bat -u
There are a few special considerations for running CRiSP.1 in batch (non-graphics) mode on Windows 95/NT systems. These derive from the architecture of Windows 95 and Windows NT, which make sharp distinctions between MS-DOS-based programs and Windows-based programs.
If you are running CRiSP.1 from the MS-DOS prompt, you have two choices: 1) redirect the program's standard and error output streams to text files or 2) have standard and error output streams write to the MS-DOS shell.
Example command to redirect the output streams to text files
crisp1 -bs -f base.dat >output.txt 2>error.txt
Example command to redirect both of the output streams to the same file
crisp1 -bs -f base.dat 1>output.txt 2>&1
To let the batch mode program's output streams write to the MS-DOS shell, you must use a second program called crisp1b that runs crisp1 in batch mode and is equivalent to crisp1 -b.
crisp1b -s -f base.dat
For this to work properly, the files crisp1.exe and crisp1b.exe must reside in the same directory.
Warning. It would be a mistake to run the crisp1b program and then redirect its standard output streams.
columbia.desc)base.dat)flow.archive)columbia.descThe River Description File (columbia.desc) contains all the information necessary to define the physical river system from the ocean to the various headwaters. This includes latitudes and longitudes of all possible release sites, dams, and river segments as well as many of the physical parameters of these features. All menus and input and output tools automatically configure from the information in this file. See the Technical Details section on the River Description File Structure for details on file structure, rules of construction, and parameter definitions. The Parameter Glossary contains definitions of the parameters and tokens found in this file.
The columbia.desc file is an ASCII file that you can edit and contains the following information:
The default columbia.desc file contains an abbreviated description of the Columbia Basin river system with about thirty fish release points and major dams. Some rivers in the basin are not represented in this map (for example, Imnaha River or Grande Ronde River).
Additional River Description Files are also available in the CRiSP.1 distribution. They have been modified to reflect changes in the river that could occur under certain proposed management actions. The file columbia_snakedraw.desc does not have any of the Snake River dams in it. This simulates a Snake River drawdown in order to make the Snake River free-flowing. It has four dams removed that are in the default columbia.desc file: Lower Granite, Little Goose, Lower Monumental, and Ice Harbor dams. The file columbia_drawdown.desc is similar to columbia_snakedraw.desc. In addition to the removal of the four Snake River dams, it also has the John Day dam removed. This represents the most drawdown being considered. Five dams are removed that are in the default columbia.desc file. A River Description File can only be read when CRiSP.1 is initially started. In order to use one of the alternative files, you must start CRiSP.1 from a command prompt with the -r flag. See the Starting from the Command Prompt section for more information.
Columbia River map showing potential release sites, dams, and rivers
base.datThe Yearly Input Data File (base.dat) contains all model parameter data for a single year run. If no other yearly input data file is specified when CRiSP.1 is started, the model will initially read the file base.dat. The CRiSP.1 Graphical User Interface menus are used to create and modify the parameter data for a run or for storage in data files. The data can be saved as either a single file or as a group of parameter data files corresponding to predefined data groupings. These files can be read into the model individually or in a group prior to a run. See the Reading Data into CRiSP.1 section for further details. A file containing all model parameter data is designated .dat and is referred to as a yearly input data file.
Parameter Data File Name Extensions
dat: all model parameter databeh: parameters related to fish travel time and mortalityres: predator density in reservoirsspill: spill schedules at all damsflow: headwater flows, losses, elevations, storage reservoirsdam: all parameters related to dam operationrls: all parameters describing fish releasesriver: headwater temperature and river parameterscnf: runtime settings and output settingsThe Model Parameter Data Files section discusses the data and file name extensions in further detail. A yearly input data file containing all the data used in CRiSP.1 may be over 1M in size, depending on the number of releases and tributaries defined in the river. Typical data files are about 200K in size. See Technical Details section on the Yearly Input Data File Structure for details on file structure, rules of construction, and parameter definitions. The Parameter Glossary contains definitions of the parameters and tokens found in this file.
CRiSP.1 contains eight predefined model parameter data file name extensions. The model parameter data files are subsets of the data in CRiSP.1. All data in CRiSP.1 can be contained in these eight parameter data file types. All eight files combined would contain the same information as a Yearly Input Data File (.dat). By using Save As and a predefined extension, specific model parameter data groupings can be saved to a file for future use. In a similar manner, specific model parameter data groupings can be read into CRiSP.1 by using Open. See the Reading Data into CRiSP.1 section for further details. All eight parameter data files can be written out simultaneously using a Control File.
The following is a list of data parameters stored in each file as determined by the file name extension. Following each extension is a short description and in parentheses is the GUI menu location for editing these parameters.
.rls: release information (Release).res: reservoir parameters (Reservoir).beh: behavior parameters (Behavior).flow: flow parameters (Flow).dam: dam guidance and mortality factors (Dam).spill: spill information at each dam (Dam).river: river information (Reservoir).cnf: config information (Run)A Control File allows you to write out or read in a set of parameter data files. In this manner, subsets of model parameter data can be replaced while other elements are unchanged. Control files are designated by the extension .ctrl.
Control files contain a list of Model Parameter Data Files which are identified in the lines below the Control File line (see file sample). You can save to disk all eight parameter data files with the same base name as the Control File by selecting Control Files (*.ctrl) for Save as type (Unix users will need to specify the file name extension) from File
Save As.
When reading control files into CRiSP.1, the parameter data files specified in a Control File can have different base names. By editing the Control File, you can mix parameter data files from different alternatives and sessions. You can use any text editor to edit a Control File. Each specific combination of parameter data files listed in a Control File can be read into CRiSP.1 by selecting the control file you want from FileOpen.
Sample Control File with a list parameter data files from different alternatives.
#===================================================# # CRiSP Control File CRiSP v1.6.0 (Solaris 2.x) # #Written on Fri Jun 25 11:53:20 1999 #===================================================# version 6 include session.beh include session1.res include session3.spill include session.flow include session2.dam include session.rls include session4.river include session.cnf
flow.archiveThe Flow Archive File (flow.archive) contains flow, spill and elevation data generated from hydroregulation models such as SAM, HYSSR or HYDROSIM. The flow archive file can be used in Monte Carlo Mode as the source for flow, planned spill, and elevation. Information contained in a flow.archive file includes:
See Technical Details section on the Flow Archive File Structure for details on file structure and parameter definitions.
A CRiSP.1 run generates and stores various information in output files and directories. Without making any selections with Output Settings (Run Menu), a model run in either mode generates travel time and survival information at the Estuary. All other data output must be specified prior to the run in Output Settings or specified in the data files used during the run. The following files and directories result from model runs and are stored in the CRiSP.1 home directory.
summary.dat: An output file that contains results from the most recent run of CRiSP.1 in the Scenario Mode. This includes for each selected passage point:summary.alt#: An output file that contains results from the most recent run of an alternative in Monte Carlo Mode if the "Write supplemental data" check box is selected in the Monte Carlo window or if the -u command line option is used in batch mode. Run results written to this file are determined by the Output Settings specified in the yearly input data files used in each alternative.altern#: A Monte Carlo Alternative directory that contains three output files. The files should only be modified by using the Monte Carlo tools to make any changes. The files are as follows:altern#.alt: name of flow archive, names of input files in an alternative, number of games and years in the archive file, and number of times each archive flow file year is usedaltern#.ind: internal index file generated by CRiSP.1altern#.out: output information used in Monte Analysis.By default, data stored in CRiSP.1 is replaced by data read from a file, if and only if, that data item appears in the file. For each appearing data item, this is referred to as a "replace" operation. For example, this allows you to read in new flow information from a .flow file without affecting the rest of the data currently stored in CRiSP.1.
There are three types of data that are exceptions to this rule: spill schedules, transport records, and releases. For these three types of data, a decision is made as to whether to delete existing data prior to reading the file. In all cases and all modes, once data reading has begun, multiple specifications of transport, spill, or release data are merged with each other.
In interactive (GUI) mode, CRiSP.1 performs Replace or Merge operations according to file extension and user response.
Depending on the file name extension, Replace or Merge operations are as follows:
.dat, .ctrl, or unknown.spill, .spi.dam.rls.beh, .res, .flo, .flow, .riv, .river, .cnfFiles which are "included" from other files are not subject to the above determinations (see the CRiSP.1 Parser section for information on file includes). Only the top-level file to be read (not included) will have its extension examined. The above list then holds for all data read from that file or from any file subsequently "included."
In batch mode runs, a replace operation is always performed. All spill, transport, and release data are first deleted, and then replaced with data appearing in the file. All other data appearing in the file is replaced as per the standard default. Note that in batch mode, since the pre-existing data consists of hard-coded defaults which may be questionable, it is advisable to make sure that files used in batch mode runs provide full coverage for all parameters.
Interactive operation of CRiSP.1 is through a graphical user interface (GUI) using a two-button or three-button mouse. CRiSP.1 standard features and tools are detailed in the following sections.
CRiSP.1 uses standard window features found on Windows 95/NT and Unix systems for opening, closing, resizing, and shrinking windows to an icon. If you have questions, please refer to your operating system and software documentation.
The following are definitions of mouse operations as used in this documentation.
Both the mouse and the keyboard can be used to open and select from the menus and submenus found in CRiSP.1.
Using the mouse, you can open windows from menus and submenus.
Using the keyboard, you can open windows from menus and submenus.
Open context-sensitive help information by clicking 
or 
in a window. The context-sensitive help and additional information is accessible from Help in the Main Panel.
Throughout the model, CRiSP.1 uses the concept of two level editing and display. The data being displayed on the screen may be different from the data in the underlying database. A red dot 
in each corner of a window indicates that the data being displayed is different from the data currently stored in the model and that changes have not been applied to the underlying database, yet. For changes to take effect, click Apply or Apply All. Modifications that have not been applied can be discarded by clicking Reset or Reset All.
Note. For example, if you open windows for all three dams for Flows / Reservoirs and modify the Outflow at each dam, you can apply the changes in two ways. If you click Apply in the Chief Joseph Dam Outflow window, that will only save the changes made to Chief Joseph Dam Outflow. If you click Apply All in any of the three dam Outflow windows, that will save changes made to Outflow at all three dams.
All input windows in CRiSP.1 contain all or a combination of the Standard Commands.
Powerhouse Schedule window (default) and before applying changes
In general, any number of windows of the same type can be active at the same time - just select the same menu item several times to create several copies of the same type of window. For input windows (dialogs and editable graphs), it is possible to have multiple windows displaying the same data at the same time. If the data is changed in one window, the others will update automatically to reflect the changes.
Yellow dots 
will be displayed in the corners of all output graph windows when any input data has been changed, but the model has not been re-run to create new outputs. Yellow dots do not imply correlation between the data displayed in the output window and the changes to model input.
To demonstrate this, run the program in Scenario Mode, and the open a Passage graph for the Estuary and the VVar window. After you click Apply in the VVar window, the passage graph will display yellow dots. VVar has changed, but passage has not been recalculated. Now run the model again. Passage is now up to date with respect to model inputs, so the yellow dots disappear. Please take note that yellow dots would also appear on a TDG Saturation output graph, even though VVar does not influence total dissolved gas.
Yellow Dots in Passage for Estuary window
Slider Input windows are one type of data input windows found in CRiSP.1. Red sliders represent parameter settings and are changed using the mouse or the keyboard as described in the following sections. CRiSP.1 variables that incorporate sliders include:
As shown below, there are several formats for Slider Input windows. The Unregulated Headwater Flow Maximum window is an example of the Slider Input window in its simplest form. The Migration Rate Variance window contains a "tab" list where the list of variables is longer than allowed for one screen (ten variables) and is accessible by clicking on the tabs (labeled A, B, etc.) at the top of the window. Also illustrated in this window is the concept of setting Mean, Low and High values for each variable. The Dam Predation Probability window illustrates a Slider Input window containing time-specific, dam-specific and species-specific settings.
Various Slider Input windows
There are three ways to edit the value of an individual slider.
All changes made to slider values need to be applied by clicking Apply / Apply All / OK before the values will take effect.
Slider Input window and Slider Value dialog box
Some Slider Input windows contain a tab list (variable list is longer than ten items), click on a letter tab to access a portion of the list and edit the desired slider as directed above. Some Slider Input windows contain Mean, Low, and High value sliders which are separate entities and are edited separately.
There are several Slider Input windows which involve setting time-specific, dam-specific and species-specific values for each slider, and there is one Slider Input window which involves setting reach-specific and species-specific values.
Parameter values can be set individually for each species at each dam by selecting the desired species from the species menu, selecting the desired dam from the dam menu, and then following the directions above. If you make multiple changes to dam and species parameter settings, click Apply All to save all the changes made. Parameters can be grouped across Time (T), Dam (D) or Reach (R), and Species (S) by selecting the appropriate check boxes to the right of the slider. See the Edit Multiple Slider Values Simultaneously and Edit All Slider Values Simultaneously sections for directions.
Dam Predation Probability window.
Editing multiple slider values simultaneously uses the "group" concept. For the majority of Slider Input windows, there is only one column of check boxes on the right side of the slider labeled G. There are several Slider Input windows in CRiSP.1 which involve setting time-specific, dam-specific or reach-specific, and species-specific values. These Slider Input windows have check box columns labeled T (time), D (dam), R (reach), and S (species). For Slider Input windows containing sliders for mean, low and high values, sliders are grouped for mean, low or high values separately.
All changes made to slider values need to be applied by clicking Apply / Apply All / OK before the values will take effect.
Multiple sliders grouped
Editing all slider values simultaneously uses the "group" concept. For the majority of Slider Input windows, there is only one column of check boxes on the right side of the slider labeled G. For Slider Input windows containing sliders for mean, low and high values, sliders are grouped for mean, low or high values separately. There are several Slider Input windows in CRiSP.1 which involve setting time-specific, dam-specific or reach-specific, and species-specific values. These Slider Input windows have check box columns labeled T (time), D (dam), R (reach), and S (species).
All changes made to slider values need to be applied by clicking Apply / Apply All / OK before the values will take effect.
All sliders grouped with top check box
Slider Input windows that involve setting time-specific, dam-specific or reach-specific, and species-specific values include the following features:
Editable Graph windows allows rapid input and visualization of data that varies from day to day. Open Editable Graph windows by making a selection from a menu. Depending on the settings in the Mouse Tool, some Editable Graph windows can be opened from the River Map by clicking on a dam, reach or headwater. CRiSP.1 variables that can be set with a Editable Graph window include:
In all cases, Julian day is given as the horizontal coordinate (X-axis) with day zero corresponding to December 31. The vertical axis (Y-axis) is defined below the graph, naming the parameter and its unit of measurement.
Actively update the graph display for dam, reach, or headwater as the pointer moves over the location on the River Map.
Fix scale to current settings in order to visually compare graphs.
Increase vertical graph scale. Or right-click in the upper-half of graph (2). This doubles the vertical scale.
Decrease vertical graph scale. Or right-click in lower-half of graph (3). This halves the vertical scale.
Round scale up to next significant number.
Display graph with continuous line connecting the data points (default view).
Display the graph with horizontal lines connecting the data points.
Display the graph as hollow bar chart.
Display graph as solid bar chart.
Group several graphs together to simultaneously change the scale when using Ymax, Ymin, , , , or .
Editable Graph window
There are three ways to edit the values in a Editable Graph window.
to update the display list with the new values and redraw the corresponding graph. to update the display list with the new values and redraw the corresponding graph.All changes need to be applied by clicking Apply All / Apply / OK for changes to take effect.
Opens Save dialog box to save data points to a text file.
Opens Print dialog box to print graph to a selected printer. Opens context-sensitive Help for the active graph window variable.Schedule Tool windows allow for keyboard input of data by time periods in days or hours. Schedule Tool windows occur two ways in CRiSP.1. Every Editable Graph window includes a Schedule button which opens a companion Schedule Tool window for editing the data. In addition, CRiSP.1 contains Schedule Tool windows that exist separately from Editable Graph windows, for example, Powerhouse Schedule (Dam Menu).
to update the display list with the new values and redraw the corresponding graph.You can define a period to be a single day or a range of days. A single value can be applied to a range of days even if values are already specified for the days. Use the steps outlined above (create a new period) to create a new range of days.
to update the display list with the new values and redraw the corresponding graph.Schedule Tool features and functions
Schedule Tool window
Julian Day Output windows allow visualization of data calculated by CRiSP.1. The viewing features are the same as the Editable Graph; however, the Julian Day Output window has no input features. Open Julian Day Output windows by making a selection from a menu. Depending on the settings in the Mouse Tool, Julian Day Output windows can be opened from the River Map by clicking on a dam or reach. CRiSP.1 includes the following dam and reach specific Julian Day Output windows:
Julian Day Output window
Actively update the graph display for dam, reach, or headwater as the pointer moves over the location on the River Map. Fix scale to current settings in order to visually compare graphs. Increase vertical graph scale. Or right-click in the upper-half of graph. This doubles the vertical scale. Decrease vertical graph scale. Or right-click in lower-half of graph. This halves the vertical scale. Round scale up to next significant number. Display graph with continuous line connecting the data points (default view). Display the graph with horizontal lines connecting the data points. Display the graph as hollow bar chart. Display graph as solid bar chart. Group several graphs together to simultaneously change the scale when using Ymax, Ymin, , , , or .
Closes the Julian Day Output window. Opens Save dialog box to save data points to a text file. Opens Print dialog box to print graph to a selected printer. Opens context-sensitive Help for the active graph window variable.Equation Input windows allow you to view and edit equation settings and parameters which are, in effect, submodels of CRiSP.1. The response of the equation to the parameters over the possible range of the independent variable is illustrated in the equation window as each parameter is changed. Note that for equation inputs, if you alter an equation and wish to use that altered equation in subsequent model runs you must click the Apply button to activate it, otherwise the model will revert to the previously-displayed equation and values.
Equation name | Independent variable | Dependent variable migration | Julian day | migration rate in miles/day spill | % river spill | % fish passage with spill tdg saturation | spill in kcfs | % tdg sat above 100% gas mortality | % tdg sat above 100% | % mortality/day population density vs. depth | depth (ft) | density, % of population/ft fge | fish age | fish depth parameters transportation mortality | water particle travel time | % transportation mortality
Equation Input window
Equation Input features and functions
Equation Input windows contain all or a combination of these features and functions.
The Graphical User Interface of CRiSP.1 contains the Title Bar, Menu Bar, Toolbar, Status Bar, and River Map.
Main Panel of CRiSP.1
Open/Read a parameter data file into the model (see Reading Data into CRiSP.1 for details). Save parameter data to a file (see Model Parameter Data Files for details on file types). Print Map.
Display or hide River Map.
Display or hide Latitude/Longitude (LatLon) Grid.
UnZoom one level of zoom stack for the River Map.
Run model in Scenario Mode.
Cancel a run in either Scenario or Monte Carlo Mode.
Open Mouse Tool to redefine mouse button functions on the River Map.The River Map identifies river segments, dams, headwaters, and release sites as determined by the columbia.desc file. The majority of model variables, such as river flow or fish passage, can be accessed from any site on the map by positioning the pointer on the location and clicking a mouse button (Mouse Tool settings determine which windows open). The River Map contains the following features and functions:
Potential Release Site
Existing Release Site
Dam, Potential Transport Site
Existing Transport Site in the Toolbar or select UnZoom from the View menu.
River Map with river segments, dams and release sites
The File menu contains general model functions and features.
Selecting FileOpen opens a file selection dialog box to read data files into the model. You can use this menu option to open any data file in the proper format, either manually created or saved from CRiSP.1. You can revert to all default settings and parameter values for CRiSP.1 by using this menu option to open a Yearly Input Data File (.dat). In addition, the Open command is represented by in the Toolbar. Several parameter data files can be read into CRiSP.1 simultaneously by using a Control File.
Selecting FileSave As opens a file selection dialog box to save part or all of the current database to a single file or to multiple parameter data files. The data files use a file name concatenated with predefined extensions (described in the Model Parameter Data Files section) identifying the type of data to be written out to that file. All the parameter information can be written out to separate data files by using a Control File. In addition, the Save As command is represented by in the Toolbar.
The Save As function allows you to store model parameter changes, i.e. parameter values that have been set with the various input parameter tools, on disk for reuse. This gives you the flexibility to manipulate and store all data used in CRiSP.1 except flow archive data. Each parameter data file can be written separately by naming the file and choosing from the Save as type selection menu or specifying the appropriate data file extension. Currently, the Save as type selection menu is available for Windows 95/NT only.
Selecting FilePrint Map opens a printer control dialog to print the River Map. In addition, the Print Map command is represented by in the Toolbar.
You can define the function of the mouse buttons when used on the River Map by selecting FileMouse Tool. In addition, the Mouse Tool command is represented by in the Toolbar. Location-specific output windows can be opened by placing the pointer on the desired location on the River Map and clicking the appropriate mouse button. The Status Bar displays which Dam, Reach, or Headwater is active. The exact function of the mouse button depends on where the pointer is located, which button is pressed, and how the functions have been assigned. For example, On Release can be set to open a Release Tool or to have No Operation; the default setting opens a Release Tool window with a right-click on a Release Site. Four categories of selection are available: On Dam, On Reach, On Release, and On Headwater.
The actions of each mouse button are changed by selecting the desired function from each category. Any changes you make take effect immediately and do not need to be applied. The Middle Button selections are provided for a three-button mouse; the settings are unavailable if you are using a two-button mouse.
Mouse Tool identifies mouse button functions on the River Map
Selecting FileMessage Log opens or restores the Log window. The Log window provides a number of messages from model runs. CRiSP.1 will alert you in the Log window if model operations encounter unexpected or incorrect model parameters. Error messages that warn of data problems that will cause CRiSP.1 to stop are always displayed in the Log window. You can choose which other types of messages will be displayed by choosing one or more of the options from the Logging menu in the Log window.
Please send email to "crisp-passage@cbr.washington.edu" if you have questions about any of the messages you get when running the model.
Log window features
summary.dat) and 2) any data requested by making selections in the Output Settings windows before run execution.columbia.desc file by checking if flows and cross-sectional area of segments are reasonable.Sample output showing the beginning of a Scenario Mode run summary
transportation started at Lower Granite Dam, day 92
transportation stopped at Lower Granite Dam, day 300
transportation started at Little Goose Dam, day 92
transportation stopped at Little Goose Dam, day 300
transportation started at Lower Monumental Dam, day 94
transportation stopped at Lower Monumental Dam, day 300
transportation started at McNary Dam, day 160
transportation stopped at McNary Dam, day 300
CRiSP1 Summary Output File
Mon Jun 21 10:51:58 1999
Scenario Mode
No average flows were calculated for this simulation.
Statistics fields: first day, last day, total passage, mean day
median day, mode day, std.dev day, avg.flow
bypass out, spillway out, turbine out, transport out
total in, bypass in, spillway in, turbine in, transport in
The preceding line was repeated 2 times.
Release: Dworshak Species: Steelhead Stock: Generic Start date:
119 Released: 1192503
Survival Below Lower Granite Pool
Passed: 1078314
Survival: 90.4%
stats: 120 165 1078314.38 127.03 126.33
125.00 3.45 0.00 0.00 0.00 0.00 0.00 1179277.88
0.00 0.00 0.00 0.00
Selecting FileExit discards all unsaved changes and quits the CRiSP.1 program. If you have made changes to parameter values and settings in CRiSP.1 that you want to use at a later time, you should first save your changes to the appropriate parameter data file or save the whole database as a Yearly Input Data File (.dat). See the Save As section for further information on writing out settings and parameter values.
The View menu contains functions related to the display of the River Map.
Selecting ViewUnZoom clears one level of the River Map zoom stack. In addition, the UnZoom command is represented by in the Toolbar. This action can also be accomplished by clicking on an undefined area on the River Map. See the River Map section for more details.
Selecting ViewGrid turns on or off the display of the latitude / longitude (latlon) grid on the River Map. The default setting for CRiSP.1 is to display the latlon grid. In addition, the Grid command is represented by in the Toolbar.
Selecting ViewMap turns on or off the display of the River Map. The default setting for CRiSP.1 is to display the River Map. In addition, the Map command is represented by in the Toolbar.
The Release menu provides access to the Release Tool and its companion graph window, the Release Schedule. By opening these windows, you can create, modify, or delete releases. On the River Map, designates the location of possible releases as defined in the columbia.desc file and designates the location of existing releases as defined in a Yearly Input Data File (.dat) or a .rls file.
Selecting a release site from ReleaseNew opens the Release Tool and its companion graph window, the Release Schedule, for creating a release at this site. The list of possible release sites is determined by the specifications in the River Description File (columbia.desc). See the Release Tool section for further details on creating, editing, and deleting releases.
Selecting ReleaseRelease Tool opens the Release Tool window and its companion graph window, the Release Schedule. In these windows, you can control release parameters including the timing and numbers of fish released and their level of smolt development. You can save your release specifications to a Yearly Input Data File (.dat) or a .rls file for subsequent use (see Save As).
Details on creating, editing, and deleting releases are covered in the following sections:
New - Opens the Release Tool and editable Release Schedule window for the selected site. After a new release is created (see Create New Release section) and applied, the River Map and the Existing releases site list will automatically update to show the newly created release.Release Tool: Opens the Release Tool and editable Release Schedule window. or on the River Map (unless you reconfigure the Mouse Tool).
After a new release is created and applied, the River Map and the Existing releases menu will automatically update to show the newly created release. On the River Map, if there where no previous releases specified at the release site, the release icon will change to the existing release icon .
Release Tool window
After an existing release is deleted and applied, the River Map and the Existing releases menu will automatically update to reflect this change. On the River Map, the release icon will change to the possible release site icon if there are no other releases specified at that release site.
Parameters for individual releases are set in the Release Tool window. Multiple releases can be identified for any site. Setting release parameters uses the Release Tool window and the Release Schedule graph window.
Release Tool window
Release Tool features and functions
Open the Release Schedule window, companion to the Release Tool window, by opening the Release Tool window. See the Open Release Tool section for details. In the Release Schedule window, you can change the number of fish released and the release range (the number of days over which the release is spread) following the Release Start day set in the Release Tool window. The range of the release and the number of fish released is displayed using Julian Day in the Release Schedule window. Please note that you are not actually setting release numbers to occur on specific days. CRiSP.1 will ignore attempts to set part or all of the release range before the Release Start day. After setting the range of the release, if you change the Release Start day in the Release Tool window, the whole release range will shift in respect to the change in that date (the length of the release range will remain the same). For example, if the range of the release is five days and the Release Start day is adjusted in the Release Tool window, the release will remain spread over five days. If you make changes in release counts or the number of days of release, you must click Apply for changes to take effect.
This is an Editable Graph window.
Release Schedule window, the Release Tool companion window
The Reservoir menu allows modification of predator densities, water temperature at the headwaters, and several global river parameters.
Selecting ReservoirReach Predator Density opens a window for setting predator densities by species for each river segment. Densities are given as number of northern pikeminnows per square kilometer of reservoir, excluding the tailrace and forebay (set in DamPredator Density). This measure, based on full pool dimensions, is effectively a measure of the relative number of predators in a river segment. A segment is defined as a section of river between river elements (such as dams and confluences). Predation mortality in CRiSP.1 is related to predator abundance, predator temperature response, and a predator activity coefficient. These factors combine to determine a predation rate which is applied to the smolt population on a time-step basis. To use these parameter values during a run, select Gas and Pred Mortality as the Mortality Model in RunRuntime Settings.
This is a Slider Input window. Click on the letter tabs to page through the Reach list.
This Slider Input window includes a menu for selecting by Species. You can group sliders by: Reach (R) or Species (S).
Reach Predator Density window
Selecting ReservoirPredator Distribution Coefficient opens a window for setting the predator distribution coefficient of the predator density/volume interaction for each river segment. The main purpose of the predator density/volume interaction is to properly scale the effect of initial predator densities on predation rate during reservoir drawdown. To use these parameter values during a run, turn on predator density / volume interaction in RunRuntime Settings.
This is a Slider Input window. Click on the letter tabs to page through the Reach list.
Predator Distribution Coefficient window
Selecting ReservoirReach Gas Theta opens a window for setting the mixing parameter for dissolved gas in a specified reach. Gas Theta determines the rate of mixing between the gas levels in the left-bank and right-bank flows of the river (facing downstream). These flows often have different levels of gas upon exiting a dam and become more mixed as the river flows downstream. The mixing rate is with respect to time and is set by default to be 0.075 (mile)^-1, which leads to roughly 95% mixing after 40 miles. A value of zero for Reach Gas Theta results in no mixing between the flows and a value of 10 allows for complete mixing between the flows.
This is a Slider Input window. Click on the letter tabs to page through the Reach list.
Reach Gas Theta window
Selecting ReservoirGas Distribution opens a graph of the level of dissolved gas in a reach from the start of the reach to the end. Both the left-bank flow and right-bank flow levels are marked on the same graph, with the left-bank flow in red and the right-bank flow in blue. These flows often have different levels of gas upon exiting a dam and become more mixed as the river flows downstream. The total amount of gas in the reach also decreases due to the dissipation in the reach. A slider for the graph is provided to change the Julian day for which gas is displayed. The X-axis is the distance downstream in miles from the start of the reach, mile 0. The Y-axis is the gas level measured in percent above 100, the equilibrium level. For example, if saturations vary between 100% and 110%, the Y-axis will range from 0 to 10.
This window emulates an Equation Input window, but it is display only.
Gas Distribution window
Selecting a Dam from ReservoirTDG Saturation > 100%Dam opens a histogram of the total dissolved gas (tdg) level exiting the dam for viewing only. This corresponds to the tailrace dissolved gas level. Tdg saturation for both the powerhouse flow (red) and spill flow (blue) levels are marked on the same graph. These flows often have different levels of gas upon exiting a dam because of the gas production from spill. Consult the table below to determine whether the spill side is left or right, looking downstream, at a specific dam. Histograms of the daily tdg level are displayed in percent above 100, the equilibrium level. For example, if saturations vary between 100% and 110%, the Y-axis will range from 0 to 10.
DAM spill side
Chief Joseph right
Wells left
Rocky Reach left
Rock Island right
Wanapum right
Priest Rapids right
McNary right
John Day right
The Dalles right
Bonneville right
Dworshak left
Hells Canyon right
Lower Granite right
Little Goose right
Lower Monumental left
Ice Harbor right
This is a Julian Day Output window.
TDG Saturation > 100% for Ice Harbor Dam
Selecting a Reach from ReservoirTDG Saturation > 100%Reach opens a histogram of the level of total dissolved gas (tdg) exiting the reach for viewing only. Tdg saturation for both the left-bank flow (red) and right-bank flow (blue) levels are marked on the same graph. These flows often have different levels of gas upon exiting a dam because of the gas production from spill. As the water flows downstream, the level of total dissolved gas decreases due to dissipation across the air-water surface. For reaches directly above a dam, this corresponds to the forebay dissolved gas level. Histograms of the daily tdg level are displayed in percent above 100, the equilibrium level. For example, if saturations vary between 100% and 110%, the Y-axis will range from 0 to 10 with the Julian date on the X-axis.
This is a Julian Day Output window.
TDG Saturation > 100% for Columbia above Snake Confluence
Selecting a Dam from ReservoirWater TemperatureDam opens a histogram of water temperature at the dam for viewing only. Water temperature is set on a daily basis in the headwaters. River temperatures in downstream segments are computed according to the fractions of the incoming flow which are derived from different headwaters in the segment and the temperature of the headwaters on a given day.
This is a Julian Day Output window.
Water Temperature for Dworshak Dam
Selecting a Reach from ReservoirWater TemperatureReach opens a histogram of water temperature in the reach for viewing only. Water temperature is set on a daily basis in the headwaters. River temperatures in downstream segments are computed according to the fractions of the incoming flow which are derived from different headwaters in the segment and the temperature of the headwaters on a given day.
This is a Julian Day Output window.
Water Temperature for Clearwater River
Selecting a Headwater from ReservoirHeadwater Temperature opens a window for setting water temperature for the selected headwater. Headwater temperature is specified on a daily basis. Daily water temperature at a headwater is read in to CRiSP.1 as input from the Yearly Input Data File (.dat). This window can be opened by right-clicking on a headwater on the River Map (unless you reconfigure the Mouse Tool).
This is an Editable Graph window.
Headwater Temperature for Clearwater Headwater
Selecting a Reach from ReservoirVelocity opens a histogram of the daily river velocity in miles per day for the reach for viewing only. The river velocity through a reach is calculated based on water elevation, bathymetry, and the daily flow level in the segment. Bathymetry data is read in to CRiSP.1 from the River Description File (columbia.desc).
This is a Julian Day Output window.
Velocity for Columbia Gorge
Selecting ReservoirRiver Parameters opens a window for setting several parameters that are applied throughout the river system and do not depend on species or day. The model is fairly sensitive to changes in these parameters; caution is recommended when making changes to these parameters.
This is a Slider Input window.
River parameters window
The Behavior menu allows you to set coefficients that model the rate of migration and survival. These parameters are species-specific and are applied uniformly in all reservoirs.
Predation coefficients effect the rate of predation activity by northern pikeminnows on smolt for a given predator density. The coefficients are species specific and are defined separately for reaches, dam forebays and dam tailraces. Predation mortality in CRiSP.1 is related to predator abundance, predator temperature response, and a predator activity coefficient. These factors combine to determine a predation rate which is applied to the smolt population on a time-step basis.
BehaviorPredation CoefReach Activity opens a window for setting the predator activity coefficient which scales the m