Help Schwab SEPHELP Help in the SEP computer environment matt@sep.Stanford.EDU Matthias Schwab /usr/local/src/our/sephelp/sephelp When working in the SEP computer environment you encounter certain computer tools. This document lists documentation and resources for these different tools. UNIX All machines at SEP are based on the UNIX operating system. It is extremely beneficial to know the basics of UNIX. All UNIX commands are documented on-line: (type man commandname ). If you do not know the command name try man -k keyword . For a more overall description, I suggest Kernighan's UNIX book Kernighan.unix.1984 . If you have never used a UNIX computer you probably should take Phil Farrell's fall computer class Farrell.course.1994 . EDITOR At SEP two different editors are widely used: vi and emacs . The traditional UNIX editor vi exists on any UNIX machine and is a well trusted editing work horse. Any UNIX book documents vi . ...
A tour of SEPlib for new users
(ps.gz 304K) , (src 754K)
by Joe Dellinger, S T and James Rickett
SEPlib is a data-processing software package developed at the Stanford Exploration Project. Many researchers at universities and oil companies would find SEPlib extremely useful if they could only get over the initial hump of learning how SEPlib programs are used. By working through several illustrative examples this document attempts to painlessly introduce novice users to the fundamental SEPlib concepts they will need to understand the available SEPlib self-documentation and manual pages. Concepts covered include self-documenting programs, history files and data files, SEPlib-style pipes, command-line and history-file ``getpar'' parameters, auxiliary input and output, and how to use some of the more useful SEPlib utilities.
The ``unwritten'' computing rules at SEP
(ps.gz 30K) , (src 37K)
by Alexander M. Popovici, Dave Nichols and Dimitri Bevc
This short note is intended for the fresh SEP-er. It is a collection of rules and SEP trivia that are obvious to any SEP student who spent more than a year working on our computers. Since many of the ``senior'' SEP students plan to graduate this year, we thought a formal introduction to our computing environment could be in place. The title is taken from a seminar handout given to the first author by John Etgen a long time ago ... Home directory The directory /homes/sep/username also called your ``home directory'' contains mainly source files and text files, generated using an editor. In other words, files that were ...
List of commands
(ps.gz 28K) , (src 33K)
by Martin Karrenbach
This is a list and brief description of the most commonly used commands. The commands are given with arguments followed by a small description. By including ``sepmacro.tex'' you will get that functionality.
(ps.gz 43K) , (src 210K)
by Kamal, Niki, Joe and Martin
This is is a sample of a report, written in with included interactive figures. To compile and print this document: texpr -s -bib textour
How to organize an interactive document
(ps.gz 105K) , (src 883K)
by Martin Karrenbach
An interactive document is a self contained unit; it can either exist by itself or as part of a report or book. Everything necessary to recreate your paper must be within the paper directory. This document outlines the organization of the paper directory. This document follows the same organizational rules; you can view it, by going to our/word/tutorials/idocorg and typing "cake" . To rebuild all figures type cake figures .
Easy referencing and bibliographies
(ps.gz 29K) , (src 32K)
by Martin Karrenbach
Referencing is easy using bibliographic databases. Currently we have a database with all the SEP reports in it ( SEP.bib ). It is very easy to write your own small bibliography files e.g. martin.bib or segmaster.bib . xwais is the recommended way to search for bibliographies for citation keys. It is very quick and searches all available bibliographies. You also get the citation keys by using sepindex yilmaz . To see the complete bibliography entry use sepbib yilmaz . You can do wider searches by using eg. bibindex yilmaz GEOPHYSICS EAEG which looks for Geophysics and Geophysical Prospecting papers or abstracts. All references will automatically sorted and correctly numbered if there are more than one paper from the same author per year. To see this document: cd /usr/local/src/our/word/tutorials/Sample ; cake bib
How to use cake with interactive documents
(ps.gz 37K) , (src 46K)
by Jon F. Claerbout and Martin Karrenbach
My experience with maintaining 300 illustrations has been distilled to two pages of cake rules. Each directory has a cakefile containing a list ( FIGLIST ) of buildable figure names. All figures can be built with the command cake figures and removed with cake burn . Precious figure files (ones not considered replaceable) are named NAME.save . Karrenbach's activeplot macro launches the UNIX command cake NAME.menu or cake NAME.idoc . The default cake rule is to come up with an Xwindow menu xtpanel or to show a plot with tube or show a movie with X11movie . For unusual actions, you can override the default by making a rule for the target NAME.action .
Xtpanel: an interactive panel builder
(ps.gz 311K) , (src 1365K)
by Steve Cole Dave Nichols
Xtpanel builds interactive panels --- containing objects such as buttons, sliders, and dialog boxes --- from a simple script file or from the command line. With xtpanel, one can quickly add a layer of interactivity to existing software. For instance, a velocity analysis tool can be created in minutes by using xtpanel to add an interactive front end, where sliders choose velocities from a user-specified range, to an existing NMO correction program. Panels can take advantage not only of existing application programs, but also the utilities built into the UNIX operating system. In one example, we use an 80-line script to build an X windows calculator by making a front end to the line-oriented UNIX calculator bc . Another utility built with xtpanel is the xtpanel generator. This is a series of panels that let users build new panels interactively, without having to learn and use the script language.
How to make a CD
(ps.gz 39K) , (src 12K)
by M. Schwab