• to learn vim (and vi), run vimtutor
• Vi Quick Reference
• Using vi
• vi reference card
• Vi Lovers Home Page
• The VIM (Vi IMproved) Home Page
• Unix is a Four Letter Word... and Vi is a Two Letter Abbreviation by Christopher Taylor, a Unix and vi guide
• Emacs Commands

• latex: Unix's Word Processing Software.
  To see some example Latex documents that produce slides and papers, import postscript figures, use bibtex, and that use Latex's math mode, look in my public directory (start with the README file): /home/newhall/public/latex_examples/
  Latex Tutorial
• xfig and gimp: for drawing figures that can be saved in postscript, gif, jpeg, and other formats and incorporated into webpages, latex documents, etc.
• xgraph create line and bar graphs. Some examples: /home/newhall/public/xgraph_examples
• gnuplot another graph/plotting application (see the man page)
• xv for editing figures in many formats
• xwd (X Window Dump) use it to capture the contents of a window on your terminal to a figure file.

  xwd > outfile.xwd	# then click on window to capture in outfile.xwd
  

  You can then use xv to edit outfile.xwd and save it in one of several figure formats. See the man page for xwd for more details.
• openoffice Unix application for creating .doc, .ppt, and .xls files. The resulting files are not completely compatable with Windows, so I generally use openoffice to view Windows docs or to create openoffice slides (I don't even try to create .ppt slides with openoffice)

• Using git, subversion, CVS and RCS revision control software
• Safe File Sharing for Group Projects

• Bourne Shell Programming by Robert P. Sayle
• Bash Shell Programming
• Advanced Bash Scripting

• Using Condor on our system
• CS project etiquette page information about using nice, screen, and where to find disk space for huge files
• Write and use scripts. If you have a lot of experiements to run, write a bash, or perl, or python, or ..., script to run the set of experiements and save the results to files (possibly by using script to capture console ouput to to a file). You can also write scripts to setup your experiemental environment, and you can write scripts to process result files and create input files for xgraph, gnuplot, etc. (perl or awk are more useful than bash for file processing). By using scripts, you take the time to write the script once, but you can easily run the script over and over. You can also use scripts to process large experiment output files to extract fields and create files that can be used as input to graphing programs like gnuplot.
• script and dos2unix to capture a terminal session to a file

• time will measure the total runtime of the a.out program, and will give the breakdown of user and system time. For example, the following call to time ./myprog says that my program took 10.083 seconds to run, 0.000 seconds (less than 1 ms) of user-level CPU time and 0.004 seconds of system-level CPU time (my program was sleeping and not scheduled on the cpu for most of its 10 second runtime):

  % time ./myprog
  real    0m10.083s
  user    0m0.000s
  sys     0m0.004s
  
  # here is time for a cpu-bound program.  you can see almost all of its 
  # 7.931 seconds of execution time were due to user-level cpu time
  %time ./a.out
  real    0m7.931s
  user    0m7.928s
  sys     0m0.000s
  

• /proc: /proc is a pseudo file system that provides a file interface to the operating system. Through /proc you can get information about system-wide resource usage and about individual processes running on the system. For example, cat'ing out the /proc files meminfo, swapinfo, loadavg, will give you information about a machine's memory usage, about its swap space usage, and about its cpu load averages. See the man page for proc for more information (man 5 proc).
• gettimeofday: you can add timing calls to sections of code directly. In C, you can call the gettimeofday function around code you want to time. Be careful about not timing code fragments with debug output, because the debug output can distort the real time of the code fragment you are measuring.
• gprof is a profiler for C and fortran programs. To compile, use the -p option:

  % gcc -g -p -o myprog foo.c
  

  when you run your program, a file named gmon.out is created that contains profiling information of the run of your program. You can view this file by running gprof (see the man page for gprof for more information):

  % ./myprog
  % gprof myprog gmon.out 
  

• ntop.org a tool for network traffic measurement
• Paradyn a performance tool for parallel programs

Python

Sockets, http:

MPI and PVM:

GPU computing:

Parallel Algorithms: