FAQ


Overview

The lab machines have the latest version of Windows 10.

Please note that c:/ drive is a very fast SSD hard drive with all the software you need installed. Please keep all data that you need for your projects and classes on the rotary d:/ or e:/ drive. We do not want to run out of room on c:/ as the software takes up a lot of space.

Remember to login with your LSU Credentials, your CCT password does not work. Login using the regular microsoft login and your user name WITHOUT @lsu.edu.

Please remember to back up and remove all software from All the internal drives as they will get wiped for complete re-imaging when we update all the software. Box is a good place to store all of your files when you are on break.

  • Adobe After Effects CC 17.1.2
  • Adobe Animate CC 20.5.1
  • Adobe Audition CC 13.0.8.43
  • Substance B2M 3.1.4
  • Adobe Illustrator CC 24.2.3
  • Adobe Photoshop CC 21.2.1
  • Adobe Premiere Pro CC 14.0
  • Adobe Substance Designer 2019.3.3-3313
  • Adobe Substance Painter 2020.2.1
  • Adobe XD 21.2.12
  • Autodesk Maya to Arnold 4.0.4
  • Autodesk Maya 2020.2 ML
  • Autodesk Houdini for Arnold 5.4.0
  • Box for file access
  • Epic Unreal 4.25.3
  • Git 2.22.0 (with Bash)
  • Google Chrome 84.0.4147.125
  • Firefox 72.0.2
  • Foundry Katana 3.6V2
  • Foundry Nuke 12.2v2
  • Microsoft VS Code 1.48.0
  • Microsoft Visual Studio 2019 16.2.0
  • Pixelogic Zbrush 2020.1.4 FL
  • SideFX Houdini 18.0.532
  • Steam, Vive & Oculus drivers
  • Unity 2020.1.2f1 2019.2.4f1
  • YoyoGames GameMaker 2.2.5.481

Virtual Reality Settings

  • We have one lab account that can be used with the Oculus Rift in the Oculus store and Vive with Steam. For login information go to dmae github link

Accessing Software Offsite or on Personal Equipment

All software in the lab except for Adobe products can be installed and accessed off campus. For software that requires a license server you will need to be on campus within the intranet or access it outside of campus through Global Protect VPN.

A full description of the process is available in the links below. For Adobe products consider purchasing a student license for the duration of the studies if you find that you need it outside of the lab.

Accessing Lab Software

  1. All software can be installed on personal computers except for Adobe Creative Cloud. Adobe applications are ONLY available in the lab.

  2. Installation information for either the PC or Mac version of all other software can be found at the dmae github link.

  3. Email maubanel@cct.lsu.edu if you do not have access to the repository.

Accessing Box for File Storage

  • To store large files it is best to use Box at LSU. You can access it from the lab and at home and allows for offline or only online storage. If you cannot log into LSU Box with your LSU credentials, get a free account online at box.com.
  • If you want to use box without the browser you can download their app for windows or mac at on box.com.

