Changes between Version 1 and Version 2 of ticket/261/TicketSummary/DescriptionAmv


Ignore:
Timestamp:
Feb 26, 2016 12:33:59 PM (3 years ago)
Author:
Jin Lee
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/261/TicketSummary/DescriptionAmv

    v1 v2  
    1414|| '''Bufr file''' || '''originating centre''' || '''satellite platforms''' || '''notes''' ||
    1515|| || || || ||
    16 || amv160 || NESDIS || GOES-E, GOES-W, Aqua/MODIS, locally generated AMV's from MTSAT-1R, MTSAT-2 and Himawari-8 || The originating centre for the loally generated AMV's from MTSAT-1R, MTSAT-2 and Himawari-8 is ???. [[BR]][[BR]] Note also that the expected error values are converted to QI values to allow OPS to process them as if they are JMA-supplied winds ||
     16|| amv160 || NESDIS || GOES-E, GOES-W, Aqua/MODIS, locally generated AMV's from MTSAT-1R, MTSAT-2 and Himawari-8 || The originating centre for the loally generated AMV's from MTSAT-1R, MTSAT-2 and Himawari-8 is ???. [[BR]][[BR]] Note also that the expected error values are converted to QI values to allow OPS to process them as if they are JMA-supplied winds. [[BR]][[BR]] Q. Is Himawari-8 given the satellite ID of 173 in the Bufr file? ||
    1717|| amv254 || EUMETSAT Operation Centre || contains METEOSAT First Generation || ||
    1818|| amv254msg || EUMETSAT Operation Centre || contains METEOSAT Second Generation) || ||
     
    2121=== How Ops_ExtractAndProcess processes AMV's ===
    2222
    23 Originating centre of ??? (locally derived AMV's)
    24 
    25 === !ToDo ===
    26 
    27 1. The processing of locally generated AMV's should be done properly. Currently locally derived AMV's are assigned the same M.O.T. as JMA-supplied AMV's. In Ops_Satwind_SetObsType.f90,
     23In the OPS code in the trunk, the locally derived  AMV's which have originating centre of ??? are assigned the same M.O.T. as JMA-supplied AMV's. In Ops_Satwind_SetObsType.f90,
    2824
    2925{{{
     
    3228}}}
    3329
    34 UKMO agreed that Bureau can use M.O.T. of 235?? to assign to locally generated AMV's. We should use this and modify OPS code to process locally generated AMV's differently to JMA-supplied AMV's. Then the code change can be put in the MOSRS OPS trunk.
     30
     31=== !ToDo ===
     32
     331. The processing of locally generated AMV's should be done properly.
     34   a. Currently locally derived AMV's are assigned the same M.O.T. as JMA-supplied AMV's (see under '''How Ops_ExtractAndProcess processes AMV's''').
     35   b. UKMO agreed that Bureau can use M.O.T. of 235?? to assign to locally generated AMV's. We should use this and modify OPS code so that Ops_ExtractAndProcess processes the locally generated AMV's differently to JMA-supplied AMV's.
     36   c. The code change then should be put in the MOSRS OPS trunk.