Laserfiche WebLink
<br /> <br />cycle began, the existing procedure had been that all of the old products from the <br />previous cycle were deleted from the CSU Real-time Forecast Web site. This <br />was to avoid confusion by users, who otherwise might not realize that when they <br />were examining a time sequence of products. the valid time might cross over <br />discontinuously from the new forecast cycle to the old cycle. (The model run <br />produces 2-hr forecasts out to 48 hours. The new 2-hr forecasts are posted right <br />after the 0000 UTC model run completes them.) However, particularly with the <br />slow runs, the deletion of the old cycle products resulted in no high-resolution <br />forecast guidance for the first day or so of the new cycle, until the new cycle <br />reached that far. <br /> <br />It was thus decided to keep the old forecast cycle's products until they <br />were superceded and over-written by each two-hourly increment of the new <br />cycle. In this way, the products valid at 36 hours in the old cycle (or 1200 UTC <br />on Day 2), for Instance, were retained to provide guidance at 1200 UTC on Day 1 <br />of the new cycle, until the new cycle's products were produced. To help the user <br />avoid the possible confusion of not realizing the discontinuity, prominent labels <br />were updated and displayed on each menu that give the initialization time of the <br />current cycle and how far out in the 48-hr cycle it has reached. Thus, any <br />products beyond that point were more easily recognized as being from the older <br />cycle, but were still available for high-resolution guidance. This change was <br />made beginning with the January 19, 2004 forecast cycle. <br /> <br /> <br />The real-time RAMS 0000 UTC forecast runs, originally intended to <br />constitute the set of control (no-seed) runs for the entire season, were <br />determined to be unusable for that purpose due to several problems that <br />became evident deep Into the cold season. The problems were traced to three <br />factors, two of which Involved overly warm soil temperatures that resulted in <br />too much surface sensible heat flux and low-level warming. One problem was <br />a soil initialization scheme that prevented the soil temperature from initializing <br />colder than aoe and the soil moisture from being initialized in frozen form, <br />when those conditions should have been allowed at high elevations deep into <br />winter. The second problem was a coding error with the thermal energy <br />content applied to soil, where sub-freezing soil improperly warmed rapidly to <br />aee when the slightest initial frost or frozen precipitation occurred in the <br />topmost soil layer. <br /> <br />The third problem was the use of an alternate horizontal diffusion <br />scheme that esu had used in previous winter seasons in order to avoid <br />runaway cooling at the lowesllayer that sometimes occurred with the standard <br />diffusion scheme. The alternate scheme was not strictly mass conserving, <br />however, and in many runs it apparently resulted in too much mass and <br />moisture convergence into the high country. <br /> <br />These three problems resulted in unrealistically warm low.level <br />(basically below ridge crest) temperatures and overestimates of precipitation in <br /> <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />. <br />4 <br />4 <br />4 <br />4 <br />4 <br /> <br />32 <br />