{"id":6197,"date":"2012-12-07T16:57:20","date_gmt":"2012-12-07T21:57:20","guid":{"rendered":"https:\/\/hwt.nssl.noaa.gov\/ewp\/internal\/blog\/?p=6197"},"modified":"2017-06-23T14:05:17","modified_gmt":"2017-06-23T19:05:17","slug":"warning-verification-pitfalls-explained-part-5","status":"publish","type":"post","link":"https:\/\/inside.nssl.noaa.gov\/ewp\/2012\/12\/07\/warning-verification-pitfalls-explained-part-5\/","title":{"rendered":"Warning Verification Pitfalls Explained &#8211; Lack of Reports Can Inflate Lead Time"},"content":{"rendered":"<p>As finally promised as an &#8220;aside&#8221; in <a href=\"https:\/\/hwt.nssl.noaa.gov\/ewp\/internal\/blog\/2011\/10\/11\/warning-verification-pitfalls-explained-%E2%80%93-part-2-2x2-x2\/\">this blog entry<\/a>, I will cover the issue of how using point observations can lead to a misrepresentation of the lead time of a warning.<\/p>\n<p>Consider that one warning is issued, and a single severe weather report is received for that warning.\u00a0 We have a POD = 1 (one report is warning, zero are unwarned), and an FAR = 0 (one warning is verified, zero warnings are false).\u00a0 Nice!<\/p>\n<p>How do we compute the lead time for this warning?\u00a0 Presently, this is done by simply subtracting the warning issuance time from the time of the first report on the storm.\u00a0 From <a href=\"https:\/\/hwt.nssl.noaa.gov\/ewp\/internal\/blog\/2011\/10\/17\/creating-verification-numbers-part-4-%E2%80%9Ctruth-event%E2%80%9D-scores-for-one-event\/\">this earlier blog post<\/a>:<\/p>\n<p><em>t<\/em><sub>warningBegins<\/sub> = time that the warning begins<\/p>\n<p><em>t<\/em><sub>warningEnds<\/sub>= time that the warning ends<\/p>\n<p><em>t<\/em><sub>obsBegins<\/sub> = time that the observation begins<\/p>\n<p><em>t<\/em><sub>obsEnds<\/sub>= time that the observation ends<\/p>\n<p>LEAD TIME (lt): <em>t<\/em><sub>obsBegins <\/sub>\u2013 <em>t<\/em><sub>warningBegins <\/sub>[HIT events only]<\/p>\n<p>Let&#8217;s look at our scenario from the <a href=\"https:\/\/hwt.nssl.noaa.gov\/ewp\/internal\/blog\/2012\/12\/07\/warning-verification-pitfalls-explained-part-4\/\">previous blog post<\/a>:<\/p>\n<p><a href=\"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/leadtime-perceived.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-14606 size-full\" title=\"lead time perceived\" src=\"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/leadtime-perceived.png\" alt=\"lead time perceived\" width=\"552\" height=\"415\" \/><\/a><\/p>\n<p>For ease of illustration, I&#8217;m using the spatial scale to represent the time scale.\u00a0 The warning begins at some time <em>t<\/em><sub>warningBegins<\/sub>, and the report is at a later time <em>t<\/em><sub>obsBegins<\/sub>.\u00a0 The lead time is shown spatially in the figure, and in this case, it appears that the warning was issued with some appreciable lead time before the event at the reporting location occurs.<\/p>\n<p>However, as we explained in the <a href=\"https:\/\/hwt.nssl.noaa.gov\/ewp\/internal\/blog\/2012\/12\/07\/warning-verification-pitfalls-explained-part-4\/\">previous blog post<\/a>, reports only represent a single sample of the severe weather event in space in time.\u00a0 How can we be certain that the report above represents the location and time of the <em>very first instance<\/em> that the storm became severe?\u00a0 In all but probably rare cases, it does not, and the storm became severe at some time prior to the time of that report.\u00a0 This tells us that for pretty much every warning (hail and wind events at least), <em>the computed lead times are erroneously too large<\/em>!\u00a0 Reality looks more like this:<\/p>\n<p><a href=\"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/leadtime-actual.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-14607 size-full\" title=\"lead time actual\" src=\"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/leadtime-actual.png\" alt=\"lead time actual\" width=\"552\" height=\"422\" \/><\/a><\/p>\n<p>ADDENDUM (1\/10\/2013):\u00a0 Here is another way to view this so that the timeline of events is better illustrated.\u00a0 In this next example, a warning is issued at t=0 minutes on a storm that is not yet severe, but expected to become severe in the next 10-20 minutes, hence hopefully providing that amount of lead time.\u00a0 Let&#8217;s assume that the red contour in the storm indicates the area over which hail <span style=\"text-decoration: underline;\">&gt;<\/span>1&#8243; is falling, and when red appears, the storm is officially severe.\u00a0 As the storm moves east, I&#8217;ve &#8220;accumulated&#8221; the severe hail locations into a hail swath (much like the NSSL Hail Swath algorithm works using multiple-radar\/multiple-sensor data).\u00a0 Only two storm reports were received on this storm, one at t=25 minutes after the warning was issued, and another at t=35 minutes.\u00a0 That means this warning verified (was not a false alarm), and both reports were warned (two hits, no misses).\u00a0 The lead times for each report were 25 and 35 minutes respectively, but official warning verification uses lead time to the first report known as the <em>initial lead time<\/em>.\u00a0 Therefore, the lead time recorded for this warning would be 25 minutes, which is very respectable. \u00a0 However, in this case, the storm was actually severe starting at t=10 minutes.\u00a0 The lead time between the start of the warning and the start of severe weather was <em>15 minutes shorter<\/em> than that officially recorded.<\/p>\n<p><a href=\"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/leadtimeloop3.gif\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-14608 size-full\" title=\"leadtimeloop\" src=\"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/leadtimeloop3.gif\" alt=\"leadtimeloop\" width=\"1409\" height=\"802\" \/><\/a><\/p>\n<p><a href=\"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/PictureSwath1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-14609 size-full\" title=\"Picture Swath\" src=\"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/PictureSwath1.png\" alt=\"Picture Swath\" width=\"1409\" height=\"802\" srcset=\"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/PictureSwath1.png 1409w, https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/PictureSwath1-800x455.png 800w, https:\/\/inside.nssl.noaa.gov\/ewp\/wp-content\/uploads\/sites\/22\/2012\/12\/PictureSwath1-768x437.png 768w\" sizes=\"auto, (max-width: 767px) 100vw, (max-width: 1200px) 60vw, 720px\" \/><\/a><\/p>\n<p>How can we be more certain of the actual lead times of our warnings?\u00a0 By either gathering more reports on the storm (which isn&#8217;t always entirely feasible, although that may be improving with new weather crowdsourcing apps like <a href=\"http:\/\/www.nssl.noaa.gov\/projects\/ping\/\">mPING<\/a>), or using <em>proxy verification<\/em> based on a combination of remotely-sensed data (like radar data) and actual reports.\u00a0 Again, more on this later&#8230;<\/p>\n<p><em>Greg Stumpf, <\/em><em>CIMMS and NWS\/MDL<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>As finally promised as an &#8220;aside&#8221; in this blog entry, I will cover the issue of how using point observations can lead to a misrepresentation of the lead time of&#8230; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/inside.nssl.noaa.gov\/ewp\/2012\/12\/07\/warning-verification-pitfalls-explained-part-5\/\" class=\"more-link\">Read more \u00bb<\/a><\/p>\n","protected":false},"author":333,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-6197","post","type-post","status-publish","format-standard","hentry","category-experimental-warning-thoughts"],"_links":{"self":[{"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/posts\/6197","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/users\/333"}],"replies":[{"embeddable":true,"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/comments?post=6197"}],"version-history":[{"count":3,"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/posts\/6197\/revisions"}],"predecessor-version":[{"id":14611,"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/posts\/6197\/revisions\/14611"}],"wp:attachment":[{"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/media?parent=6197"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/categories?post=6197"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/inside.nssl.noaa.gov\/ewp\/wp-json\/wp\/v2\/tags?post=6197"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}