Email Etiquette

  1. Only discuss public matters. There is no such thing as privacy in an email.

  2. Don’t ‘email angry’. Email is not an effective forum for venting and is much better at summarizing. If an issue has arisen that causes anger, either meet in person or talk on the phone.

  3. Respond in a timely fashion. If you are not able to respond right away, please respond with a receipt and a timeframe of when you will respond. Not responding witin 24 - 48 hours is not acceptable.

  4. Refrain from sending on-liners. You can put No Reply Necessary at the top of an email if you don’t expect a response.

  5. Avoid using shortcuts, emoticons, jargon or slang.

  6. Keep it professional. Imagine your grandmother is being CC’d on the email.

  7. Be clear in your subject line.

  8. Don’t email more than one address per receipient. If you don’t know which they prefer, then ask.

  9. Keep it short and get to the point.

  10. Remember, the email you write is a reflection of you.

Lab Etiquette

  1. Make sure faculty television is turned off if you are the last person to leave the lab.

  2. Make sure the door is locked if you are the last person to leave the lab. The door is locked by the switch on the latch assembly on the side of the door.

  3. Please try and eat in the cafeteria area just outside the second floor staircase. If you absolutely have to eat in the lab because class is starting please dispose of your food garbage in the cafeteria area. We don’t want the lab to smell like food or attract critters.

  4. Log off of your computer and make sure that it goes into sleep mode. Please do not disable the sleep functions of the computer.

Accesing Tree From Off Campus

You can access the campus network drive tree from home using Cisco VPN. Please be aware that the tree servers at school are not backed up and if the discs get corrupted the data will be lost. Please be sure to have another backup for all important data for you projects. ## Apple Mac

  1. First connect to Cisco VPN using Mac Remote Access to install and run the VPN.
    Alt tag

  2. Go to Finder | GO | Connect To Server.

  3. Add to Server Address: smb://tree.cct.lsu.edu/dmae_students. If it asks you to login please use your CCT credentials.
    Alt tag

  4. You are now connected to the campus network. Please be aware that all your internet traffic will be going through the school servers. You will have access to the tree drives and all the network access you enjoy on campus.


  1. First connect to Cisco VPN using PC Remote Access

  2. Right click on Computer in File Explorer and select Map network drive.

  3. Pick a drive letter that is not used and in folder type \\tree.cct.lsu.edu\dmae_students

  4. Press Finish and then you can make an alias of the drive on your desktop or pin it to your tool bar.

  5. You are now connected to the campus network. Please be aware that all your internet traffic will be going through the school servers. You will have access to the tree drives and all the network access you enjoy on campus.

Installing Maya Off Campus

  1. If you have not installed the VPN, please go to PC Remote Access or Mac Remote Access to install and run the VPN.
  2. Connect to Cisco VPN with your CCT login credentials.
  3. Connect to the tree drive (look at Access to Tree link above).
  4. Download Maya from the Maya2017 folder for your system, both the PC and Mac version are included.
  5. Unzip (if necessary) and install Maya. It will ask you whether you have a license key or license server, select the Single License Server option.
  6. If you need to enter the license server click on this license server link

Accessing Nuke Off Campus

If you have not installed the VPN, please go to PC Remote Access or Mac Remote Access to install and run the VPN.

  1. Connect to Cisco VPN with your CCT login credentials.

  2. If you have Nuke installed and running skip to step 5 otherwise proceed to step 3.

  3. Download the latest version of Nuke installed in your computer. You can find it on the server at school //tree/dmae_students/software/nuke. Please use these copies so we are all on the same version.

  4. Install Nuke.

  5. Run Nuke to use the software. You should have a free trial version for a couple of months.

  6. Once your trial version runs out contact maubanel@cct.lsu.edu for how to connect to the license server.

You can also run your personal laptop version of Nuke on campus and follow the above instructions without logging into the VPN.

Digital Tutors New User Sign-Up

  1. Sign up by registering for our Digital Tutors group through : LSU Digital Tutors. You need to be added to the DMAE_students group to see the contents of this link.

  2. Login and access material. Remember to log out when you are finished as there are limited digital tutor seats that allow a number of people to use it at once.

  3. If there is no more space or you have problems registering please email maubanel@cct.lsu.edu

Logging in to Digital Tutors

  1. Log in to Plurasight and click on Sign In. Then at the bottom you need to click on sign in at Sign in with Digital-Tutors.
    Alt tag
  2. Sign in with your Digital Tutors username and password.


  1. You can access Gnomon through: LSU DMAE GNOMON. You need to be added to the DMAE_students group to see the contents of this link.
  2. Please remember to log out when you are finished, we only have a single seat for now.

Registering with CCT GIT

CCT has a private GIT repository. I suggest you get comfortable using command line with GIT. The advantages far outweigh the disadvantages and it is worth learning. For text editing be careful to use an editor that DOES NOT add meta data to the file. The program recommends Sublime Text (free to use) but there are many other popular choices. You do not need to use the Cisco VPN to access GIT off campus and can access it from anywhere with an internet connection with a valid SSH key.

  1. Go to CCT GIT

  2. Register yourself by creating a new account. Add your Name Username email and password. Please use your real name and not an alias or nickname.
    Alt tag

  3. All traffic is governed using an SSH key. You need to generate an SSH key that then gets stored in a hidden folder on your harddrive. I suggest using the same key on all computers to fascilitate administration on your part.

  4. On a Mac, go to Finder, choose Utilities from the Go menu. Find the Terminal application in the Utilities window. Double-click the Terminal application. Enter the following command: ssh-keygen -t rsa. Press the ENTER key to accept the default location and name. Type in a passphrase, then enter a second time to confirm.

  5. On a PC, …

  6. Copy and paste the entire contents of the id_rsa.pub key (using a standard text editor, preferably sublime text) into https://git.cct.lsu.edu/profile/keys the Key box. It should look something like this:
    Alt tag

  7. Press Add Key, and you should be set to go.

  8. You can access the CCT git repository at git.cct.lsu.edu.All the projects that you are a part of will be listed on the Front Page.
    Alt tag

