You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The species database in GEOS-Chem currently primarily includes definitions of advected species. Many chemical species defined in KPP are not includes and are therefore assigned a molecular weight of -1. Daniel Jacob has suggested the following:
Assign molecular weights to all non-transported species. That some are proxies/lumped should not be a limitation – we can just assume MWs for them, and as long as we’re consistent from version to version that would be fine. Kelvin Bates could give you MWs for all these species.
The text was updated successfully, but these errors were encountered:
This is now slated for 12.9.0. In gcpy, we have converted to species database in YAML format and will ideally be reading this into GEOS-Chem instead of having the species database in Fortran. It makes more sense to add the species database updates listed here to the .yml file instead of to the much more cumbersome species_database_mod.F90.
This first draft has been sent to Kelvin Bates and the Chemistry Working Group leaders for assistance in filling in missing molecular weights for some chemical species defined in KPP.
The updated species database may not officially be implemented until GEOS-Chem 13.0.0 because the Fortran-YAML package may rely on the new directory structure in GEOS-Chem that allows us to access common external libraries. See #216 for discussion on that progress.
msulprizio
changed the title
[FEATURE REQUEST] Define all GEOS-Chem species in species_database_mod.F90
[FEATURE REQUEST] Define properties for all GEOS-Chem species in the species database
Apr 15, 2020
The species database in GEOS-Chem currently primarily includes definitions of advected species. Many chemical species defined in KPP are not includes and are therefore assigned a molecular weight of -1. Daniel Jacob has suggested the following:
The text was updated successfully, but these errors were encountered: