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 »

Duplicate and then modify the page to reflect what your co-op will be doing.

Move the duplicated document under here: Startup Guides for Co-op Students

Welcome to WARG

We’re happy to have you on board as our new [position]! To aid your first few days here at WARG, we have created a startup guide that you can refer to to see what your project will be, key contacts, and some steps you’ll have to take.

Contact information

These are your day to day contacts:

  • Mentor: @[name]

    • Your mentor is responsible for guiding you throughout your co-op (e.g. daily syncs)

  • Manager: @[name]

    • Your manager is responsible for the administrative aspects of your co-op (e.g. evaluations)

Additionally, feel free to contact the WARG leadership at any time if there are any issues that cannot be resolved through your co-op manager: Lead List

  • Subteam leads: @[name] @[name]

    • Subteam leads are responsible for the subteam you are part of

  • Directors: @[name] @[name]

    • Directors are responsible for the overall operation of WARG

  • Safety captain: @[name]

    • The safety captain is responsible for everyone’s safety

About WARG

WARG’s purpose is to:

  • Enable UW students to learn about and develop innovative new aerial robotic solutions through collaboration and non classroom instruction

  • Expose UW students to engineering challenges, such as mechanical, electrical, and controls

  • Expose UW students to organizational procedure, such as project management, documentation, finance, fundraising, and marketing

  • Provide UW students the opportunity to work with academic and industry professionals advising WARG

Copied from the team charter: Team Charter

To meet these objectives, we compete annually in the AEAC student competition. For the most recent competition in 2024 May, we developed a quadcopter aircraft (project Pegasus).

[images]

The [name of subteam] subteam is responsible for [subteam responsibilities]. For the [term] term, we are focusing on [general overview]. Your project, involving [a few words], will [explain how the project will help the subteam and WARG in general].

Administrative tasks

Pre 1st day tasks

Safety training

Please complete the all of the following:

  • SO1001 Employee Safety Orientation
  • SO1081 Workplace Violence Awareness
  • WHMIS 2015 (you do not need to complete this if you have the Workplace Hazardous Materials milestone on your UW transcript)
  • SO1010 Laboratory Safety
  • Engineering Student Machine Shop Orientation [include or exclude this as required]

To start the safety training:

  1. Go to UW LEARN

  2. At the top, click Self Registration

  3. Find and click the course name

  4. Click Register

  5. Once enrolled, you can find the course again on the home page under All

Join Discord

WARG uses Discord as the primary means of communication.

1st day tasks

WARG bay

  • Meet with your co-op mentor and manager
  • Tour the WARG bay
  • Get the bay code

Scheduling

Accounts

  • Join additional sites and accounts: TODO LINK

Bootcamp

  • Start the bootcamp: [link to subteam bootcamp]

1st week tasks

Onboarding

Project TODO

[THIS IS AN EXAMPLE PLEASE REPLACE. Sahil is writing an old task here as an example of what to do]

Give context

Currently, the firmware bootcamp that WARG uses as a training platform for onboarding new recruits is outdated and lacks succinct documentation. We have received feedback that it is too hard to follow and believe it costs us talent. You will be implementing the firmware application for the bootcamp and writing the associated documentation that new bootcampers will use when completing it.

Specify the action from a broad point of view

Sahil Kale has given direction to make a new bootcamp for the winter 2022 recruitment season. The new bootcamp will have the following requirements

  • Introduce individuals to low-level development in the form of protocol development and STM32 peripheral configuration

  • Give exposure to our tooling (STM32 Cube IDE, cmake, bash, git)

  • Fun to complete, and requiring less than 4 hours of work for a new first year with knowledge of C or C++ to complete

Give concrete next steps

After you are finished onboarding, here are the tasks that will occur:

  • Meet with Sahil Kale and @hardwaredesignerhere to discuss the implementation of the bootcamp from a high level standpoint - what will the bootcampers be implementing and basic electrical architecture
  • Develop the ‘solution’ firmware that other firmware team members will use as the answer key on a development board
  • Work with our EE team to bring up a PCB that members can use for the bootcamp, and validate your firmware on it
  • Write the surrounding documentation required for bootcampers to complete the bootcamp successfully

Appendix

  • No labels