• System Architecture
• Requesting cluster access
• Accessing the cluster
• Job submission
• Software
• BIAC Sample Scripts
• Interactive jobs
• Advanced Bash/Python Submission Scripts - Provided by Dr. Scott Huettel's lab, the scripts included here will check FSL parameters to make sure jobs do not get “stuck” running on the cluster, and submit multiple jobs in a smart way so individual users do not tie up the cluster at any one time.

The BIAC cluster is a Linux-based processor put in place to analyze any type of data. You will work on the cluster though a terminal window by writing commands one line at a time. In order to set up access to the cluster on your computer, you need to be behind the DHE firewall. Being at BIAC or on a DHE wireless network puts you within the medical center firewall. If you are not within the med center you can request access to the DHE VPN via biac-help@duke.edu.

To connect to the cluster, you will need XWin/Putty from windows, or Terminal with Xquartz from Mac

• Accessing the cluster

qinteract is also known as the ‘interactive node,’ because it allows you to interact directly with your data on Munin (or whatever server). It also contains the “packages” (FSL, CMTK, FreeSurfer) that BIAC has installed. You can access the GUI’s for these packages by typing in their appropriate commands once in qinteract.

• List of packages: http://wiki.biac.duke.edu/biac:cluster:packages
• Getting on: log onto the cluster, in the command line (username@cluster: ___) type “qinteract” if prompted, type yes, and then enter your cluster password.
• Congratulations! You are now on the “interactive node.” Access your study data by typing “cd `findexp Study.01`”

• ls - “list scripts” displays the contents of the directory
• ls -ltr - ls w/ time and date
• cd - “change directory,” to be followed by the name of the directory you want to go to
• mkdir - “make directory,” to be followed by the name of the directory you want to make
• gedit - will open a text editor, to be followed by the name of the text file you'd like to edit
• rm - “remove” followed by what you'd like to remove - be careful!
• cp - copy
• qdel - delete job
• qstatall - display active jobs

• If you command line is gone in the cluster, as in you don’t have the prompt to type something, make sure nothing is open in gedit (for example batchMakeFSL_Data is open using gedit – click out), click ctrl+c
• In order to avoid this, follow commands with an &
• Hit the up arrow in order to go to the previous written command
• Hit tab in order to fill in a file, script, or directory name
• If there are multiple files with that name it’ll fill in up to where they differ
• If you’d like to work the command on all files with that particular prefix, immediately follow the prefix with * (for example “gedit batch*” would open all scripts that start with batch)
• To cd to previous folder type cd ..
• Scripts with tildes (~) are there as a backup service, ignore, don’t use, can be deleted if you make sure the proper script is current (example batch_QA versus batch_QA~)
• By typing qstatall (no folloing arguments necessary), you can look at the active jobs on the cluster
• By typing ls –ltr you’ll have a list of files with a timestamp/ more details
• In order to paste from windows into linux (example gedit or the FSL GUI), copy using right click and paste using the center scroll button

• Installation
• Management
• System Log

For issues and discussions related to the cluster, visit the Cluster Forum