This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Travis, > Hello, > > A couple weeks ago I had emailed about ingesting our own WRF runs into EDEX. > I have now set > it up to automatically feed in our WRF grib2 files like an ldm would do. I'd > like to visualize > precipitation output in CAVE for some crude model performance analysis, but > the way that the > precip data is in the Product Browser is not consistent with any other > models. I would really > like to have a 3 hourly precip rate that I can step through (just like I can > for the GFS20 for > example), but the way that the precipitation data gets decoded by EDEX is > different. Inside of > the product browser, each hour's precip accumulation gets decoded to a > separate variable, i.e., > TP12hr, TP13hr, TP14hr, TP15hr, TP16hr, ... , TP36hr. Similarly, the TP3hr > for my 36-hour > forecast run only contains one frame valid for FH03. > > When I look at other models e.g., the GFS and the Euro (that I set up to > ingest automatically) > have a total accumulated precip over the model run (mapped as TP-GFS and > TP-ECMWF) as well as > a 3 hourly, 6 hourly, and 12 hourly that I can step through. Is there a way I > can set up EDEX > to decode my WRF data (and other models for that matter) like these two > models? > > Hopefully this explanation made sense. If it did not, please let me know! From our best understanding, model precip data (specifically) is something that AWIPS calculates as a derived product on the EDEX side. For some reason, it seems to not be consistent between model sources and is a complicated process. Unfortunately, we do not understand it well at all. The only place I could direct you would be the processing files for the existing models: /awips2/edex/data/utility/common_static/base/grib/postprocessing I'm sorry this is an area we do not have much expertise in. If you are able to make any progress please feel free to report back. Thanks. --Shay Carter She/Her/Hers AWIPS Software Engineer UCAR - Unidata If you're interested, please feel free to fill out a survey about the support you receive: https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform Ticket Details =================== Ticket ID: AMB-223808 Department: Support AWIPS Priority: Normal Status: Open =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.