NCEP Home > NCEP Central Operations > Systems Integration Branch > Realtime Monitor
Data Deficiency Troubleshooting Guide
DATA DEFICIENCY TROUBLESHOOTING GUIDE
Data Type Categorical Index:
Data Type Mnemonic Index:
Advanced troubleshooting techniques for
decoders
data (for NCEP only)
Advanced utilities to monitor ingest of satellite
data (for NCEP only)
Surface Data Types
SYNOP (Manual and automatic synoptic reports):
SYNOPM (Manual and automatic mobile synoptic reports):
SYNOPR (Restricted synoptic reports (WMO Res 40) manual and automatic):
Flow path: GTS data from many sites worldwide => NWSTG -- TNC => CCS
Many of these data are constructed automatically at TOC using 6-hourly
metar data from "first order" stations as input. If flagged for deficiency,
check with TOC Tech Control for possible decoder or comms line problems.
If 6-hourly (00Z, 06Z, 12Z, 18Z) metar data are deficient at the Gateway,
then synop data can be expected to be deficient. Many synopm data come from CMC.
If deficient, check SNCN19 CWAO.
METAR (Aviation surface based observations):
Flow path: GTS data from many sites worldwide => NWSTG -- TNC => CCS
These data are collected regionally and disseminated by ASOS data acquisition
systems (ADAS). If flagged for deficiency, check NAWIPS, AWIPS, and the
TOC "metar" program in order to determine the extent of the deficiency
such as 'only Canada missing'. Check with AMOC who should be aware of any
ADAS problem, then report your findings to TOC Tech Control.
SLPBG (Sea level pressure bogus, aka PAOB):
Flow path: GTS data from Australia => NWSTG -- TNC => CCS
These non-critical data originate from Australia under WMO headers UXXS(01-05) AMMC.
Check these bulletins in FADD for evidence and report to TOC. These bulletins
normally post twice a day around 06Z and 18Z. Request TOC to contact
Australia only if deficiencies persist for more than two model cycles.
Upper Air Data Types
DROPW (Dropwinsonde data):
Flow path: GTS data usually from TPC or USAF (CARCAH) or occasionally from non U.S.
sources => NWSTG -- TNC => CCS
If expecting some, and they do not show, check with CARCAH or TPC and find out what WMO
bulletin header was used. Check with TOC Tech Control for any comms break.
RAOBF (Fixed land rawinsonde data):
Flow path: GTS data from many sites worldwide => NWSTG -- TNC => CCS
If flagged for deficiency, check NAWIPS (Family of Services (FOS)),
bulletin header USUS50 in FADD, OSOTG DATA program, and AWIPS in effort
to isolate break in data flow. Reports from U.S. stations are normally
disseminated through AWIPS before reaching the Gateway and other users.
Report findings to TOC Tech Control. Also, call PMB data flow specialists
if you suspect a data flow problem or DbNet alert problem. Or contact Jeff
Ator if you suspect a decoder problem.
RAOBM (Mobile land rawinsonde data):
RAOBS (Ship based rawinsonde data):
PIBAL (Free balloon observations):
Flow path: GTS data from many sites worldwide => NWSTG -- TNC => CCS
In the unlikely event these data types are flagged for deficiency, check
with TOC Tech Control for any line problems.
Aircraft Data Types
ACARS (Automated MDCRS ACARS aircraft data):
Flow path: GTS data from ARINC => NWSTG -- TNC => CCS
These data are distributed from ARINC, many of which are distributed through the Leesburg link.
ACARS will often be flagged for deficiency during times of normally light air
traffic such as early Sunday and Monday mornings and holidays.
If it is flagged when normal or greater air traffic would be expected, check
bulletin header IUAX02 KARP in FADD to see if any recent bulletins were
made. Then query TOC Tech Control for an explanation. They may contact
ARINC or Leesburg for assistance in troubleshooting.
ACARSA (Auto MDCRS ACARS aircraft data (ARINC) via AFWA):
Flow path: GTS data from ARINC => AFWA => NWSTG -- TNC => CCS
These data are similar to ACARS except they are channeled through AFWA on their
way from ARINC to NWSTG. Therefore, if ACARSA is flagged for deficiency
when ACARS is not deficient, AFWA should be the first agency to query for any
problem.
AIREP (Manual AIREP format aircraft data):
PIREP (Manual PIREP format aircraft data):
Flow path: GTS data from many worldwide reporting sites => NWSTG -- TNC => CCS
Reporting sites include AWC,
FAA CWSUs, and international centers. If flagged for deficiency, check a sampling
of AWIPS pils nnnPIR000 where nnn is the node identifier, or a sampling of UBUS
bulletins in FADD. Then query TOC Tech Control for any line troubles from FAA,
WMSCR, Leesburg, etc.
ASDAR (Automated AMDAR format ASDAR/ACARS aircraft data):
EADAS (E-ADAS - European ASDAR/ACARS acft data from BUFR):
Flow path: GTS data from Exeter (Bracknell) => NWSTG -- TNC => CCS
These data are received from Exeter and are the European counterparts
of the ACARS data described above. If flagged for deficiency, check bulletin
headers UD(EU,AS,NT,NA,AF)02 EGGR and IUAD01 EGGR in FADD. NCEP normally receives
30 to 40 such bulletins per hour. If indeed no or few recent bulletins, contact
TOC Tech Control, and TOC will probably contact Exeter to discuss and resolve the problem.
The E-AMDAR system (EADAS1 and backup EADAS2) at Exeter processes these bulletins.
Data loss may result when migrating flow from primary to backup or vise versa.
Stewart Taylor and Bruce Truscott are the E-ADAS specialists at Exeter.
RECCO (Flight level reconnaissance data):
Flow path: GTS data usually from TPC or USAF (CARCAH) or occasionally from non U.S.
sources => NWSTG -- TNC => CCS
If expecting some, and they do not show, check with CARCAH or TPC and find out what WMO
bulletin header was used. Check with TOC Tech Control for any comms break.
Radar and Profiler Data Types
NXRDW (NEXRAD Vertical Azimuth Display (VAD) winds):
RADW25 (NEXRAD radial winds superobs, level 2.5 - ORPG):
RADW30 (NEXRAD radial winds superobs, level 3 - NIDS):
RD2R(00-23) (NEXRAD reflectivity UTC hours 00-23, level 2 - GTS):
RD2W(00-23) (NEXRAD radial wind UTC hours 00-23, level 2 - GTS):
Flow path: GTS data from U.S. NEXRAD sites => NWSTG -- TNC => CCS
GPSPW (GPS integrated precipitable water):
Flow path: GPSPW data from NOAA/ESRL/GSD (formerly FSL)
=> NWSTG -- TNC => CCS
If flagged for deficiency, check bulletin ISXT40 KBOU in FADD.
Deficiencies may flag Big Brother. Check BB for additional clues.
Tech Control may call gpsmet support or the
ESRL/GSD Forecast Application Branch (FAB).
PRFLR (Wind profiler data from NOAA/NWS/OPS12):
Flow path: GTS data from NOAA/NWS/OPS12 => NWSTG -- TNC => CCS
If flagged for deficiency, check bulletin IUPT43 KBOU in FADD.
Deficiencies may flag Big Brother. Check BB for additional clues.
Then have Tech Control check with NWS/OPS12.
PRFLRB (Cooperative Agency Profiler (CAP) winds):
PRFLRP (CAP winds decoded from PILOT (PIBAL) format):
Flow path: GTS data from NOAA/ESRL/GSD (formerly FSL)
=> NWSTG -- TNC => CCS
As of May 2006, these data have been assimilated into the MADIS.
One could also examine MADIS Surface Data.
If either prflrb or prflrp is flagged for deficiency, check bulletin IUPT41 KBOU in FADD.
These data are non-critical. Check with ESRL/GSD (formerly FSL) in
Boulder only if deficiencies persist for more than one model cycle.
Surface Marine Data Types
CSTGD (Coast Guard data):
Flow path: GTS data from many U.S. sites => NWSTG -- TNC => CCS
If flagged for deficiency, check bulletins in FADD SXUS8(0-9) Kxxx
and SXUS40 Knnn, and also AWIPS pils CGR000. Then check with TOC Tech Control.
DBUOY (Drifting buoy data):
Flow path: GTS data from ARGOS => NWSTG -- TNC => CCS
NWSTG transfers data to NDBC
for data processing and quality control before passing them to users.
Drifting buoy reports come to and are distributed by ARGOS. If flagged
for deficiency, check bulletins in FADD SSVX(02-08) KARS and SSVX02 LFPW
(from France). Then check with TOC Tech Control.
MBUOY (Moored buoy data):
LCMAN (Land-based C-MAN stations):
Flow path: GTS data from many sites worldwide such as WAL => NWSTG -- TNC
=> CCS
NWSTG transfers data to NDBC
for data processing and quality control before passing them to users.
If flagged for deficiency, check bulletins in FADD SXUS(20-24) KWBC
and SNVD(15,17) KWBC, and also AWIPS pils BOYCM(1-7). Then check with TOC
Tech Control.
SHIPS (Manual and automatic ship reports):
Flow path: GTS data from many sites worldwide => NWSTG -- TNC => CCS
Ship reports come to and are distributed from WAL (Wallops) through NOS CORMS.
If flagged for deficiency, check FADD to see if bulletins are being made; eg,
BMDA90 KWBC and SMVX90 KWBC. Then call TOC Tech Control who will check for any
line problem and contact WAL as needed.
TIDEG (Tide gauge reports):
Flow path: GTS data from NOS/CORMS => NWSTG -- TNC => CCS
If flagged for deficiency, check bulletins in FADD SOUS5(2,3) KWBC and
SOPA56 KWBC, and also AWIPS pil TIDATL. Then contact NOS CORMS if not updating
properly.
TIDGCM (Tide gauge reports in C-MAN format):
Flow path: GTS data from many sites worldwide such as WAL => NWSTG -- TNC
=> CCS
These data arrive at the decoders commingled with LCMAN data.
See LCMAN for troubleshooting guidance.
Satellite Data Types
Reference this table for
useful information pertaining to NESDIS satellite data ingest in the CCS.
AIRS (AQUA-AIRS AIRS/AMSU-A/HSB 1B processed radiances-center FOV):
AIRSEV (AQUA-AIRS AIRS/AMSU-A/HSB 1B processed radiances-every FOV):
AIRSWM (AQUA-AIRS AIRS/AMSU-A/HSB 1B processed radiances-warmest FOV):
Flow path: Svalbard downlink => NASA Goddard (Greenbelt) => NESDIS dds (formerly cemscs) server -- ftp => CCS
Svalbard is believed to be located in Norway. A high-latitude site is necessary for reception.
If flagged for deficiency, query ESPC Operations, and specify Aqua-AIRS. ESPC also manage Polar AIRS and
Model AIRS which are separate entities. If data shortage is limited to AIRS, then check
with NASA Goddard. Key contact person is Walter Wolf (301-316-5003). One may browse the
NASA JPL AIRS web pages for detailed information.
GOEST (GOES/NESDIS 5x5 FOV soundings/radiances):
GOEST1 (GOES/NESDIS hi-resol. 1x1 FOV soundings/radiances):
GOESTH (GOES/NESDIS hi-resol. 1x1 FOV soundings/radiances):
Flow path: NESDIS => RSIS gp12 server => CCS
These data come from the gp12 server on the fifth floor and is monitored
by RSIS. If flagged for deficiency, query the RSIS (SATEPS) Helpdesk.
QSCAT (QuikSCAT products):
Flow path: U. of CO Mission Control Center => ESRL/GSD (formerly FSL)
=> NESDIS dds (formerly cemscs) server -- ftp => CCS
If flagged for deficiency, query ESPC Operations.
Note: OPC acquires data from SSD/SATEPS for use in NAWIPS. Check with RSIS (SATEPS)
Helpdesk and/or SAB for further inquiry.
H2IUS (GOES/NESDIS water vapor imager derived cloud motion):
INFUS (GOES/NESDIS infrared imager derived cloud motion):
VISUS (GOES/NESDIS visible imager derived cloud motion):
Flow path: NESDIS gp12 server -- ftp => CCS
If flagged for deficiency, check with NESDIS/SAB on any satellite issues.
Or check with the RSIS (SATEPS) Helpdesk for production and dissemination status.
Also browse the
Satellite Services Division
for the latest of these high-density satellite derived winds, and browse the
Interactive Processing Branch
for the number of vectors produced compared to the 30-day running mean.
H2OMO (MODIS (AQUA/TERRA) wvpr imager derived cloud motion):
INFMO (MODIS (AQUA/TERRA) infrared derived cloud motion):
AMSRE (AQUA-AIRS-E processed radiances):
Flow path: NASA Goddard Nanuk machine => NESDIS gp16 server -- ftp => CCS
If flagged for deficiency, check with NESDIS/SAB on any satellite issues where the
primary POC is Kyle Turner. Or check with the RSIS (SATEPS) Helpdesk for production and
dissemination status. Also browse the
MODIS Direct Broadcast at SSEC
to check if the satellite is actually producing data, and check the
gp16 server
for any current data. Also, one may reference
NASA's MODIS web pages
for general and detailed information about the MODIS program.
VISEU (METEOSAT/EUMETSAT visible derived cloud motion):
INFEU (METEOSAT/EUMETSAT infrared derived cloud motion):
Flow path: GTS data from EUMETSAT => NWSTG -- TNC => CCS
If flagged for deficiency, call TOC Tech Control. Tech Control will probably
check with Exeter if no problem at TOC.
VISJA (GMS/JMA visible derived cloud motion)[discontinued 6/03/07]:
INFJA (GMS/JMA infrared derived cloud motion)[discontinued 6/03/07]:
Flow path: GTS data from Japan => NWSTG -- TNC => CCS
Check WMO bulletins TN(N,S)AO(1-6) RJTD.
If any deficiency persists for more than one model cycle, check with RSIS,
ESPC Operations, and Honolulu.
Notes: The GMS satellite was replaced with GOES-9 during spring of 2003. RSIS will
only have information on the satellite ststus of GOES-9, as will SAB, but neither
will have information on the actual winds production. ESPC Operations and Honolulu will have
even less information or none at all.
SSMIP (SSM/I - FNMOC derived products):
SSMIPN (SSM/I - NCEP Neural Net-3 derived products):
Flow path: FNMOC => Pentagon => TOC => NESDIS gp12 server (btemps) -- ftp
=> CCS (ssmipn passed through NeuralNet-3 Algorithm to generate products
from btemps)
If flagged for deficiency, check with RSIS for any network problem. Then check if TOC
is receiving these data. Then query FNMOC about any problems at their end.
TRMM (NASA/tropical rainfall measuring mission):
Flow path: NASA Goddard (Greenbelt) trmmrt.gsfc.noaa.gov => ncosrv => CCS
If flagged for deficiency, check with NASA at Greenbelt.
1BAMUA (POES/NESDIS AMSU-A 1b radiances):
1BAMUB (POES/NESDIS AMSU-B 1b radiances):
1BHRS2 (POES/NESDIS HIRS-2 1b radiances):
1BHRS3 (POES/NESDIS HIRS-3 1b radiances):
1BHRS4 (POES/NESDIS HIRS-4 1b radiances):
1BMHS (NOAA 18 MHS NCEP-processed radiances):
1BMSU (POES/NESDIS MSU 1b radiances):
OSBUV (POES/NESDIS solar backscatter UV radiances):
OSBUV8 (POES/NESDIS solar backscatter UV radiances, version 8):
H1BN14 (NOAA 14 high resolution infrared 1b radiances):
M1BN14 (NOAA 14 microwave sounding unit 1b radiances):
A1BN15 (NOAA 15 adv. micro sounding unit-A 1b radiances):
B1BN15 (NOAA 15 adv. micro sounding unit-B 1b radiances):
A1BN16 (NOAA 16 adv. micro sounding unit-A 1b radiances):
B1BN16 (NOAA 16 adv. micro sounding unit-B 1b radiances):
Flow path: NESDIS dds (formerly cemscs) server -- ftp => CCS
Most deficiencies with these data are short-lived and the result of timing issues;
however, if any deficiency persists for more than one model cycle, then check with
SAB about the NESDIS dds server.
MESONET Data Types
MSO470 (Colorado E-470 (Interstate 470)):
MSOALK (Alaska Department of Transportation):
MSOAPG (U.S. Army Aberdeen Proving Grounds):
MSOAPR (Citizen Weather Observers Program):
MSOAWS (AWS Convergence Technologies, Inc.):
MSOAWX ("Anything Weather"):
MSOCOB (NWS COoperative Observer Program):
MSOCOL (Colorado Department of Transportation):
MSODCN (DC Net):
MSODEN (Denver Urban Drainage and Flood Control):
MSOFLA (Florida (FAWN and USF)):
MSOFLT (Florida Department of Transportation):
MSOGEO (Georgia Department of Transportation):
MSOHAD (NWS Hydrometeo. Automated Data System (HADS)):
MSOIEN (Iowa Environmental):
MSOIND (Indiana Department of Transportation):
MSOIOW (Iowa Department of Transportation):
MSOKAN (Kansas Department of Transportation):
MSOKLA (Oklahoma Mesonet):
MSOLJU (Louisiana State & Jackson State Univ.):
MSOMCA (Missouri Commercial Agriculture Wx Net):
MSOMIN (Minnesota Department of Transportation):
MSONOS (NOS-Physical Oceanographic Real-Time System):
MSORAW (NFIC Remote Automated Weather Stations (RAWS)):
MSOTHR (Miscellaneous):
MSOVIR (Virginia Department of Transportation):
MSOWFY ("Weather for You"):
MSOWIS (Wisconsin Department of Transportation):
MSOWST (MesoWest):
MSOWTX (West Texas):
Flow path: GFDL -- ftp => ncosrv --
dbnet => CCS
First contact a data flow specialist such as Paula Freeman for any ftp, dbnet, or
ncosrv problem. If none, then contact GFDL
where the primary POC is Mike Barth.
The following are listed on model data dump reports but not used presently in model analyses.
GPSRO (CHAMP/COSMIC GPS radio occultation data):
This dataset is actually comprised of a combination of two unique and independent data subsets.
Flow path: Presently, NCEP mirrors both subsets from NESDIS gp12
but intends to obtain them through GTS in the future which is now being done in Development.
The CHAMP (CHAndra Multiwavelength Project) subset is German satellite data which is used for
GPS-based atmospheric soundings.
The COSMIC subset also is used for GPS-based atmospheric soundings and comes from UCAR which provides
COSMIC data status reports.
ATOVS (POES/NESDIS - processed ATOVS soundings/radiances):
CAMDAR (Automated Canadian ASDAR/ACARS data from BUFR):
GEOIMR (GOES/NESDIS (11x17 FOV) imager clear radiances):
H2OIN (INSAT/India water vapor derived cloud motion):
H2OJA (GMS/JMA water vapor imager derived cloud motion):
INFIN (INSAT/India infrared derived cloud motion):
PRFLRJ (Japanese Meteo Agency profiler winds):
RASS (RASS temperatures, NOAA and Cooperative Agency):
SSMIT (SSM/I - brightness temperatures):
TAMDAR (Automated TAMDAR aircraft data):
VISIN (INSAT/India visible derived cloud motion):
WDSAT (WindSAT scatterometer winds from FNMOC):
These data types are not used presently in model analyses. Therefore, troubleshooting
efforts are not required, and solid troubleshooting guidance is not available.
Nevertheless, any troubleshooting efforts could wait until any deficiency persists for
at least two model cycles.
The following are available sporadically and not used presently in model analyses.
3P9US (GOES/NESDIS 3.9 micron channel derived cloud motion):
AMSREP (AQUA-AMSR-E ocean surface products /Level 2/):
AMUATA (POES NOAA AMSU-A NESDIS antenna temperatures):
ANOWB1 (AIRNOW ozone data - 1-hour backward average):
ANOWB8 (AIRNOW ozone data - 8-hour backward average):
ANOWFA (AIRNOW ozone data - 1- and 8-hour forward average):
ANOWPM (AIRNOW particulate data - delayed 1-hour backward average):
ANOWRT (AIRNOW ozone data - real time 1-hour backward average):
AVCL17 (NOAA 17 AVHRR GAC NCEP-proc'd cloud or land radiances):
AVCL18 (NOAA 18 AVHRR GAC NCEP-proc'd cloud or land radiances):
AVCS17 (NOAA 17 AVHRR GAC NCEP-proc'd clear and sea radiances):
AVCS18 (NOAA 18 AVHRR GAC NCEP-proc'd clear and sea radiances):
BATHY (Bathythermal data):
BUOYSH (Buoys (moored or drifting) decoded from SHEF format):
CAJSWW (JASON-1/CNES/AVISO IGDR wind/wave):
CMANSH (CMAN stations decoded from SHEF format):
COOPAL (Coop All NWS COOPerative Obs decoded from SHEF):
COOPMD (Coop/MADIS Modernized NWS COOPerative Observers):
ENVSAL (ENVISAT/NAVOCEANO ALPS SSHA hi-res global altimeter):
ENVSWW (ENVISAT wind/wave):
ERSAL (ERS/radar altimeter data):
ERSHAL (ERS/NLSA high-resolution regional altimeter):
ERSAR (ERS/SAR):
ERSWN (ERS/scatterometer winds):
ESAMUA (POES NOAA AMSU-A processed radiances from EARS):
ESAMUB (POES NOAA AMSU-B processed radiances from EARS):
ESHRS3 (POES NOAA HIRS-3 processed radiances from EARS):
GFOFWW (GEOSAT Follow-On/NAVOCEANO wind/wave fast delivery):
GFOHAL (GEOSAT Follow-On/NLSA hi-resol regional altimeter):
H2IJAN (GMS/NESDIS water vapor imager derived cloud motion):
H2OEU (METEOSAT/EUMETSAT wvpr imager derived cloud motion):
H2SUS (GOES/NESDIS water vapor sounder derived cloud motion):
HYDDEN (Hydro/MADIS Denver Urban Drainage & Flood Control):
HYDOTH (Hydro/MADIS many providers, not separated out):
INFJAN (GMS/NESDIS infrared derived cloud motion):
MTIASI (METOP IASI 1C radiance data):
NERSAL (ERS/NAVOCEANO ALPS high-resol global altimeter):
NGFNAL (GEOSAT Follow-On/NAVOCEANO Navy IGDR winds altim):
NGFOAL (GEOSAT Follow-On/NAVOCEANO ALPS hi-res global altim):
NJSNAL (JASON/NAVOCEANO ALPS high-resol global altimeter):
NJSNWW (JASON-1 wind/wave direct from NAVOCEANO):
NTPXAL (TOPEX/NAVOCEANO ALPS high-resol global altimeter):
OZONHI (Ozone soundings, high-resolution orig. in ASCII):
OZONLO (Ozone soundings, low-resolution from Met. Office):
PRFLRE (European profiler winds):
PRFLRH (Hong Kong profiler winds):
PRFLRM (Profiler spectral moments, NOAA and Coop Agency):
PRFLRS (Surface profiler Data, NOAA and Coop Agency):
PTRUS (GOES/NESDIS picture triplet derived cloud motion): discontinued
RTOVS (POES/NESDIS - processed RTOVS soundings/radiances):
RIVER (USGS river/stream data):
SCD (Aviation - supplementary climatological data):
SHEFCM (Complete set of products decoded from SHEF (hydrologic data) format):
SHEFF (AFOS products (precip) decoded from SHEF format):
SNOW (Snow/MADIS many providers, not separated out):
SSMISU (DMSP/SSM/IS 1C radiance data from Met Office):
SSTNS (POES/NESDIS sea surface temperatures):
SSTNSG (GOES/NESDIS sea surface temperatures):
SSTNSO (POES/NESDIS AVHRR obs and sea surface temperatures):
SSTNSP (POES/NESDIS physical sea surface temperature retrievals):
SSTNVP (POES/NESDIS AVHRR physical retrieval sea sfc temps):
SSTNV (POES/Navy low-resolution sea surface temperatures):
SSTNVO (POES/Navy AVHRR obs and sea surface temperatures):
SSTNVP (POES/Navy AVHRR physical retrieval sea sfc temps):
SSTNVH (POES/Navy high-resol sea surface temperatures):
TESAC (TESAC data):
TIDGSH (Tide gauge reports decoded from SHEF format):
TOPHAL (TOPEX/NLSA high-resolution regional altimeter):
TOPLAL (TOPEX/NLSA low-resolution global altimeter):
TOVS (POES/NESDIS - processed TOVS soundings/radiances):
TRKOB (TRACKOB data):
TRPSTM (Tropical storms):
VISUW (GOES/UW-CIMSS visible derived cloud motion):
WDSATS (WindSAT scatterometer winds from NESDIS):
These data types are not used presently in model analyses and not listed on any data
dump reports. Therefore, troubleshooting efforts are not required. Due to sporadic
availability and the lack of count reports for these types, any deficiencies would
be undefinable or difficult to determine. Any deficiency one might detect should
persist for at least two model cycles before any troubleshooting efforts.
|