Skip to content

Latest commit

 

History

History
93 lines (72 loc) · 4.92 KB

intro-to-group.md

File metadata and controls

93 lines (72 loc) · 4.92 KB

Welcome to the Computational Physics @ GT CSE research group!

The most important thing about this document is that I/we are very glad to have you. You wouldn't be a part of the group otherwise. This document has some parts that are specific to Ph.D. students, but much of it applies to undergraduate researchers in the group as well.

Getting started

CODA

You will need access to the CODA building. GT CSE is on floor 13, and our group is in room S1347. We also hold meetings either in my office (S1313) or one of the conference rooms on the 13th floor. Request this from Spencer. Send him your GTID number. Though times vary, it will likely take a week to "start working."

Websites, software, course numbers, and such

  • Box, located here

    • Purpose: Common location to store things, unlimited space. Put your group and 1-1 updates here.
    • Request access to group Box from Spencer.

  • GitHub organization, located here

    • Purpose: Your code goes here. Keep it up-to-date via commits. I will likely bug you if you don't update your codes via regular commits as you progress.
    • If you're reading this, you already have access.

  • Zotero, located here

    • We have an unlimited shared Zotero group where you should post papers and books relevant to your studies. I also randomly reference many texts, and you can often find them available here.
    • It has an iPhone app, a MacOS/*nix app, a web interface, etc. It is very convenient. After using both significantly, I prefer it over Mendeley.
    • Request access from Spencer.

  • Group email list

    • Upon joining, remind Spencer to add you to the comp-physics@office365.gatech.edu email list

  • Group website, located here

    • Send Spencer a headshot and your LinkedIn, ResearchGate, personal/research website, Google Scholar, etc. for the website

  • Taking a "special problems" or research "class" with me? Find the course and section number for me below

    • For graduate students
      • CSE
        • Special Problems - 30901 - CSE 8903 - B13
        • Teaching Assistantship - 30903 - CSE 8997 - B13
        • Research Assistantship - 32385 - CSE 8998 - B26
        • Doctoral Thesis Preparation - 30902 - CSE 8999 - B13
      • AE
        • Research Assistantship - 93417 - AE 2698 - BRY
        • Doctoral Thesis - 93424 - AE 9000 - BRY
        • Special Problems - 93423 - AE 8900 - BRY
    • For undergraduate students
      • CSE
        • Undergraduate Research Assistantship - 32788 - CS 2698 - B26
        • Undergraduate Research Assistantship - 32880 - CS 4698 - B26
        • Undergraduate Research - 34679 - CS 4699 - B26
      • AE
        • Undergraduate Research - 93418 - AE 2699 - BRY
        • Research Assistantship - 93419 - AE 4698 - BRY
        • Undergraduate Research - 93420 - AE 4699 - BRY

Computers

We maintain access to many (super)computers and testbeds. We maintain a separate page on this here

Research meetings

You will usually have a meeting with Spencer every week (often on Monday). These sometimes involve you and another student (2-1 meetings). During this meeting, you will present an update on your research. We also have an in-person group meeting every week. Some guidelines apply:

  • Have at least one PowerPoint slide for each update, stating the work you did and plan to do in the next week (see examples in the Box updates/ directory).
  • If you make little progress, that's OK! In fact, the weeks you make the least progress are the most important for updates since my job (in part) is to help you.
  • Even if you have little progress because you were busy with coursework or on a vacation, please put this on a slide so I can keep track of things.

Group GitHub Page

We have a group GitHub page. You should keep the software projects related to your research in repositories on this page. We keep all of our software public (open-source), even during development. We often use the MIT license, which is permissive and copyleft. It also allows us to collaborate freely with corporations, like those at NVIDIA and Google, as well as our academic and lab-based partners.

Collaboration

You are expected to collaborate with your colleagues when appropriate. Your colleagues are students within the group and the school more broadly. Part of this is willingly and openly sharing your code and ideas. It makes us all better researchers.

Social activities

We try to arrange a group social activity at least every few months. This means things like going to a neighborhood restaurant or a trivia night, but we do an anonymous poll to see what everyone would enjoy.