Skip to content

Lab Manual

Mission

Our mission is to understand the mechanisms of mRNA translation through interdisciplinary research at the interface of experimental and computational biology. We pursue this goal by training independent scientists and collaborating across fields including immunology and cancer biology.

Roles & Expectations

Everyone

  • is motivated to learn new ideas and techniques. Our projects require continuous learning and adaptation. Embrace challenges and learn from setbacks as part of the scientific process.

  • develops independent research skills. First-year members focus on learning core techniques. Subsequently, emphasis shifts to independent problem-solving, experimental design, and mentoring junior members.

  • maintains organized records. Follow systematic approaches for experiments, analysis, and documentation to ensure reproducibility and clarity.

  • is collaborative. Projects build on shared expertise. Senior members are expected to mentor newer members.

  • is respectful. We value diverse backgrounds, working styles, and perspectives.

PhD and Postdoc Trainees

  • Keep track of all academic requirements in a timely manner (for PhD students). This includes setting up thesis committee meetings, finishing course work, and teaching requirements.

  • Work closely with Rasi to craft and revise research proposals and presentations.

  • Be prompt and diligent in your lab duties.

  • Apply for all available sources of stipend and fellowships.

Long-term Research Staff

  • Help move others' projects forward by contributing unique skills.

  • Establish new techniques in the lab and take on risky projects.

  • Manage day-to-day operations such as equipment maintenance and lab duties.

  • Ensure that the lab space is well organized with all equipment and supplies in their assigned location.

PI

  • Provide feedback on research design, execution, and results.

  • Provide feedback on manuscripts, presentations, and fellowship applications.

  • Help lab members meet their training and career development goals.

  • Ensure a vibrant and safe lab atmosphere conducive to learning and research for all lab members.

  • Acquire funding through writing grants.

  • Highlight lab's research and trainees through conferences and outside seminars.

  • Set long-term vision and trajectory for the lab.

  • Manage the portfolio of projects in the lab to balance productivity and impact.

Logistics

Communication

We use Slack for informal non-scientific communication.

We use GitHub Issues for recording and organizing all our scientific communication. All GitHub repositories are set up to automatically ping to Slack upon updates. For more information on how to use GitHub Issues, see How to use GitHub issues and branches..

Lab Notebooks

We use GitHub Repositories to record all our scientific work. GitHub repositories are essentially cloud-synced folders which enable collaborative work, version control, discussion, and project management, all in one place. In our lab, GitHub repositories are divided by projects, and not by individual lab members. Record your day-to-day scientific work as well as fellowship and manuscript drafts in the appropriate project repository. For more information on how to record your work on GitHub repositories, see TBD.

Weekly Updates

We use GitHub Project Boards for tracking progress on individual Issues. Before the end of every work week, lab members update their project board to indicate what Issues they worked on the past week and plan to do so in the next week. Then post a new detailed comment in each Issue with the title Update indicating what you did or plan to do along with links to notebooks, figures, code as appropriate.

Lab Meetings

We have weekly lab meetings on Wednesdays at 3:30pm, and they typically last for 1-1.5 hours. We cycle between short updates by everyone, longer updates by one lab member, journal club, and a no-meeting week every month. See current lab meeting calendar here.s

Work Hours and Vacation

Core hours are 10am-5pm weekdays. Outside these hours, schedules are flexible based on research needs.

Record all time off on the lab calendar. For extended leave, plan experiments accordingly and notify PI in advance.

Contact Info

If you need to urgently contact lab members when they are not in the lab, see here.

External Logins

We create a single common login for ordering using all external vendors. See this page for login information. We have standing POs for a few vendors that we use frequently. Make sure to use the most recent standing PO numbers.

Grant Numbers

See here for information on grant numbers to use for ordering and shared resources use.

Technical How-Tos

We have detailed how-to pages with sub sections for experiments, data analysis, software, and writing.

Onboarding

  1. Join Github and share username with Rasi.
  2. Join Slack and share username with Rasi.
  3. Get access to our lab Github repository for your project.
  4. Give yourself access to the lab Google calendar using the info here.
  5. Get access to rhino computing cluster by contacting scicomp@fredhutch.org. We use this for all computational work.
  6. Get access to lab AWS S3 storage by contacting helpdesk@fredhutch.org. We use this for storing all experimental data and large files.
  7. Learn lab organizational structure for experiments and data analyses.
  8. Learn git.
  9. Learn VSCode and Markdown for writing and version control.
  10. Learn to use Jupyter Notebooks within VSCode and the tidyverse R package for routine data analysis tasks.
  11. Open a GitHub Issue to discuss an idea, collate literature, plan your first experiment, or start a data analysis task.
  12. Get access to lab database for ordering, plasmids, cell lines, oligos.
  13. Add yourself to our lab website (not necessary for rotation students).

Offboarding

Data and Analysis

  1. Create a summary post of key to-do items for your projects in the respective GitHub repository at notes/USER/offboarding_summary.md.
  2. In the summary post, include all boxes that you are leaving for future use.
  3. Move plasmid maps you entered into our plasmid / cell line database into the lab_database folder in Snapgene.
  4. All your raw data should be in AWS S3 under fh-pi-subramaniam-a-eco/data/USER/.
  5. Commit all your presentations to rasilab/PROJECT/presentations/USER.
  6. Put all your fellowship applications reports in rasilab/PROJECT/grants/USER repo.
  7. Commit any code that you wrote from /fh/scratch/delete90/subramaniam_a/user/git/PROJECT to http://github.com/rasilab/PROJECT.

Lab Bench

  1. Give enzyme or expensive reagent aliquots to suitable lab member. If in doubt, ask Rasi.
  2. Put all lab ware (unopened pipettes, tube racks, cardboard boxes) in their common places or give to another lab member.
  3. Throw away all tubes and intermediate samples in the freezer and on your bench.
  4. Throw away any agar plates with bacteria / yeast or tissue culture plates.
  5. Get rid of inexpensive buffer aliquots.
  6. Clean out your drawers.
  7. Put pipettors in drawer 73.

Organization

  1. Go through your oligo, plasmid, and cell line boxes with Rasi to decide what to keep and what to throw out.
  2. Put all your published cell lines and plasmids in a separate box, and change their location in the lab database at http://rasilab.org/db.
  3. Put your oligo and plasmid boxes in the bottom rack of our lab's common –20 ℃ freezer.
  4. Organize your –80 ℃ boxes into the common lab rack.
  5. Give lab key to our lab's current Research Administrator.