[Manual] [Contents] [Prev] [Next]
"can't parse archive header for archive <name>"
There is something wrong with the top several lines of your flow archive. Check the header against a working flow archive and see if you can identify the difference; this warning message is almost always accompanied by an error message that will halt the Monte Carlo run.
"Dam abbreviation not found. The dam <name> can't be used."
The flow archive contains flow information for some dam that is not defined in your columbia.desc file. This is likely to be a dam quite far up the system (e.g. Albeni Falls). CRiSP.1 discards flow information for these dams.
"delay params: delay threshold <value> out of range (0<t<1) for <species>, adjusting."
The delay threshold must lie between 0 and 1, and cannot be 0 or 1. You have specified a value outside that range, and CRiSP.1 is changing the value to either 0.001 (if you specified a value less than 0) or 0.999 (if you specified a value greater than 1).
"elevation drop below depth in reach <name>, adjusting"
"free running tailrace (depth 1) at <name>"
You have drawn down a pool so that the upper depth, associated with the tailwater, has reached zero feet. CRiSP.1 will calculate how much of the pool has been rendered free-running and will apply the same algorithms for water flow and fish passage as it does in other free-running sections of the system. This is not an error: significant drawdowns will produce substantial free-running sections below dam tailraces.
"encountered EOF before end when parsing <name>"
This suggests that your data file is corrupted; the file ends in the middle of a piece of information. You will probably need to create a new data file or use a clean and well-formed copy of the original data file.
"insufficient flow at <segment>, adjusting loss"
CRiSP.1 insists that all segments have minimum flows; setting a flow to zero at some headwater will cause the model to issue this warning and reset the flow to the minimum flow by adjusting the loss in that segment. This should only happen if you have set an unrealistically low flow at some headwater.
"Missing one or more file names. I won't save the data for the blank file names"
You are trying to write a control file but have not specified file names for some parts of the data that is to be written. CRiSP.1 will write only the segments you have named; the rest will be lost. If you wanted to save those other parts, assign names for them as well and write it out again.
"No file extension on file name <file>. I am placing the name in the first blank spot", or
"Unrecognized file extension on file name <file>...."
The pieces of a control file have extensions that indicate what portion of data they represent, e.g. mydata.dam would contain the dam-related parameters. The piece you are trying to write lacks the proper extension; this should not happen. You can explicitly add the extension to the name and it should write out properly.
"Obsolete token. Data discarded. Separate into reach, forebay, and tailrace"
This is a special case. In old CRiSP.1 data files, predator density and activity coefficients were applied to the entire reach. More recent versions of the model separate each pool into three sections: the forebay, the tailrace, and the reach proper. Each segment has its own predator density and activity coefficient. See the list of data file tokens or write out a default data set to get the correct tokens.
"period data beyond last season day. Inaccurate spill possible at <dam>."
CRiSP.1 currently runs for 300 days, from the start of the year until Julian day 300. Your flow archive contains flow and spill descriptions that go beyond that date; as a consequence, when CRiSP.1 produces modulated flows and spills for the truncated period, there may be some error. Solution: curtail your archive to be 300 days long.
"reading old version <number> archive file! Consider creating archive with more recent crisppp."
The CRiSP Pre-Processor - crisppp - has evolved through several versions, beginning with version 0.7, and is now at version 1.0. The archive you are using was created using an old version of crisppp. It will almost certainly be a perfectly acceptable archive, but it may lack some information that later archives possess: for example, early versions of crisppp produced archives containing only flow, planned spill, and overgeneration spill, but later versions also include elevation data. This may be important to your application of the model.
"storage volume specified for dam <name> with no reservoir in description file"
You have attempted to create a reservoir in your data file without specifying its existence in the columbia.desc file; either remove the reservoir from your data file or add it to the columbia.desc file, using already-existing reservoirs as examples.
"token <name1> has been renamed to <name2>. Parsing."
"Obsolete token <name>. Discarded"
This warning informs you that CRiSP.1 no longer uses the same token name as it used to for some parameter; in the first case the model is parsing the old token as if it had been correctly renamed. If you subsequently write this file out to a file, it will contain the updated tokens. In the second case, the model can't figure out what the old token is supposed to be, or that token refers to a parameter no longer used; these data are simply discarded.
"unknown species <name>. Skipping."
Species must be named in the columbia.desc file; if you insert a new stock into your data file (e.g. "summer chinook") without also inserting the name at the head of the columbia.desc file, the model will ignore all information pertaining to that stock. Check both files to make sure you have been consistent in your naming convention (e.g. that it's not "summer chinook" in one file and "chinook summer" in the other).
"View failed, no variables (categories, indices) selected!"
"report tool: Data category <name> has variables (categories) set but no categories (variables)"
"report tool: View All failed, no data category has both variables and categories selected"
You attempted to view output from the report tool without correctly specifying what you wanted to see. Go back to the tool and make a more complete description of the data in which you are interested.
"You are missing one or more input files. I will parse as much as I can."
You are trying to read in a control file that is no longer complete. Check to see if you have deleted or moved some parts of that file, or if you have made a typing error in naming the file. CRiSP.1 will read whatever it can, but the pieces that are missing will revert to default values.
[Manual] [Contents] [Prev] [Next]
Columbia River Salmon Passage Model CRiSP.1.5 User Manual
Copyright © 1996, Columbia Basin Research. All rights reserved.
web@cbr.washington.edu