Marshall Knox, an environmental scientist on the supply and demand assessment team, demonstrated how to download, set up and run the LSPC hydrology model for the Navarro River in a prerecorded presentation and live walkthrough.
Knox said the steps he demonstrated for the Navarro River “will be applicable to all watersheds once the models are released for those additional watersheds.” He told attendees the model requires a Windows operating system (Windows 10 or higher) and that “our team has experienced runs that take about 1 to 2 hours on average,” adding that runtime varies with user hardware.
The demonstration covered where to obtain the model files (a zip folder hosted on the supply-and-demand GitHub), how to extract and organize files for shorter file paths (desktop or C: drive recommended), and how to place the LSPC executable and the Navarro folder so the inputs and outputs are correctly located. Knox recommended at least 10 gigabytes of free storage for the Navarro River model and noted that more complex watershed models could require additional space.
Knox showed how to open the application and addressed a common Windows security prompt: right-click the executable, select Properties, and check the Unblock option when Windows Defender flags an unknown program. He then demonstrated loading climate input data from the included Access database by selecting File → Get from database in the LSPC application and verifying that hydrology and irrigation controls populated correctly and the interface displayed a “ready” status.
Participants were shown how to confirm or change the output folder in the left toolbar so model results write to the intended directory. Knox described the two ways to start a run—clicking the run button in the toolbar or choosing File → Run the model—and pointed out the progress bar that reports elapsed time, estimated time remaining and which climate date the model is processing. He said output files will appear in the Navarro LSPC output folder when the run completes.
After the run demonstration, Knox passed the presentation to Akash, who was introduced as the next presenter and will discuss model validation and performance checks.
The presentation included instructions for attendees on how to use Zoom’s Q&A feature to submit questions. The session did not record any formal votes or policy actions; it was a technical demonstration and handoff to validation work.
Next steps: Akash will present model validation procedures and any attendees’ technical questions can be submitted via Zoom Q&A.