Forums (Forecast Builder)

Back

Forecast Builder Bug

MS
Michael T Stavish, modified 3 Years ago.

Forecast Builder Bug

Youngling Posts: 12 Join Date: 9/20/12 Recent Posts

Hi,

Passing along an issue identified by one of my forecasters and our ITO. Please let me know if you can identify what the problem is.

 

- I ran forecast builder normally with the end time toggled to extended in step one. The tool ran properly with all grids compiling properly. A key thing to note though is that I set the finalize and P-type to run automatically.

- Then, we got talking about Temps during an east wind period and decided we needed to make some edits after FB ran. We made these edits and I went to use FB to re-compile the hourlies. 

- This is where the issue occurred. It started when I set the time range to start at "highlighted time range" and end at "highlighted time range", turning off the Populate step, I had the Analyze/adjust step set to manual, and the Finalize step set to automatically run. The P-type step was also set to auto run and all others were turned off. After continuing past step one and re-calced the hourlies based on Max/Min values, I would run into a problem where the non-3 hr grids were not filling in on the finalize step. 

- To fix this, we tried setting the finalize step to manual. After calcing Ts from Max/Mins we clicked the finalize step (again, in its manual setting) and it calced and filled in the hourlies as it should have.

- So again, the bug seems to be when the auto-run feature is turned on and the end time is set to "highlighted time range" instead of  "Extended".

 

Thanks,

Mike

 

 

JT
Justin Titus, modified 3 Years ago.

RE: Forecast Builder Bug

Padawan Posts: 33 Join Date: 10/24/15 Recent Posts

Mike,

I'm in CR and was unable to replicate the issue even when changing my config to utilize the simplified time range option. I then went into service backup for your office and again was unable to replicate when repeating the steps your described. I'm going to have one of our team members from WR try to test this in case there's some other config difference causing this issue.

 

Thanks for reporting this to us!

Justin Titus

ForecastBuilder Technical Working Group