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 4 Next »

Topics:

  • Current state of EFS and in general, the team

  • Start of term plan (meeting schedule, worksessions, etc)

    • new intern

    • including new leads

    • availability form

    • Interest form

  • Ongoing projects, including state and goal

  • Intern Projects

  • Bootcamper schedule

    • Bootcamper team role?

    • Priority of projects

  • Update asana?

Current State of EFS

  • The outcome: zeropilot did not fly in comp

    • timelines were clearly not met

    • lack of testing

    • lack of basic functionality

      • had major bugs, for ex, PPM

  • Every year it seems like we try to implement a brand new thing

    • introduction of LOS

      • introducing this new (major) software, without working drivers in the first place

      • one of the biggest bugs: DMA interrupts → makefiles → LOS

      • separation of large repositories (LOS as a submodule in ZP)

        • separate build systems

        • when testing drivers, dealing with LOS as a submodule is kind of weird

      • LOS is meant to be this library of drivers and interfaces BUT it contains the most project specific code you can possibly have (the generated files)

    • LOS/ZP STRUCTURE LOWKEY MAKES NO SENSE:

      • ideally, each drone project has its own repo (for ex, Vanny, Icarus, houston)

        • each containing their own project specific files

          • flight control parameters

          • generated files (from CUBE)

          • etc

        • pulling in (maybe via submodule) ZP, for controls

        • pulling in LOS, for drivers

          • at that point, we should put LOS in ZP

        • Can use getters/setters to pass in HAL functions to LOS Core,

          • LOS drivers call LOS Core so that they can compile

          • If the library cant run on its own, why does it have to be able to compile on it’s own?

    • Acknowleging that this structure makes less sense, we’re going to stick with the current/simpler structure until it flies.

    • introduction of new ZP3 arch

    • IMPORTANT: MUST DISCUSS WITH MORE MEMBERS

Start of term plan (meeting schedule, worksessions, etc)

  • Send out a message

    • introducing the leads for the term and their roles

    • introduce new co ops

    • link lettuce meet for weekly meetings and work sessions

    • mention task interest form, but send it out after our first meeting

  • Its a summer term, which means deadlines in general are pretty flowy

  • Generally a time to rebuild/structure and plan out the next comp cycle

  • Need to talk about work sessions, info sessions, etc

Ongoing projects, including state and goal

  • Waiting until Anni and Ayoung come back

Intern Projects

  • Hardy: competition SM

  • Nolan: TBD

Bootcamper Schedule

  • AADI AND AYOUNG UPDATE THE DOC TO GET PINGED INSTEAD OF ANNI

  • Lets make a Bootcamper support role that any bootcamper can use to ping any members (leads are mandatory) that are willing to help

  • Chris will take weekday session, aadi will take weekend session (make

    • Wednesday 9pm, tentative

Asana

  • asana should be updated once we have our first meeting

Outstanding topics to discuss

  • LOS

  • Nolan’s task

    • Tracking antennae, or HIL if we cant do tracking antennae

  • Ongoing projects, state, and goal

  • No labels