Differences

This shows you the differences between two versions of the page.

--- tutorials:first_steps [2019/07/21 10:38] – dominique
+++ tutorials:first_steps [2019/08/03 22:08] (current) – [Data input and output] seisunix
@@ Line 7: / Line 7: @@
 <WRAP box 800px round center centeralign>
-''segyread tape=test.segy > test.su''
+''segyread tape=test.segy verbose=1 | segyclean > test.su''
 </WRAP>
 Other tools are available to read SEG-2 and some GPR files.
+<WRAP download>
+You can download a SEGY test file [[https://nextcloud.seismic-unix.org/index.php/s/Bc7RgbwiGdCBZ8A|here]]
+</WRAP>
 ===== Data input and output =====
@@ Line 19: / Line 23: @@
 For example:
 <WRAP box 800px round center centeralign>
-''sufilter f=10,20,150,200 <data_to_be_filtered.su >filtered_data.su''
+''sufilter f=10,20,150,200 amps=0,1,1,0 <data_to_be_filtered.su >bandpass_data.su''
 </WRAP>
-will apply a band-pass filter to a SU data file and store the result in an other data file.
+will apply a band-pass filter to a SU data file and store the result in the file bandpass_data.su ,
+<WRAP box 800px round center centeralign>
+''sufilter f=10,20,150,200 amps=1,1,0,0 <data_to_be_filtered.su >low_pass_data.su''
+</WRAP>
+will apply a low pass filter, and
+<WRAP box 800px round center centeralign>
+''sufilter f=10,20,150,200 amps=0,0,1,1 <data_to_be_filtered.su >high_pass_data.su''
+</WRAP>
 As other UNIX tools, SU tools can be linked with the pipe mechanism.
@@ Line 32: / Line 46: @@
 </WRAP>
-''suwind'' reads the file other_data.su and its stdout is linked to the stdin of ''sufilter'' whose stdout is redirected into the file new_su_file.su.
+''suwind'' reads the file other_data.su, keeps only the first 10 traces and its stdout is linked to the stdin of ''sufilter'' whose stdout is redirected into the file new_su_file.su.The default filter is a trapezoidal bandpass filter.
 <WRAP info>
 if you are running SU on a multicore/multiprocessor computer with shared memory, the tasks will be distributed by the operating system to different cores/processors.
 </WRAP>
 ===== Structure of a SU command =====
@@ Line 54: / Line 67: @@
 ==== Screen display : ====
+=== Variable area bitmap ===
 <WRAP box 800px round center centeralign>
@@ Line 63: / Line 77: @@
 Both SU tools (''suplane'' and ''suxwigb'') are used with their default parameters. ''suplane'' is used to generate some simple seismic traces and ''suxwigb'' is used to display them on screen.\\ By default, ''suxwigb'' represents the seismic signal as the combination of a wiggle trace and variable area.\\ This simple sequence is often used to quickly test test a new SU installation. If you use ''suxwigb'' with too many traces with respect to the picture size and screen resolution (i.e. the number of pixels available to draw a trace), you will get a black box.
+=== Variable density ===
 <WRAP box 800px round center centeralign>
  suplane | suximage
@@ Line 73: / Line 88: @@
 ==== Printing ====
-SU ready to print files are coded in the PostScript language. Actually, they are encapsulated postscript files that can be imported in any decent text processing or drawing software. They can also be easily converted to PDF format for better portability.
+SU ready-to-print files are coded in the PostScript language. Actually, they are [[wp>https://en.wikipedia.org/wiki/Encapsulated_PostScript|encapsulated]] PostScript files that can be imported in any decent text processing or drawing software. They can also be easily converted to [[wp>https://en.wikipedia.org/wiki/PDF|PDF format]] for better portability.
 === Variable area bitmap ===
@@ Line 118: / Line 133: @@
 You can also subscribe to the [[ https://mailman.seismic-unix.org/listinfo/seisunix | SU mailing list ]] to get in touch with other SU users around the world.
 </WRAP>
+ --- //[[dominique.rousset@univ-pau.fr|Dominique ROUSSET]] 2019/07/23 11:50//
+{{gravatar>dominique?l}}