Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • H hermesv3_bu
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • hermesv3_bu
  • Issues
  • #92
Closed
Open
Issue created Jun 01, 2023 by mguevara@mguevaraDeveloper

Shipping vertical emissions: Update master/production + create new tag

@ctena ,

Currently in HERMESv3_BU we are assuming that all shipping emissions occurring in port areas are released into the lowest vertical layer of the model. This assumption is hardcoded in the code as follows (line 597 of the shipping_port_sector.py script):

dataframe['layer'] = 0

Several studies suggest that this assumption can lead to an overestimation of concentrations in the vicinity of the port areas (e.g. Badeke et al. (2022). FMI recommends to inject emissions from ships between 30 - 100 m.

To reflect that in HERMESv3_BU, I propose to modify the line I mentioned above as follows:

dataframe['layer'] = 1

It's not an ideal solution but it's the best we can do for now to better reflect vertical distribution of these emissions. I already tested this change in the framework of VITALISE and the model works well and improve performance of AQ modelling results.

The idea would be to implement this change in the master and production branches of HERMESv3_BU, and then create a new tag that can be used to update auto-CALIOPE and auto-MONARCH.

FYI: @jmateu , @ojorba , @molid , @drodrig1

Assignee
Assign to
Time tracking