Changes between Version 8 and Version 9 of ticket/365/TicketDetails


Ignore:
Timestamp:
Jan 18, 2019 2:41:14 PM (3 months ago)
Author:
Jin Lee
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/365/TicketDetails

    v8 v9  
    3232|| 20171215T0600Z || gl[mu]_ops_process_background_ahiclear || Not known || Reset to succeeded ||
    3333
     34==== u-be334 ====
     35
     36|| Cycle time || Failed task || Reason for failure || Action taken ||
     37|| || || || ||
     38|| 20171215T0600Z || gl[mu]_ops_process_background_ahiclear || Not known || Reset to succeeded ||
     39
    3440== Results ==
    3541
    36 My working hypothesis is that areas of difference will propagate downstream with increasing forecast lead time. If for a particular forecast hour the differences are averaged we may see a track.
     42My working hypothesis is that areas of difference will propagate downstream with increasing forecast lead time,
     43
     44   * Simply looking at difference for a particular basetime may not yield anything. Better way to bring out differences is to average all the differences for each forecast range. This is based on my hunch: at 00 forecast hour absence of Macquarie Island obs should produce differences around the Island. This difference will move eastward while being amplified