What data are getting in LAPS? Check the LAPS GUI...
There is a graphical user interface (GUI) on AWIPS that can tell you what data (obs & model background) are making it into the LAPS analyses. This can be different from the obs that are plotted on the workstation due to timing, etc. To check the GUI, click on "Tools", then on "LAPS", and click on any of the 5 analyses of interest. In each case, you should be able to see the categories and lists of observations making it into the analysis. Verification statistics are also included for how well the analysis (and initial background field) fits the observations.
Ingest Flow Chart
The blue colored data are what we are using in AWIPS LAPS. The other data are being used in our "full-blown" LAPS and can potentially be added to AWIPS/LAPS if the data becomes available.
An overall description of raw data. and ingest processes. is in our README file.
Surface:
We are using METARS for the surface observations. LDAD and Maritime surface observations are also being used if available. There may remain some questions about whether LDAD obs are being processed by AWIPS in a timely enough fashion to make it into LAPS. Surface observations from mesonet, wind profiler, and GPS stations should all be getting into the surface LDAD files.The data paths for surface data are specified in 'obs_driver.nl'. There are three separate paths for METAR, LDAD, and Maritime files. Surface observations are now used from a time window between 15 minutes before and 15 minutes after the top of the hour.
In the past there have been some questions about bulls-eyes in various surface analyses, particularly the CAPE field. The CAPE is very sensitive to dewpoint and temperature, so some bulls-eyes are normally to be expected. The key is to look at and assess the dewpoint and temperature inputs to the CAPE. Some problems in the dewpoint/temperature have been related to the spline routine and erroneous observations making it past the QC. We have replaced the spline with a more robust "Bratsethian" style of Barnes successive correction. We are also improving the QC procedures and thresholds. More details are listed below for each AWIPS build.
Background:
We are using the RUC model as the default background, with a failover to Eta if RUC is not available. Some coastal sites may be better served by using Eta for the default; this can probably be done on-site by editing the 'background.nl' namelist file.
Satellite:
The satellite interface for AWIPS depends on (8-bit) image data only, (those acquired via the Satellite Broadcast Network). The satellite interface in "regular" LAPS is capable of this plus interfacing to GVAR full resolution image data (10-bit) and sounder radiance data (13-bit). More information regarding AWIPS satellite application can be found here.In terms of the analyses, the IR image data feeds into the cloud analysis as well as the surface temperature analysis. The VIS and 3.9u data (used in clouds and snow cover) is currently being developed over the next few builds (see below).
LAPS Satellite ingest processes the image closest to the top of the hour, up to a range of H-15 to H+15 minutes.
Radar:
The LAPS VAD wind interface (ingest_vad.exe) is currently inactive.The radar reflectivity data is utilized by the cloud analyses and QPE precipitation analysis.
We are currently utilizing low-level radar reflectivity data (Level-III RPG) for input into LAPS. The strategy is to process low-level reflectivity data in polar form into a NetCDF file that is readable by the LAPS ingest program 'remap_polar_netcdf.exe'. Ideally we prefer full volume (or layer composite) radar data for LAPS, though LAPS can function to a degree with the two-dimensional, single-radar input.
LAPS uses the low-level tilt scanned closest to the top of the hour, up to a range of H-20 to H+20 minutes.
In the future we hope to use multiple radars. Towards this end a mosaicing program is being implemented as part of the LAPS AWIPS suite to combine individual 'vrc' files generated for each radar using 'remap_polar_netcdf.exe' into a composite 'vrc'.
To improve ground clutter rejection, we hope to use either the DHS (Digital Hybrid Scan), or multiple low-level tilts.
In the more distant future, wideband (Level-II) reflectivity and velocity data would be attractive for use in AWIPS/LAPS. The additon of Doppler velocity data would improve the quality of the wind analysis (3-D and surface).
Wind Profiler/RASS:
We are currently interfacing to the WFO profiler data (WPDN 404 MHz network) via 'ingest_pro.exe'. Profiler data will be read in from the current hour's NetCDF file, if that file is created by :25 past the hour. If the file arrives later than :25 after then no profiler data gets in. The boundary layer 915 MHz profiler network interface is inactive. The RASS ingest also is inactive (ingest_lrs.exe). These can be activated if appropriate NetCDF data becomes available in the AWIPS database.
ACARS/Pireps:
ACARS should be functioning in build OB1 with voice Pireps following in OB2.
RAOB:
The interface to RAOB data (ingest_raob.exe) should be functioning as of version OB1. RAOBs, even if available, are sporadic so most hours LAPS runs would not see them being used within the +/- 1 hour data cutoff.
GPS:
LAPS uses GPS precipitable water data in the humidity analysis that is stored in NIMBUS/NetCDF files. There is a second local data (LDAD) NetCDF file that carries GPS data. This second format supplies GPS surface data to 'obs_driver.x' and the intermediate 'LSO' file. LAPS does not yet read precipitable water from the LDAD format, only the NIMBUS one. Therefore GPS precipitable water is not yet available for the default version of LAPS on AWIPS.