PC Password

  1. If you are tired of entering your SSH password everytime in Git Bash you pull or push the repository, you can set it up so it remembers the password until you log off or reboot.
  2. Open Git Bash and go to the directory with the repository you want to use.
  3. Type
    eval `ssh-agent -s`
  4. then press enter (be careful of the special characters after eval).
  5. Then type
  6. and enter your ssh password.
  7. Now you should be good for a set amount of time without having to re-enter the password every time.


  1. Create a GIT repository on your computer by cloning an existing project. If you are starting from scratch follow the directions when creating a New Project on the website.

  2. Otherwise you need to clone a git repository with:
    git clone git@git.cct.lsu.edu:maubanel/sample.lsu.edu.git
    Cut and paste project site from the website and replace above git@git.cct link with the one of the desired project. Please note that this will create a new directory with the one used for the project. If you want to use your own you can create the project inside an empty existing directory using:
    git clone git@git.cct.lsu.edu:maubanel/sample.lsu.edu.git .
    Alt tag

Normal Workflow

  • git pull origin BRANCH-NAME

  • git add -A .         (‘.’ is wildcard for all changed files, can instead use a filename if you want to only add a single file)

  • git commit -m         (Detailed message of small atomic change)

  • git push origin BRANCH-NAME


Available Branches

  • git branch         (for local)

  • git branch --all         (for local and server)

Create Branch

  • git branch BRANCH-NAME

  • git branch -m BRANCH-NAME        (Creates a branch and checks out new branch)

Rename Branch

  • git branch -m NEWNAME         (if on the same branch)

  • git branch -m OLDNAME NEWNAME         (if on a different branch)

Delete Branch Locally

  • git branch -d BRANCH-NAME         (only deletes branch if there is no work)

  • git branch -D BRANCH-NAME         (Deletes branch and throws away all the work)

Delete Branch On Server

  • git push origin :BRANCH-NAME

Get Branches locally from server

  • git fetch

Change Branches

  • git checkout BRANCH-NAME


  • git merge BRANCH-NAME --no-ff         (No fast-forward, preserves complete history)
  • git branch --merged         (checks to see if branch is merged)
  • git branch --nomerged         (checks to see if branch is not merged)

Merge Conflicts

  • git checkout --theirs FILENAME         (Take the server version (deletes local) of the file in the conflict if you cannot resolve with say a binary file for example)

  • git checkout --ours FILENAME         (Take the local version (replaces server) of the file in the conflict if you cannot resolve with say a binary file for example)

Deleted by User and changed on Server

  • git rm FILENAME

Deleted by Server and changed by User

  • git add FILENAME

If you have a mergetool set up

  • git mergetool        (to launch mergetool to resolve any conflicts)


  • git diff FILENAME         (if no FILENAME all changes will be shown)

  • git diff --patience FILENAME        (–patience provides more readable diff but takes longer to render)

  • git diff --histogram FILENAME         (–histogram is compromise)

Ammend Commit

  • git commit -amend (Creates new commit message)

  • git commit -amend -C HEAD        (Uses same message as existing commit)

Delete Local changes

Sometimes not all work is worth saving. You often try something out to decide that you do not want to pursue this task anymore.

If you want to revert to what was previously on the server then do the following (this is destructive and this work cannot be accessed again):

  • git reset HEAD

  • git reset --hard

  • git pull


If there are files on the server that are in your .gitignore file, you will need to remove them from the server with:

  • git rm -r --cached .

  • git add .

  • git commit -m 'Fixed untracked files in .gitignore'


To tag a version just enter:

  • git tag TAG-NAME

Move Changes to New Branch

If you are working on the wrong branch there is an easy way to stash your changes and have them pop back on a new branch:

  • git stash

  • git checkout BRANCH-NAME

  • git stash pop

VI Editor

Sometimes when git merges, it ends up sending you to the VI editor to record a message. If so the commands are:

  • i         (to go into insert mode to edit text)

  • esc         (to leave insert mode, so you can save and exit)

  • :x         (to save and exit)

  • :q!        (to exit and ignore changes)

Mac Terminal Shortcuts

  • command k        (to clear window as ‘clear’ doesn’t work as it comes back with next git command)


To find out where the project is at and whom has done what:

  • git log --all --format='%aN' | sort -u         (to list all contributors)
  • git log --oneline         (to show a list of all pushes with just the comments)
  • git lg --author=“NAME”         (to show a log of all commits from a single author)
  • git lg --author=“NAME” --since“1 week”         (time limited log of commits from a single author)
  • git shortlog -sne        (shows total number of commits from entire Terminal)

Squash merges

If you want to combine multiple merges into one (sometimes when there are conflicts it creates extraneous commits):

  • git rebase -i HEAD~6         (or any previous number)

Cherry Pick from Other Branches

If you want to pick out individual commits from a branch

  • git cherry-pick BRANCH#