Online Learning

  • We have access to Pluralsite and Gnomon for their amazing tutorials. Login information can be found at dmae github link.

  • We also have access to professional music and sound effects from alibi which includes multi-tracks! This can also be found at dmae github link.

  • If you don't have access to this link then request permission by emailing Marc Aubanel at maubanel@cct.lsu.edu.

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 one-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. The DMAE lab has a capacity of 11 people.

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

  3. 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.

  4. 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.

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

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.

  • Go to CCT GIT

  • 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.

  • 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.

  • 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.

  • On a PC, go to Git Bash (go to git and install git bash) and enter 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.

  • 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:

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

  • 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.

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`

  1. then press enter (be careful of the special characters after eval).

  2. Then type

ssh-add

  1. and enter your ssh password.

  2. Now you should be good for a set amount of time without having to re-enter the password every time.

Line Endings

Since Unix/Mac OSX and Windows have different line endings, it is good to make sure that the database doesn't update every time a different os is used. Git defaults to this being an unresolved conflict. For more detailed information go to github help.

  1. You need to change the core.autocrlf = true on PC and core.autocrlf = input on unix/mac.

  2. On Windows you need to enter: git config --global core.autocrlf true

  3. On Unix/Mac: git config --global core.autocrlf input

Cloning

  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 by cutting 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.

  • git clone git@git.cct.lsu.edu:maubanel/sample.lsu.edu.git
  1. 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 ./>}

Normal Workflow

Just note that git pull is a shortcut for git pull origin master and git push is a shortcut for git push origin master. The default name for <remote> is origin and is used that way in most projects. The default master branch is typically named master.

  • git pull <remote> <branch>     (shortcut for git fetch <remote> and git merge current branch)

  • git add <filename> or git add . (. is wildcard for all unstaged files)

  • git commit -m "add message here of what was commited. Be specific."     (Detailed message of small atomic change)

  • git push <remote> <branch>

Create Repository from Existing Project

  • git init

  • git add .

  • git commit -m "First commit"

  • git remote add origin <directory url>

  • git remote -v (verifies the new remote)

  • git push -u origin master

Branches

Available Branches

  • git branch     (for local)

  • git branch -r     (for server)

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

  • git remote show <remote>     shows what branches your pull and push without remote and branch will default to

Create Branch

  • git branch <branch name>

  • git branch -m <branch name>        (Creates a branch and checks out new branch)

Rename Branch

  • git branch -m <new branch name>         (if on the same branch)

  • git branch -m <old branch name> <new branch name>         (if on a different branch)

Delete Branches 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 Remote Branches

To change to a branch that is not locally on your computer you need to fetch the latest data for all branches on the remote repository. This will copy all the latest commits and branches from the server that you don't have locally.

  • git fetch <remote>     (< remote > defaults to origin)

Change Branches

  • git checkout <branch name>

Merge

  • 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)

  • git branch -v     branch with commit message and hash reference

  • git branch --merged or git-branch --no-merged     show which branches are merged or not merged to working branch

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, and you still want the file deleted

  • git rm <filename>

Deleted by Server and changed by User and you don't want the file deleted

  • git add <filename>

Mergetool

If you have a Mergetool like kdiff3 set up

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

Changes

Diff

Find out what in your working directory, or staging area has changed.

  • git diff <filename>     (if no filename all changes will be shown)

  • <filename>git diff --patience <filename>     (--patience provides more readable diff but takes longer to render)

  • git diff --histogram <filename>     (--histogram is compromise)

  • git diff --staged     (checks the differences in the staged area)

Ammend Commit

  • git commit --amend (ammends new staged files and creates new commit message)

  • git commit --amend --no-edit    (amends staged files and uses same message as existing commit)

  • This only works on a local commit. If you pushed to a server and you want to amend both the local and server follow the above steps and then:

  • Rewind to commit before conflicting

  • git reset --soft HEAD~1

  • Pull the remote version

  • git pull

  • Add the new commit on top

  • git add .

  • git commit -m "message"

  • git push

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. For a single file or two you can just checkout from the previous commit. This is not saved or tracked so use sparingly. You will lose this work though and it won't be tracked. So say you want to revert to your last commit on file1.txt you would type:

  • git checkout file1.txt

To remove multiple files without checking them out. This removes all of your changes without saving history (be careful this is not saved):

  • git reset --hard

If you want to undo the last commit but keep the items in the staging area (uncommitting the changes). Your changes are still there but they are not commited. This way you can make the changes you need then commit your work.

  • git reset --soft HEAD~1

If you want to clean up stray files that you don't want to add you can use. The -n switch will show you what it will do and the -f switch will do what it says in the -n switch.

  • git clean -n

  • git clean -f

Delete Files from Repository

  • Please back up your folder before doing any of the below. These are destructive processes. It is best to keep a copy around just in case you remove files you did not intend to. If you need to get rid of a file that is larger than ther repository can hold you can get rid of the file. If you added, commited and pushed and received an error you need to:

  • Find out list of files that are largest:

git ls-files | xargs ls -l | sort -nrk5 | head -n 10

  • Delete all files that are too large

git filter-branch --force --index-filter

git rm --cached --ignore-unmatch path/to/filename.jpg --prune-empty --tag-name-filter cat -- --all

  • Do this for each file. The force a push:

git push --force --all.

  • A second option is to install a tool that makes it a bit easier. If you need to get rid of a giant file or binary that is blowing up the size of your project the easiest way to deal with it is to install BFG on your computer (npm git-bfg):

  • Go to root of git repository, you CANNOT be in the directory of file your are deleting file and DO NOT ENTER the path, BFG will figure this out on it's own, you just need the filename.

  • git pull

  • bfg --delete-files <filename.ext> (no path required)

Or the directory:

  • bfg --delete-folders "foldername" (or {"comma", "delineated", "listOfFolders"})

  • git reflog expire --expire=now --all && git gc --prune=now --aggressive

  • Entergit status and stage and commit any files that it requrests (often the entire directory gets rebuilt).

  • Now you need to force a push as the histories are different on your computer and the one on the server. Remember this is destructive, the files and folders you have deleted will be forever gone and cannot be recovered.

  • git push --force origin <branch> then follow next step often git push

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. You can only stash what you have staged with a git add:

  • git stash

  • git checkout <branch>

  • git stash pop

  • git stash list     lists all stashed work

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 <git hash>

Working with Remotes

Getting Data from Remote

Reminder that < remote > defaults to origin.

  • git fetch <remote>

  • git remote show <remote>

Pull Single File From Remote Master Branch

  • git checkout <remote>/<branch> -- path/to/file

Show Changes

  • git show head shows the last commit and all changes

  • git show HEAD~1 shows the second to last commit and all changes

.gitignore

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'

Tags

Tag commits with a stable version number or name

  • git tag <version/name of tag> ligth weight tag

  • git tag -a "VERSION#/NAMEOFTAG" -m "ENTER MESSAGE" _annotated tag_

Push tag to remote repository

  • git push --tags

Delete History

Remove Entire History from Repository (CAUTION YOU LOSE ALL PREVIOUS COMMITS)

Since all of the commits history are in the .git folder, we have to remove it. Delete the .git folder:

  • git rm -rf .git

Now, re-initialize the repository:

  • git init

  • git remote add origin repositorydirectory

  • git remote -v

Add all the files and commit the changes:

  • git add --all
  • git commit -am "Initial commit"

Force push update to the master branch of our project repository:

  • git push -f origin master

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 Commands

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

Logging

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)

The deadline for the Master's Application For Degree and Master's Examination & Degree Audit is September 3rd, 2020. The deadline for approval of the final exam is November 18th, 2020.

Request for Master's Examination & Degree Audit

Fill in your Name, LSU ID Major and degree sought. Fill in all classes that you have succesfully completed in section 1. Fill in the remaining courses that you are still enrolled in for point 4. The department will then forward this on to the grad school.

Master's Application For Degree

Fill in the first page of this form. Included below is a template for what should appear in each section. Please make sure you use your lsu email and not your cct email address. Please submit this to the grad school before the deadline.

Graduate school forms can be found at: lsu.edu/graduateschool/forms

.