1 / 17

Observation pre-processing in the ARPEGE/ALADIN model

Observation pre-processing in the ARPEGE/ALADIN model. Roger Randriamampianina Hungarian Meteorological Service ALADIN 3D-Var/ODB training course, Budapest, 6-10 June, 2006. Outline. Local pre-processing:. OULAN . BATOR. 1C RAD. BIAS CORRECTION. OULAN .

conan
Télécharger la présentation

Observation pre-processing in the ARPEGE/ALADIN model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Observation pre-processing in theARPEGE/ALADIN model Roger Randriamampianina Hungarian Meteorological Service ALADIN 3D-Var/ODB training course, Budapest, 6-10 June, 2006

  2. Outline Local pre-processing: OULAN BATOR 1C RAD. BIAS CORRECTION

  3. OULAN

  4. Real time available data: Networks Observations arrive through - GTS (Global Telecommunication System) in ASCII or BUFR format - Direct Sat. Reception – (Budapest HRPT Station) - Special TCP/IP lines - Internet FTP in some cases Providers - All WMO countries for most of the observation types - Space agencies for Satellite observations (Eumetsat, ESA, NESDIS, NASA, DMSP) - NMS for the local national data Source: www.wmo.int

  5. Types of observations Satellite Observations Meteosat: - SEVIRIClear sky radiances NOAA Atovs: - Hirs, Amsua, Amsub, Mhs DMSP: - Ssm/I  AQUA: -Airs Conventional Observations Surface data: - Synop, Ship - Bathy, Tesac - Buoy Upperair data: - Airep, Amdar, Acar - Temp, Temp-ship, Temp-mobil, Temp-drop - Pilot, Pilot-ship, Europrofil, Profiler - Satob, Satgeo, geowind (MET-8)

  6. Data pre-processing at HMS ASCII GTS Eumetcast … FTP Intermediate ASCII Or direct reading … oulan BUFR Pre-processing chain: oulan bator screening Complex quality check and data selection Reading of dataand coding of additional information Blacklisting andcreation of the ODB

  7. Observation usage (in surface analysis)

  8. Observation usage (in variational analysis)

  9. Channel number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Over Land x x x x x x x x Over Sea x x x x x x x x Over Sea ice x x x x x x Cloudy pixel x x x x x Observation usage (Satellite radiances) Example: Use of RAD1C AMSU-A Over land channels 5 and 6 are used when the model orography is less than 500m and 1500m, respectively

  10. The oulan procedure You need to changein case of local implementation … Read_Synop Read_Amdar Read_Amsub … Ext_lam_Synop Ext_lam_Temp Ext_lam_Amsub … LSYNOP LTEMP LTOVSAMSUB Namelist control oulan_lam_extract OULAN OBSOUL

  11. Modifications compared to the original code Oulan: from the export version under “UTI” directory The added files: ext_amsua_aapp.f – read the native sat file (AMSU-A) ext_amsub_aapp.f – ==========x ==== (AMSU-B) ext_hirs_aapp.f – ==========x ==== (HIRS) ext_synop_netcdf.f – read the netCDF SYNOP data ext_temp_netcdf.f – read the netCDF TEMP data oulan_lam_elev.f – read the elevation data from TLS netcdf.inc – netCDF include file ama1c.h, amb1c.h, hirs1c.h, netcdf.h – include files The modified files: ext_{obs_type}.f  ext_lam_{obs_type}.f Where obs_type: synop, temp, geowind, satob, europrofil, amsua, amsub, hirs !!! Thereare two versions of the oulan_carobs in the source directory  No change in the OBSOUL format  Change in case of new obs. (eg. AMSU-B) (cy24 vs cy28)  The number of the arguments in oulan_carobs has changed

  12. Data extraction from the database at the HMS The surface and radiosonde observations:  from netCDF files;  synop, temp The 1C radiance data:  from AAPP native format;  amsua{01-20},amsub{01-20},hirs (to be modified) The aircraft observation:  from ASCII (FM42) and BUFR files  read separately and arranged in amdar_ascii.dat The Atmospheric Motion Vector data:  from BUFR files;  read separately and arranged in geowind_ascii.dat The windprofiler data:  from BUFR files (complicated, additional change had to be done to read the proper station identifier);  read separately and arranged in profiler_ascii.dat  Data in BUFR format are extracted out of the oulan program ! except the AMV, data are stored in different files

  13. &NADIRS NDATE=20020225, NRESO=00, ALANZA = 90., ALASZA = -90., ALOOZA = -180., ALOEZA = 180., NDIFFM1 = 30, NDIFFP1 = 30, NDIFFM2 = 300, NDIFFP2 = 259, LTOVSAMSUA = .TRUE., LTOVSAMSUB = .TRUE., LTOVSHIRS = .FALSE., LTEMP = .TRUE., LSYNOP = .TRUE., LAMDAR = .TRUE., LEUROPROFIL = .TRUE., LGEOWIND = .TRUE., LSATOB = .FALSE., NINIT = 0, LRH2Q = .TRUE., /END &NANBOB NBTOVSAMSUA = 80000, NBTOVSAMSUB = 80000, NBTOVSHIRS = 8000, NBTEMP = 1000, NBSYNOP = 4000, NBAMDAR = 9000, NBEUROPROFIL = 8000, NBSATOB = 20000, NBGEOWIND = 20000, /END The NAMELIST file

  14. The OBSOUL file  in ASCII format - each observation represents one article consisting of: - one header (describing the observation) - bodies (as many as the number of the observed/measured parameters) First article: - date (analysis) integer - hour (network time) integer Header: - total length of the observation article integer - observation type integer - observation characteristics integer - latitude real - longitude real - station identification character - date of the measurement integer - hour of the measurement integer - altitude real - number of the parameters (ie. bodies) integer - observation quality flags integer - site dependant info integer

  15. Example: 20041215 12 42 1 10014011 48.10000 19.51667 '12756 ' 20041215 120000 153.0000000 6 1111 100000 1 -103290.0000 0.1699999976E+39 0.0000000000E+00 2064 39 101310.0000 0.1699999976E+39 271.2600098 2048 58 101310.0000 0.1699999976E+39 82.00000000 2048 7 101310.0000 0.3211538133E-03 0.2632536227E-02 2048 41 101310.0000 3.000000000 190.0000000 2048 91 101310.0000 0.1699999976E+39 100.0000000 2048 22 2 10051144 43.52000 5.22000 'EU4426 ' 20041215 100700 182.8800049 2 11111 0 2 182.8800049 0.1699999976E+39 284.3599854 4111 3 182.8800049 4.110000134 124.0000000 4111 22 3 103254090 56.95500 -7.19100 ' 055' 20041215 114500 0.1699999976E+39 2 11111 0 200 69.00000000 0.1699999976E+39 0.1699999976E+39 9 3 30160.00000 28.79999924 296.0000000 2063 synop Amdar AMV/geowind The OBSOUL file Body (ies): - parameter type integer - first vertical coordinate real - second vertical coordinate (if necessary or other) integer - observed/measured parameter real - parameter quality flag integer

  16. To be continued … Any questions ?

  17. Exercises 1(a,b)- create a single T(a) or V(b) obs. form aircraft data around 500 hPa 2- change the obs. errors for specific humidity for radiosonde dataidea: check the ext_lam_temp around the variable ZQEEFH 3- simulate the implementation of the PILOT obs. using measurements from radiosondeidea: copy ext_pilot.F from the “UTI/oulan” directory and follow changes in the ext_lam_temp.f. Remember, that in the pilot report we have only wind measurements. 2 and 3 need the (re-)compilation of the code. To do so, please copy the oulan directory from ~wshop01/Preproc to your Preproc directory. Use “compile_oul” for compilation and “create_oulan” to create the executable file.

More Related