140 likes | 149 Vues
Application of AMSR wind speed algorithm for retrieving Windsat vector wind Akira Shibata JAXA AMSR-E meeting, at Huntsville, June 2-3, 2010. Backgrounds.
E N D
Application of AMSR wind speed algorithm for retrieving Windsat vector wind Akira Shibata JAXA AMSR-E meeting, at Huntsville, June 2-3, 2010
Backgrounds • SeaWinds on Quickscat stopped its operation in November 2009. Then, quality data of wind vector from Windsat became more necessary for analysis of weather forecast. • AMSR wind speed algorithm is being applied for retrieving wind vector from Windsat.
Parameter Definition AMSR s36 = (36H - (s × (36V – a) + b ) ) / fac parameters a ,b, s, fac depend on SST 10H* = AMSR_10H – atmos_effect_10H –calm_ocean_10H 10H* available within no-rainy area because of atmospheric correction using higher frequencies 23/36V Windsat Stokes parameters 18GHz 3rd/4th
Determination of relative wind direction (AMSR case) - 6H* / s36 plane - cross (K) 16m/s up down 6H* 7m/s (K) s36 wdir positive = downwind wdir available for wind speed greater around 7m/s
Conversion of s36 to wind speed (AMSR case) After s36 is transformed to cross-wind position K s36 m/s wind speed
Stokes 3rd/4th parameter (Windsat case) 315 10<SST<15 270 135 225 90 relative wind direction 0/360 upwind 45
Combination of stokes parameters and wdir wdir negative wdir positive
Retrieval of wind vector for Windsat • Define six lines which form 3rd/4th planes, which are variable in SST and 10H* • Calculate relative wind direction by position of the nearest line, assisted by knowledge of wdir • Temporary, 10H* is used instead of s36 Only retrievable for wind speed larger than around 7m/s, and within no-rainy areas.
Windsat 3rd/4th plane 10<SST<15 5<10H*<7 9<10H*<11 13<10H*<15 17<10H*<19
Comparison of Windsat vector and GANAL (JMA) 12GMT Jan. 1, 2009
Comparison of Windsat vector and GANAL (JMA) Jan. 1, 2009
Comparison of Windsat vector and GANAL (JMA) Jan. 1, 2009
Comparison of Windsat vector and GANAL (JMA) Jan. 1, 2009
Status • Algorithm of retrieving wind direction seems to work well for strong wind, but it needs further works for middle wind. Windsat data problems • Due to possible Tb calibration error, s36 has anomalous values, which vary along orbits and monthly. • Scan bias errors existing, in particular for s36 • Mismatch of spatial locations of s36 and 10H*