Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Admin Notes

  • One more meeting @ start of next term

Attendance

Actual Meeting Minutes

 Keeping the WARG inbox clean

Title. Use folders & Labels as necessary

 Spring 2023 Equipment Sell--off
  • End of each term, we can sell equipment to put cash (back) into our cash-box. 24 hours items are listed, FCFS and ig people can bid for it if they want? Maybe just a google sheets with a linked form and ppl can put in name/bid. idk.

  • Usually consider: broken, in need of repair, no longer used items.

  • Parts come with a written paper saying warg is not responsible for safety or damage to items…

Potential list of things we can sell off:

  • older / in a bad state ESC’s.

  • Broken/badly damaged video transmitters

  • ICARUS motors (vtol, we’ll likely not use them again for a while)

  • Older quad/hex motors (we can use them, but don’t really have the parts necssary to actually run them)

  • Large/random props

    • we do use these occasionally, but very rarely for warg purposes (usually thrust stand, mosst recently icarus) and it’s probably better just to sell them off instead of keeping them.

    • We should keep 10-14” props as well as the small props

  • Old ESC’s (T-motor ones)

    • these have failed a large number of times… I would not trust flying anything on them anymore

  • Old GPS stuff / A/v stuff / etc

    • idk do we ever use this?

  • Old 3d printer filament

    • the “USE PLEASE” ASA and the grimy looking transparent PVA?

In the past, we have sold:

  • receivers/transmitters

  • controllers

 Downstairs bay move
  • Confirmed. Moved stuff down on the 17th. Will help vexu move up on the 18th and move in same day.

 Pilot/GCS bring-up program

Anthony Luo Megan Spee

  • Levels for each thing

  • Confluence documentation for each level

  • online quiz + in person demo (for some) levels.

  • Will go from basic (no qualification) up to competition ready?

 Comp Selection Criteria
  • How many people, from which subteams, etc.

  • Megan Spee to lead discussion (hopefully)

 Recruitment & Marketing approach

Georgia Vachon Westerlund

Generally:

  • making sure we are advertising that we are always open to new members

  • allowing members to quickly and easily understand what teams are working on and what they can expect to do on all of those teams

  • on my mind:

    • posterboards explaining our drones (looks cool, easy to understand)

    • WARG branding (banners/stickers/idk)

    • Website to include more info?

The rest of it

  • idk we’ll discuss this in the meeting

 Fall Term budgeting / sponsorship approach

Georgia Vachon Westerlund

  • Also to be discussed. Projected income and areas that need the most funding

(on my mind: printer, rf stuff, electronics)

 Design 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

 Project 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).

 Onboarding 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.

  • No labels