Changes between Version 4 and Version 5 of ticket/261/TicketSummary/DescriptionAmv


Ignore:
Timestamp:
Feb 26, 2016 3:31:21 PM (3 years ago)
Author:
Jin Lee
Comment:

--

Legend:

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

    v4 v5  
    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. [[BR]][[BR]] Q. Is Himawari-8 given the satellite ID of 173 in the Bufr file? ||
     16|| amv160 || NESDIS || GOES-E, GOES-W, Aqua/MODIS, locally generated AMV's from MTSAT-2 || 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) || ||
    1919|| amv34 || JMA || MTSAT-1R, MTSAT-2 and Himawari-8 || ||
     20
     21Note 1. AMV's from Himawari-8 were not assimilated for the trial period (Q. even JMA-generated AMS's?)
    2022
    2123=== How Ops_ExtractAndProcess processes AMV's ===