Closed mvieno closed 5 years ago
Hi Massimo, cc @gitpeterwind, @JanEiofJonson Yes, this is a mistake, likely to do with the special treatment of AIS that had to be done before the vacations. We should really clean up the system and put the AIS emissions into our more standard formats. This will fix the above problem without the need for extra code.
I can add that the ship emissions that we have for 2015 is a global set. (VOC not included). The new set includes the effects of the SECA in the North Sea and the Baltic SEA (and outside North America etc for that matter). We also have similar sets of emission data only for the Baltic Sea for 2014 and 2016. In addition we have a an emissions set for European waters for 2011 (a warning here as the 2011 was generated without AIS data from satellites, and may have missing data/regions.
The example run included with rv4_32 shows how to use additional shipping emissions when this are not included. The emissions included with rv4_33 include shipping emissions.
Hi All, in the new rv4.15 the variable Emiss_mgm2_xxx does not include the emission from shipping. Perhaps, this was wanted but I found it cleaner, and more useful for checks, if “all” the emissions are included in the Emis_mgm2_xxxx prognostic.
The shipping emissions are properly read in tho.
I think in the Emiss_mgm2_XXXX all emissions should be included (e.g. DMS, soil NOx, shipping, etc.). For non "MSc-W" users the Emis_mgm2_xxxx variable is a useful way to check that new emissions inputs are ok.