Versions Compared

Old Version 11

changes.mady.by.user Anthony Luo

Saved on

compared with

New Version 12

changes.mady.by.user Anthony Luo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleDesign Reviews from Profs/Industry experts

This is something we used to do, and we should continue to do!

  • Have some contacts in our e-mails (usually very fast response)

  • Leverage discords && other community forums

Expand
titleProject Goal(s) for fall term

< Section content moved to end of page for (better formatting) reasons>

  • Who will be on-site next term?

  • Focusing on comp stuff

  • Conops kick-offs - we need to be ready. Schedule out meeting times regularly each week for those syncs and architecture meetings to happen.

  • Can leverage existing sync shedules.

  • Increasing sync-schedules for comp specific parts (tracking antenna, RF infra, etc?)

  • Having concrete test & project plans before the term starts

    • not just “what are we going to test” but also making sure “how are we going to test it” is cared for from all sub-teams and there’s points of contact listed for active projs.

    • Hopefully done before next leads meeting (early sept, probably).

Expand
titleOnboarding stuff

  • Workload assessment, being ready for a LOT of new bootcampers

Project Goal(s) for fall term

Objectives: Have entire competition architecture ready & tested. The earlier the better.

  • Comp drone (frame + wiring)

  • Antenna Tracker

  • Landing pad detection & auto-landing

  • Gemini, LTE, other comms solutions?

Availabilities: Who will be on-site next term? How often?

  • Autonomy:

  • Electrical:

  • Embedded Flight Software:

  • Mechanical:

Meetings, Worksessions, Syncs, Workshops

Architecture meetings: When will these happen? How will they be scheduled?

  • As soon as conops comes out. Saturday & Sunday directly after release?

Project Syncs: Which project’s need syncs? Which ones need in-person cross-subteam work sessions?

Worksessions: We will have a bay downstairs, so much more realistic to have everyone coming in together! !

Flight Tests

Scheduling: Aiming to have a flight test every other weekend?

  • Identify what airframes are available (Houston, Pegasus)

  • Identify tasks which need to be flight-tested.

  • Identify how we can break those tasks down so that we bring incremental targets to each flight test.

  • Identify how we can run multiple tests in one flight-test.

  • Identify how we can minimize operator overloading for flight tests (e.g. start running auto-missions, operator only needs to know how to RTL, etc).

Auxiliary Projects

Projects not directly related to this competition season, but likely to be necessary if we want to continue to improve and compete at larger competitions.