This types of flow charts are always a bit confusing. Hopefully I can simplify things. In the upper left, RiverWare is the starting point for generating a baseline and a comparative alternative for managing reservoir operations and deliveries within the hydrologic network. Output from RiverWare concerning flows, storage and irrigation deliveries is reformatted so the DSS can read it and is brought into the model on an aggregate page. RiverWare output is directly input to the SNTEMP model, which produces daily water temperatures at the hydrologic nodes for each of the five floodplain reaches (these a Jack Stanford’s floodplain reaches from his 2002 study). These temperatures are brought into the DSS aggregate page. Forget about this sediment transport link for the time being. The sediment transport model is still under construction by the BOR and we are not exactly sure how this is going to work.

The five “REACH” pages are set up identically and are designed primarily to calculate habitat time series statistics using the flows input from the aggregate page and habitat/flow functions contained in look-up tables. These functions were calculated using predicted hydraulic conditions obtained from the 2-D models converted to habitat metrics with HSC and reclassified as suitable habitat with GIS. Temperature data are also accumulated on these pages according to the biological hydroperiods set for each reach.

All of this information then goes back to the aggregate page and you are ready to generate output. So let’s take a look at that output.