Versions Compared

Old Version 32

changes.mady.by.user Sean Leonard

Saved on

compared with

New Version Current

changes.mady.by.user Sean Leonard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagebash
titlemake a single final file using the cat command and copy to a useful work directory
collapsetrue
# remember that things after the # sign are ignored by bash 
cat *.out > first_job_submission.final.output  # Remember that the * wildcard will take things in alpha order, if you want you can list each file separately to control what order they go into the new file.
mkdir $WORK/BDIB_GVA_2015
mkdir $WORK/BDIB_GVA_2015/Day1
mkdir $WORK/BDIB_GVA_2015/Day1/first_tacc_job  # each directory must be made in order to avoid getting a no such file or directory error
cp first_job_submission.final.output $WORK/BDIB_GVA_2015/Day1/first_tacc_job
cp *.sge $WORK/BDIB_GVA_2015/Day1/first_tacc_job
cp *<job-ID> $WORK/BDIB_GVA_2015/Day1/first_tacc_job  #your job-id is the string of numbers following the .o and .e filenames

 

Moving beyond the preinstalled commands on TACC

If (or when) you looked at what our edits to the .profile file did, you would have seen that the last lines were a series of "module load XXXX" commands, and a promise to talk more about them later. I'm sure you will be thrilled to learn that now is that time... As a "classically trained wet-lab biologist" one of the most difficult things I have experienced in computational analysis has been in installing new programs to improve my analysis. Programs and their installation instructions tend (or appear) to be written by computational biologists in what at times feels like a foreign language, particularlly particularly when a particular when things start going wrong. Luckily TACC (and the BioIteam) help get around a large number of these problems by preinstalling many programs if you know where to look.

...