Clarus Quality Checking Summary Formats Is a Task Force Needed PowerPoint PPT Presentation

presentation player overlay
1 / 14
About This Presentation
Transcript and Presenter's Notes

Title: Clarus Quality Checking Summary Formats Is a Task Force Needed


1
ClarusQuality Checking Summary FormatsIs a Task
Force Needed?
Clarus ICC5 Meeting Session 5
  • Andy Stern
  • Consulting Meteorologist (Noblis)
  • FHWA Road Weather Management Team

2
Quality Checking Summaries
  • Topic of Quality Checking (QCh) summaries was
    brought up at the Clarus QCh Task Force meeting
    in 6/06
  • The focus of this workshop was on formulating a
    next generation of QCh algorithms for Clarus
  • There was a lot of interest expressed then and
    recently at a regional demonstration training
    meeting
  • Question to think about Is there a need for a
    QCh Summary Format Task Force?

3
QCh Flag Output in Clarus
  • Here is a sample of text output from a dozen
    sensors. QCh flags are at the end
  • Flag Summary
  • P Pass
  • N Not Pass
  • Available but
  • does not run
  • / Test is not
  • supposed to run

4
Viewing QCh Flags Graphically
5
MADIS QCh Output
  • NOAAs MADIS (Meteorological Assimilation Data
    Ingest System) creates QCh output summaries
  • Provides statistical output based upon time
    periods (Hourly, Daily, Weekly or Monthly)
  • Summaries only include stations with one or more
    flagged sensors
  • Errors are based on observations subtracted from
    an area analysis (Analysis-ObservationError)
  • Is meteorologically cryptic

6
Hourly QC Message
Key QST OBS Questionable Observations Percent
QST Percentage of Total that is Questionable
7
Daily QC Message
RMS Error6F/Mean Error-5F/100 of Observations
are Questionable
8
Weekly QC Message
Daily, weekly, and monthly summaries include only
those stations with observations that have failed
more than 25 of the time.
9
Monthly QC Message
10
QCh Summary from Canadian RWIN
11
Issues from the QCh Task Force
1 of 2
  • Amount of interest differed among the
    participants wrt summary formats
  • Many will not see an emailed QCh summary must
    FTP or provide on web page
  • Only outage notification should be sent via email
  • Need additional sensor information on QCh
    summaries (e.g. subsurface temperature for weight
    restrictions/thaw cycles) and vertical thermistor
    string data
  • Hourly output is critical!

12
Issues from the QCh Task Force
2 of 2
  • QCh information can be used to update public
    traveler information systems
  • Daily summary is needed for performance measures
    (would like to see 12Z-12Z summary output)
  • Some only want to see basic information easy to
    use and understand (easier to use than MADIS)
    not overwhelm the user

13
Legal Issues
  • Caveat Emptor which is Latin for Let the buyer
    beware. Should the onus be on the party that
    uses the data?
  • Are states liable if QCh shows failed sensors?
  • As long as states show a reasonable effort to
    correct failed readings, is that enough?

14
Need for a Task Force?
  • Is there a need to convene a task force of data
    providers, data users and service providers for
    recommendations on
  • QCh formats for Clarus users
  • Summary time periods (hourly, weekly, etc)
  • Statistical output types (rms error, mean error)
  • Method of transmission (email, FTP, web)
  • Liability considerations (archiving summaries)
Write a Comment
User Comments (0)
About PowerShow.com