2023_10_20 - Flight-Path-Analysis/FlightPathAnalysis GitHub Wiki

Flight Path Analysis Meeting

Meeting Date: Oct 20, 2023 - 10:00 CT / 11:00 EST / 9:00 MST / 15:00 UTC

Meeting Location: Zoom

Chair: Andre Guimaraes

Announcements / Updates

  • 47 days until project deadline
  • [Please put any other announcements or updates here]

Agenda Items

Any Other Business

GitHub Tutorial

  • At the end of the meeting, for anyone that needs it, I can host a tutorial on GitHub and all the important features we need.

Minutes:

Recording: Fathom Link

Attendees:

  • Andre Guimaraes (Chair)
  • Hannah Solomon
  • Dimindu de Silva
  • Ruth Meadow Mac-Leod

AI-Generated Minutes

1. Announcements / Updates

  • The project deadline is in 47 days.
  • Issue with adding people to the GitHub project is being resolved; new invitations have been sent.

2. Current Status of the Project

  • Andre provided an update on the project, outlining the components and packages developed.
  • The team recognized a gap in weather data, which is critical for flight path analysis.
  • Focus on flights from JFK to Los Angeles, emphasizing the potential challenges in obtaining specific weather data.

3. Discussion Points

  • Project Name: Temporarily agreed on "Flight Path Analysis." Final decision deferred until more project outcomes are clear.
  • Defining "Optimal Flight Path": Discussion around considering various metrics, including fuel consumption and standard flight corridors.
  • Relevant flight routes: The team will start by analyzing data from January 2023.

4. Task Assignment

  • All members are to focus on gathering pertinent weather data.
  • Tasks regarding the analysis of fuel consumption and flight data distribution among members.

5. Any Other Business

  • No other business was discussed at this time.

6. GitHub Tutorial

  • Andre conducted a tutorial on using GitHub, with specific attention to cloning repositories, creating environments, and basic command usage.
  • Discussion about using JupyterLab for the project due to its advanced features compared to the standard Jupyter Notebook.
  • Members are encouraged to use VS Code for easier Git management.

7. Closing

  • The meeting concluded with agreements on next steps and responsibilities for each member.
  • Andre created a new GitHub issue for a feature request related to data analysis and assigned it to Ruth and Dumindu.
  • There was a suggestion to consider a hackathon day for intensive coding and problem-solving.
  • The meeting was adjourned at approximately 1:20 PM EST.

Next Meeting: Oct 27, 2023 - 10:00 CT / 11:00 EST / 9:00 MST / 15:00 UTC

AI-Generated Transcript Summary

The meeting started with Andre discussing the agenda and highlighting the upcoming project deadline. The team encountered some technical issues with GitHub project invitations, which Andre resolved by sending another round of invitations.

During the meeting, the team delved into the specifics of the project, including the significant need for weather data along selected flight paths. The discussion revealed potential challenges in data acquisition, particularly concerning the format and accessibility of weather databases.

The concept of an "optimal flight path" sparked a debate, with team members considering different metrics like fuel efficiency and the influence of weather conditions. The project's naming was also discussed, settling on "Flight Path Analysis" for the time being.

As the team moved to task assignments, there was a strong emphasis on the necessity for weather data, pivotal for the project's next phase. Members shared their experiences and committed to specific roles, particularly around data gathering and analysis.

The latter part of the meeting was educational, with Andre walking the team through GitHub functionalities. This tutorial covered several aspects, from setting up and cloning repositories to creating conducive work environments. JupyterLab was recommended for its efficiency over other platforms, and there was a consensus on using VS Code for its streamlined Git operations.

In conclusion, responsibilities were allocated for upcoming tasks, and the idea of hosting a hackathon was floated. The team displayed a collaborative spirit, ready to tackle the project's demands in the coming days.