1 / 27

Model overview

Model overview. Model overview (I). Model overview (II). Modelling domains. Updated emission data outside Lombardy are currently lacking (INEMAR2005). Focus has partly been shifted to the Lombardy domain (finer grid resolution)

vanna
Download Presentation

Model overview

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. Model overview

  2. Model overview (I)

  3. Model overview (II)

  4. Modelling domains

  5. Updated emission data outside Lombardy are currently lacking (INEMAR2005). Focus has partly been shifted to the Lombardy domain (finer grid resolution) Availability and consistency of regional measures at the scale of the entire Po-valley scale is difficult to achieve. The number of scenarios identified by the Lombardy Region as potentially interesting is larger than originally expected. Ref. Technical annex Modelling domains (I)

  6. Modelling domains (II) New grid set-up

  7. Emission Inventory

  8. Emission Inventory (I)

  9. Emission Inventory (II) PM2.5 Split • Notes: • Citydelta split based on American litterature (but scaled on Lombardy activities) is available sector wise. • Putaud split is available for PM10 and station-wise

  10. All emissions to be delivered at 3km resolution over the whole Po Valley and interpolated to each model grid projection. New emission inventory available at later stage of the project upgraded INEMAR and possibly traffic modelling updates APAT 2005 CES scenario Scaling for consistency across scales? Comparison of various 2005 inventories Emission Inventory (III)

  11. Emission scenarios

  12. Emission scenarios (I) • Lombardy focus: Due to data unavailability from most Regions, focus has shifted from Po-Valley to Lombardy implying a different balance in the number of planned scenarios over the two domains. Difficulty of building air quality plans at the scale of the whole Po-valley. • Priority scenarios: Apart from the 2005 BC, a few 2012 scenarios have been identified as priorities and should possibly be run by a maximum number of models. • Sensitivity scenarios: To be run by minimum number of models. Some will require increased work load. • Comparison consistency:Same model should be used across scales or across scenarios to reduce pre-processing work and facilitate comparison. • Non-contract participants: Welcome to contribute to any scenarios.

  13. Emission scenarios (II)

  14. Emission scenarios (III) Underlined: Priority scenarios Bold & blue: Available 2009-2010 CHIMERE – EMEP – CAMx – RCG -- AURORA

  15. Boundary conditions

  16. Boundary conditions (I) • All models do generate their own BC from Po-Valley to Lombardy domains. No data transfer needed • EMEP and CHIMERE Europe BC should be interpolated on a 30 km UTM output grid (Po-Valley domain + 1 grid cell?) on all original model vertical levels. Data to be sent to JRC (JRC script) • Species list: O3, NO, NO2, SO2, NH3, PM2.5, PM10, SULF, NITR, AMMO, BC, ORG • Frequency: 1h or 3h? Daily for PM? • Transfer from CHIMERE to EMEP for BC sensitivity simulation (through JRC or direct?)

  17. Output formatting

  18. Output formatting (I) • Other species: EC, Dust, …Depositions ? • Boundary conditions: same species (?) but frequency reduced to 3h (?) • Only surface data (excepted for Boundary conditions) (?) • What to be reported in PM (water?)

  19. Output formatting (II) • Data should be interpolated on the UTM defined output grids. • Format: NetCdf. Scripts similar to those developed for City- and Eurodelta will be provided by JRC • All data should be saved on DVDs and sent to JRC • Test transfer through JRC ftp server One file per scenario, month and domain: Po-Valley grid: ~ 60 Mb / file Lombardy grid ~ 65 Mb / file Complete scenario over the two grids: ~ 1.6 Gb

  20. Model Intercomparison

  21. Original data (Tb) Obs/Mod Agreement Level Display Size bins controls Tuning Level O3 clouds Dispatching Wind direction Finder Ext. Contracts Display PM Wheel Ammonium Sulfate Nitrate Pedals Deadline Lever JRC Processing Model Intercomparison (I)

  22. Model Intercomparison (II) EMIS Emissions QAQC Ratio checks Scale Comparison GOOGLE EARTH MODELLING 3D (X-Y-T) Hourly data AQ, Meteo VALID Statistical Module Multi-models obs .vs. models Pre-processing ASCII-BIN  CDF EMISSIONS PLANE Multi-models 2-D Monthly data OBSERVATIONS AQ, Meteo Available to all participants through WEB page

  23. Further analysis (vertical profiles, …) could be anticipated by requesting additional outputs from modelling groups. First version available at reception of first AQ results Model Intercomparison (III)

  24. Time schedule

  25. POMI : Overview (VI) Evaluation Software. Others Integrated Assessment FS Meteo (I) FS Meteo (II) Analysis 2012 CLE&AQP 2010-2012-2015-2020 2005 CES Simul. 2012 CLE&AQP CES 2005 2010-2012-2015-2020 Emis. Inv. Traffic modelling 2005 2012 CLE&AQP INEMAR update Bound. C. 2005 2010-2012-2015-2020 M A M J J A S O N D 2009 2010 Progress Meetings Kick-off Final M

  26. Time schedule (I)

  27. Next meeting (place & date) Free participation. Contributions to be sent AOB

More Related