NOAA Goes Live With New Forecasting Supercomputers
dcblogs writes "The National Oceanic and Atmospheric Administration (NOAA) Thursday switched on two new supercomputers that are expected to improve weather forecasting. The supercomputers are each 213 teraflops systems, running a Linux operating system on Intel processors. The U.S. is paying about $20 million a year to operate the leased systems. The NWS has a new hurricane model, Hurricane Weather Research and Forecasting (HWRF), which is 15% more accurate in day five of a forecast both for forecast track and intensity. That model is now operational and running on the new systems. In nine month, NWS expects to improve the resolution of the system from 27 kilometers to 13 kilometers. The European system, credited with doing a better job at predicting Sandy's path, is at 16 kilometers resolution. In June, the European forecasting agency said it had a deal to buy Cray systems capable of petascale performance."
I suspect if they removed the computers and installed windows in the offices of our local TV meteorologists we would get better short term forecasts. I've also decided that any precipitation forecast more than about 3-4 days out that doesn't involve a system as large as a hurricane is just a wild-ass guess*. Heck, even real time they're often wrong, the local guys are fond of reporting sunny all day while I'm actually looking outside at it raining.
*Well, unless you're in SoCal Mar-Dec, in which case "Sunny" is always the statistically correct answer, or Orlando/Daytona, where "It will rain at 3:45pm for 5 minutes" is always the statistically correct answer.
Is it just my observation, or are there way too many stupid people in the world?
HWRF runs at a much finer grid spacing than 27 or 13 kilometers. As I recall, the grid spacing is around 3 km in the inner nest. This is done to explicitly simulate the convection at the inner core of a tropical cyclone. This nest moves with the storm, and is embedded within a much larger domain. The upgrade from 27 to 13 kilometers actually refers to the GFS model. It's a spectral model that has a global domain. Other models that are regional (including the outer domain of the HWRF) need to know the conditions at their lateral boundaries, so they know what's moving into the domain. In the US, they typically use the GFS for their boundary conditions. I'm actually very skeptical of the need for upgrading the resolution of the GFS. That may have a role in improving GFS forecasts, but there have been studies showing that the initial conditions of the GFS are the real problem. The atmosphere is a chaotic system; that is, two similar initial states will diverge over time to produce two very different outcomes. In a study where the GFS was initialized with ECMWF initial conditions, the performance of the GFS improved. Hurricanes are typically steered by large scale features, which aren't necessarily going to be simulated better by using a finer resolution. It also doesn't address the initial conditions problem. I'm in favor of throwing more computing power at meteorology, but I'm not convinced it will solve the problems with the GFS.
"The system uses so much power that its emissions directly influence the weather on all continents and mars."
www.vanheusden.com - home of Multitail, HTTPing, CoffeeSaint, EntropyBroker, rsstail, bsod, listener, nagcon, nagi
Please use American measurements, like rods and furlongs for distance.
The summary is confusing two different models: HWRF and GFS. The HWRF model is a public model you can download and run, as long as you have ~20 GB of RAM free on your computer:
http://www.dtcenter.org/HurrWRF/users/overview/hwrf_overview.php
There is a public version of the GFS, but I'm not sure where. I'm mainly an HWRF developer.
Also, you can download GFS and HWRF forecasts in real-time (ie.: files less than 10 minutes after they're created by the operational NCEP WCOSS supercomputer) here:
GFS: ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gfs.*/
You want the files named gfs.t??z.pgrb2f* - those are the forecast files every 1-6 hours at 0.5 degree resolution.
The HWRF real-time data is here:
HWRF: ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/hur/prod/hwrf.*/
The *.hwrfprs_* files contain model fields. The *prs_n* are the 3km domain, prs_m are combined 9&3km, prs_p are 27km, prs_i is 9km and prs_c are combined 27:9:3km. The track files are *.atcfunix for six-hourly, *.3hourly for three-hourly and *.htcf for experimental per-timestep (5 second) information.
You can also get archived track files from a three season retrospective test of the GFS and various HWRF configurations here:
http://www.emc.ncep.noaa.gov/HWRF/tracks/
Formats of the track files contained within are described well on JTWC's website (the equivalent of the NHC for everything not near mainland US):
http://www.usno.navy.mil/NOOC/nmfc-ph/RSS/jtwc/best_tracks/
Actually, the high cost per year is because there are several stages of planned upgrades, intended to support the steady increase in resolution and data assimilation capacity of the various models. (Including a massive GFS upgrade next year.) The project, from the NCEP side at least, was completed five weeks early and under budget. The estimated savings, from shutting down the old overpriced Power6/AIX CCS cluster early, is about $1 million, and the switch to Intel/Linux will save taxpayer dollars in the long term. I know that's small compared to the national debt, but it isn't the usual government waste that you hear about, and I'm proud to say we're doing our part (even if most of the government isn't).
As for who is getting the money, have you ever heard the old adage "nobody ever got fired for buying IBM?" While this is somewhat of a Stockholm syndrome situation, I'm told IBM did manage to underbid everyone else this time, and the cluster mostly working, five weeks early. (Completely working would have bene nice, but you get what you pay for.) We've used creativity to work around the problems and get everything working with the cluster they gave us.