Written by Chris Goodell, P.E., D.WRE | WEST Consultants
Copyright © The RAS Solution 2014. All rights reserved.
“Flow or Temp time series date is not sufficient to run requested time window.” This one has been around for a while, but it just showed up again on the Facebook HEC-RAS User’s Group, so I thought I’d show the fix(es) here. This applies to the new beta version of 5.0, as well as previous versions of HEC-RAS that can run sediment transport.
When running a sediment transport model, if this error message pops up, there are at least three possible reasons.
1. Make sure you have both flow AND temperature time series data.
It’s easy to overlook the Temperature data, which can be entered in time series by pressing the “Set Temperature” button on the bottom left of the Quasi-Unsteady Flow Editor.
2. Make sure that the dates entered in the Sediment Transport Analysis window are in the format DDMMMYYYY and the times are in 24 hour format. Your dates and times should look like this:
Also, make sure you have your Windows Region and Language Settings set to English (United States). Sorry to my friends in other countries, but it’s just one of those things you have to do when running HEC-RAS. See here for more information on this..
3. And finally, HEC-RAS requires that your Quasi-Unsteady Flow Time Series data extend beyond the specified simulation time. In this example, our simulation time is exactly 24 hours, as shown in the Sediment Transport Analysis window above. That means our Flow Series Boundary Condition cannot have a total duration of exactly 24 hours. It must be something more than that. I usually just add 0.1 to the last duration entry and that will take care of the problem (see below). You could put any number in for your duration, as long as it is greater than (not equal to) the simulation time duration. This does not appear to be an issue with the temperature time series data (i.e. you can put exactly 24 hours for your temperature time series duration).
Thank you to Frederic Graf and Akhilesh Gupta for reminding us of this issue again on the Facebook User’s Group Site.