Hours and Expectations

👍Rule of Thumb

• Focus on completing the work, not a strict schedule.

• Respect other’s choices of their work hours - you can send an email late Saturday night, but do not expect a response until Monday.

🎙Lab Meeting

Our lab meeting is a one-hour formal presentation. The presentation is scheduled every 4 weeks, with a main presenter rotation schedule pinned in the #current slack channel.

Some pointers to formulate a good presentation:

• think of your presentation as selling YOUR product.

• general structure: background, motivation, results, discussion

• motivate your project: what's the current limitation, why is it important?

• the meat is always your results; typically, results = figures.

• focus on the logic flow of your results and how they connect

📝Journal Club

Journal clubs are usually two weeks before the main lab meeting and presented by the same lab presenter. The goal is to provide a thorough background of your project via presenting a good published paper in the same field of your project.

Every four weeks. See handbooks for more guidelines on how to make a good JC presentation.

🔎Open Code Review

[Currently on hiatus]

In code reviews, we will discuss and sync joint efforts for main software development in the lab.

Currently the focus is the development of AMBER.

This is a more technical session. Lab members will join each session based on their current projects and interests; no mandatory participation is expected.

Every four weeks.