Unix environment: Difference between revisions
(see also) |
(grep) |
||
| Line 12: | Line 12: | ||
You will be using [http://en.wikipedia.org/wiki/Regular_expression regular expressions] in your editor, your shell and in other commands. Just about everything. You will need to know how to use them. You can get pretty far with a minimal familiarity of the basics. Keep a [http://en.wikipedia.org/wiki/Regular_expression#POSIX_Basic_Regular_Expressions reference] handy for the odd cases where you need to use the more extensive operations. | You will be using [http://en.wikipedia.org/wiki/Regular_expression regular expressions] in your editor, your shell and in other commands. Just about everything. You will need to know how to use them. You can get pretty far with a minimal familiarity of the basics. Keep a [http://en.wikipedia.org/wiki/Regular_expression#POSIX_Basic_Regular_Expressions reference] handy for the odd cases where you need to use the more extensive operations. | ||
==grep== | |||
The [http://en.wikipedia.org/wiki/Grep grep] command is used to find lines in text files, or in streaming output from previous pipeline commands. Given a regular expression, any line matching | |||
that expression is printed out. The output can be the inverse, printing out any lines that do <B>not</B> match the expression. | |||
Example: select only the bed format lines from a custom track file so they can be used with hgLoadBed. Removing any lines that begin with track or browser: | |||
grep -v "^track|^browser" customTrack.txt > file.bed | |||
Alternatively, if it is known that all chromosome names start with "chr", select only those lines: | |||
grep "^chr" customTrack.txt > file.bed | |||
Both these examples assume there is only one track defined in customTrack.txt | |||
==See also== | ==See also== | ||
Revision as of 23:31, 29 April 2010
Working in the UNIX™ environment
Editor
The most important tool will most likely be your editor. It doesn't matter what you want to use, but whatever it is, learn it well. vi and emacs are the most common editors used in the unix environment. Your choice of editor will become critical when you use your shell command line in its editing mode. There are very good tutorials on the internet for your editor. There is a VI quick start command listing in genomewiki. See also: Editor War.
Shell
There are two shells in common use on unix: bash and tcsh. Next to your editor, your shell command line is going to be a critical element of your efficiency using unix. You will want the command line editing features turned on for your command line to recognize your favorite editor commands. Learn how to use your command line editing feature. Understand what stdout, stderr and stdin are and how to control their input and output in compound shell commands. There are very good bash and tcsh tutorials on the internet. You will never again compose a long command line just to find out it has a typo error in it, and then have to type the whole thing in again. Use your command line editor to rapidly fix the typo to repeat the corrected command.
Regular Expressions
You will be using regular expressions in your editor, your shell and in other commands. Just about everything. You will need to know how to use them. You can get pretty far with a minimal familiarity of the basics. Keep a reference handy for the odd cases where you need to use the more extensive operations.
grep
The grep command is used to find lines in text files, or in streaming output from previous pipeline commands. Given a regular expression, any line matching that expression is printed out. The output can be the inverse, printing out any lines that do not match the expression.
Example: select only the bed format lines from a custom track file so they can be used with hgLoadBed. Removing any lines that begin with track or browser:
grep -v "^track|^browser" customTrack.txt > file.bed
Alternatively, if it is known that all chromosome names start with "chr", select only those lines:
grep "^chr" customTrack.txt > file.bed
Both these examples assume there is only one track defined in customTrack.txt
