Running Your First Raven Model

This introductory module guides you through the steps to run your first Raven hydrologic model using the Irondequoit Creek watershed as an example. You'll learn how to prepare and organize input files and execute the model from the command line. Visit the Raven website to download the materials you will need. 📌 Key Topics Covered: How to set up and run a Raven model using the command line Organizing model input files for a lumped watershed configuration In a Raven hydrologic model, several input files work together to define the model structure, parameters, and forcing data.  modelname.rvi – Primary Model Input File Defines how the Raven model functions, including simulation duration, time step, routing method, and soil column representation. Specifies the hydrologic processes that redistribute water and energy between storage compartments. Lists the state variables, parameters, and output options. modelname.rvh – HRU / Basin Definition File Defines subbasins and HRUs, including number, properties, and connectivity. Assigns land use, vegetation, aquifer, and soil classes to each HRU for parameter generation. modelname.rvt – Time Series / Forcing Function File Specifies temperature, precipitation, and other environmental forcing at observation points (“gauges”). Can interpolate forcing to HRUs or link to gridded NetCDF data. modelname.rvp – Class Parameters File Contains most model parameters, organized by classes (vegetation, land use, aquifer, soil). Each HRU is assigned to one class per type, aiding calibration and parameter management. modelname.rvc – Initial Conditions File Provides starting values for all state variables in HRUs and subbasins. Can be generated from a previous run or left blank (zeroed), requiring a run-up period. When the Raven executable (Raven.exe) runs, it reads these input files to simulate hydrologic responses, producing output files such as hydrographs, watershed storage information, custom outputs, and error logs. The diagram below illustrates the flow from model inputs on the left to outputs on the right, showing how each file contributes to model setup, execution, and results analysis.