Attendance

Light attendance due to midterms, but still vibing meeting!

Others:

Announcements / Admin

• @Anthony Luo design doc freeze discussion.

  • There are still sections that need to be filled in.

  • Midterms week will slow us down for next few weeks

  • Need flight tests to determine operational limits of drone

  • @Anthony Luo to initiate RFC system

    • not much feedback from others

• @Anthony Luo To announce importance of the design document phase 1 paper.

  • What does succeeding on it means for the team?

    • SDC street cred

• @Daniel Puratich Recap flight test 2023-10-14: Pegasus Hover, ZP3.5 M1, & Pilot Trainning

  • @Nathan Green wrong motor configuration, flipped Pegasus

  • ~100 dollar of damage

    • couple props

    • antenna on LTE module

    • no action items following this, have extra props

  • @Daniel Puratich checklist updating

  • @Anthony Luo wants the flight test debrief to contain more data analysis and breakdown of what happened

    • We want people to get reasonable data out of the flight

  • We don’t want to drag out the flight test debrief to take a long time to discuss specifics of logs, @Alison Thompson @Conall Kingshott .

    • putting in the data eventually is useful

    • We test a lot of things on one day bc that's when we have the time and people to fly, @Alison Thompson

      • We shouldn’t run so much simultaneously @Anthony Luo to avoid overloading

  • Flight test debrief / data analysis needs to happen eventually

    • Can be at end of flight test, can be at another time @Megan Spee

  • Split debriefs and flight test into two meetings? @Anthony Luo

  • @R D what is problem with stacking flight tests?

    • Crunching a lot of responsibility on very few people. Leads to more mistakes.

    • @Daniel Puratich in this case, people working on peggy and tubie were split so the task saturation diagnosis @Anthony Luo may not be accurate

  • A flight test is a lot of effort, to test a lot of things, we can’t split it up into lots of days @Alison Thompson

    • It’s a big endeavor to go to a flight test

    • would rather do a big one then a bunch of small ones

    • Not everyone has to attend every flight test @Anthony Luo

      • We have limited people that can fly and people that can drive @Alison Thompson

  • @R D when we have many flight tests on a single day, there’s a concern that a single person is responsible for things on each of the tests. Can we just limit that? Clearly assign scope.

    • @Anthony Luo would allow debriefs to be split up

  • @Megan Spee same day flight tests is more convenient, much more time cost to split it. the worth of getting more attention may not be worth it.

  • @Anthony Luo flight tests overall could be shorter overall if split up.

  • @Alison Thompson Vehicles and Tubie flight same time bc the drivers and cars required.

    • @Anthony Luo not every flight test requires drivers, really only Pegasus bc of size and stuff

    • @Anthony Luo autonomous missions on houston are easy if people get trained. tubie is much easier to fly then Pegasus. can unblock teams by splitting tests.

  • @Anthony Luo was not a fan of debrief and stacking and thinks it went poorly, revisit at end of meeting, this is kind of a big discussion

• @Daniel Puratich Announce flight test 2023-10-21 Flight Tests

• @Daniel Puratich Do we want to run an AEAC sync next week?

  • midterms week next week

  • lotta people offsite

  • so we gonna run it

  • Meeting mins: 2023-10-24 AEAC 2024 Sync

•  

Action Items (we do these right now and assign immediately)

Updates / Blockers / Finished items

Airframe ON TRACK

Payload In pog-ress (pog)

Aerodynamics In pog-ress (pog)

Sensors In pog-ress (pog)

PDB In pog-ress (pog)

Harnessing In pog-ress (pog)

Gemini In pog-ress (pog)

Antenna TrackerIn pog-ress (pog)

Auto-landing Not started

Pathing

Testing goals for near future

Arch Doc