Contacting BMI

If you wish to get in touch with Prof. Clifford please email him (gari AT and CC the BMI admin (bmi-admin AT who will help arrange a meeting.


This post outlines what to do, and how, when you join the lab.

  1. Joining the lab
  2. Access to Building
  3. Roster
  4. Listserv
  5. Slack
  6. BMI listserv
  7. Journal club
  8. Google Calendars
  9. Workflow

Joining the lab

If you are a student or postdoc interested in joining the Clifford Lab:

  1. Look at our listing of jobs.
  2. Read Gari’s ethics and expectations.
  3. Send your CV, transcripts, funding situation, and research interests to Gari (gari AT
  4. If you are already at Emory or GT and want to request a 30-min chat, email the admin (bmi-admin AT who will help arrange a meeting.

Access to building

Our office at HSRB requires keycard access.

First, get your Emory ID card from the Emory card office.

Once you have your card, email Leita Young (lkyoung AT to request to have building access granted to your card.


Ask a lab member for an invitation to our Google Spreadsheet roster and add your info.


Go to our Google Group and request access. This is how Gari or the BMI administration contacts all of us.


Most of our group communicates in Slack. Ask anyone in the lab to invite you to the team.

BMI student listserv

Join the listserv for the Department of Biomedical Informatics.

Navigate to and log in.

Under “unlisted lists”, search for cci-students.

Select that listserv and click subscribe.

Journal Club

Students and postdocs attend and present at our journal club.

Check out the website, which also explains how to sign up to present.

NOTE: this is currently paused.

Google Calendars

We have several Google calendars:

  1. The Clifford Lab calendar lists lab members’ holidays/absences, key group meetings, and social events. Ask Gari Clifford for access.
  2. The BMI Talks calendar lists departmental talks, seminars, etc. Ask Barbara Birt for access.


We’ve developed some standard ways to store code, data, and information:

  • Code - store in a private repo on Default license is BSD.
  • Documentation of code - Learn Markdown and write good README files in your GitHub project repo.
  • Lab diary - Google Docs, shared with Gari.
  • Original data - beast:/data/... (this is not something you usually create) … it will soon be mirrored in a synchronised way to a mounted drive on the cluster.
  • Processed data you generate but is not the original data - your home directory on any BMI machine. This is also mirrored on a mounted drive on the cluster. If it’s on your laptop, then use Box or OneDrive to back it up if you have to. Make sure your machine is encrypted. The key point here is that no-one but you should have access to this processed data - partially because it may contain PHI, but also because it must be fully reproducible by your code applied to the fixed original data. When you share copies of the data that have been transformed, filtered, or altered in some way, the research ceases to be replicable and scientific repeatability is lost. Your research becomes useless and the next person will have to do it all from scratch. This happens often and is a constant source of frustration to everyone.
  • Manuscripts, thesis, etc. - use Overleaf and share with Gari. You can use Git to work offline, but merging and resolving conflicts is then your job.
  • References and papers - use Mendeley and insert PDFs of papers and comments on papers and share with the project team.