Thanks for the clarification Andy - I wasn't aware of all of those changes, and that makes a difference in how we create our forecasts!
In my opinion I think the team must be publishing these changes to procedure and reasoning behind it in a central location so that all forecasters are kept up-to-date on all of these changes. As someone who is enthusiastic about FB/PoWT and has followed the project closely, even I feel like there's just so much going on and changing constantly that it can be difficult to know how to handle different weather scenarios. The webinars are good, but I'm not sure if all were even recorded (is there a comprehensive list?), and some of these changes now contradict things like the FAQ here on Vlab and some of the initial documentation. The change you mention about the Previous being used in the top-down grids in the December update isn't even listed on the Development Tracker spreadsheet. I understand and appreciate the fast development cycle, but I'm just afraid that if I as a proactive user who searches for the latest info am struggling to keep up with all the changes, I can't imagine how those new to the whole PoWT/FB concept must feel. This leads to collaboration issues, too, since not all forecasters are caught up on all the latest changes.
Could the CRGMAT/FB group please consider creating a central, up-to-date source for documentation that includes information on both code that changed, reasoning for the changes, and impacts to how we create our forecast based on those changes? I suggest a "Living Release Notes" Google Doc or something of that nature that can be updated with each new release on changes.
