Practical SeisX -- Questions I have been asked

What are the Hot Keys that I should know about?

March 11, 2004 I have just learned about the b and v hot keys. They toggle the up and down cursor controls between time displayed and the scroll increment. When you first start a SeisX session, the up and down arrows control the time window (Thick scroll bar). Try pressing the b button and then the arrows. They now control the thin scroll bar and your 3D display increments. The v button will return to the time display. I have used SeisX for all these years and never know about this feature!

Here are the hot keys I normally use:

How do I increase the amplitudes of a seismic line

Question: I've just processed my seismic line, doubled the amplitudes and yet the display looks the same, why?

Answer: It's true, you have doubled the amplitudes but you have also doubled the peak amplitude as well. Users normally use the peak amplitude to display their data. It's all relative, what you have to do is use the segy editor and change the value of the peak. If you decrease the number by 50 percent, your display will appear as if it has been doubled. You don't even process your data to balance your amplitudes!

Where are the error log files if I have a problem?

Answer: They are appended to the file SeisX.log stored in your /tmp directory. If you are having a problem, it's a good idea to past these messages in an email to the SeisX support staff. Here is what a few of my error messages look like with SeisX 4.0 
cd /tmp
more SeisX.log
11/20/03 16:23:39: ERROR - Load_SEGY_3D: FILE entry already exists load_test2 STK : 0.
11/20/03 16:26:17: ERROR - Please determine a clip value prior to loading!
11/21/03 08:16:03: ERROR - Map_Draw_map_values_3D: basemap #1 min/max ribbon values the same OR min greater than max
11/21/03 08:28:34: ERROR - Graphing key values for TRACE_SEQUENCE_NUMBER cancelled.
11/21/03 07:59:28: WARNING - Project Locking disabled by DISABLE_SXLOCK environment variable.
11/21/03 07:50:01: WARNING - Failed to read basemap values from basemap #2.pha.
Note that this file may contain key information to help determine what is wrong!
Last Updated: March 12, 2004