Add LTO emissions to grid post-processing - #161
Open
ian-ross wants to merge 3 commits into
Open
Conversation
Co-authored-by: GPT-5.5 <openai-codex-gpt-5.5@pi.local> Pi-Model: openai-codex/gpt-5.5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds "surface" emissions to the gridded NetCDF output generated by the trajectory-to-grid post-processing. For the moment, this includes only LTO emissions. For each flight, LTO emissions are assigned to the locations of the origin and destination airports as follows:
This approach is based on the behavior of the legacy trajectory builder, which starts it trajectory simulation at the origin airport's location at the altitude of the beginning of the "non-LTO" part of the trajectory. There is thus not a part of the trajectory ground track between the origin airport and the beginning of real trajectory points over which we could distribute takeoff and climb emissions, so the only thing we can really do is to assign those emissions to the origin airport location. The same sort of reasoning goes for approach emissions at the destination airport. And I split idle emissions 50/50 because I couldn't think of anything better to do.
@aditeyashukla Does that seem like a reasonable approach? This will have to be reviewed if the takeoff and landing phases are ever modeled more directly, but that's something for the future.
You can see what the NetCDF data containing the LTO outputs looks like in
/home/iross/data/AEIC/oag-2019/test-oag-2019.ncon Hex.