Guide to RSF file format - Revision history

Fomels: typos

2024-11-20T19:58:19Z

typos

Sergey: /* Reading and writing CSV files */

2021-03-08T23:09:32Z

Reading and writing CSV files

@@ Line 481: / Line 481: @@
 *******************************************************************************
 </pre>
 ==Other documentation==

Sergey: /* Reading and writing CSV files */

2021-03-08T23:06:13Z

Reading and writing CSV files

@@ Line 457: / Line 457: @@
 .0,1.5,3.0
 .8,9.1,7.3
 </pre>

Sfomel: /* Reading and writing CSV files */

2018-11-17T00:01:55Z

Reading and writing CSV files

← Older revision		Revision as of 00:01, 17 November 2018
Line 453:		Line 453:
	<pre>		<pre>
	bash$ sfdd form=ascii --out=file.csv \		bash$ sfdd form=ascii --out=file.csv \
	line=3 strip=1 format="%3.1f," ~~number=n~~ < file.rsf >/dev/null		line=3 strip=1 format="%3.1f," < file.rsf >/dev/null
	bash$ cat file.csv		bash$ cat file.csv
	1.0,1.5,3.0		1.0,1.5,3.0

Sfomel: /* Reading and writing CSV files */

2018-11-17T00:00:52Z

Reading and writing CSV files

← Older revision		Revision as of 00:00, 17 November 2018
Line 453:		Line 453:
	<pre>		<pre>
	bash$ sfdd form=ascii --out=file.csv \		bash$ sfdd form=ascii --out=file.csv \
	line=3 strip=1 format="		line=3 strip=1 format="%3.1f," number=n < file.rsf >/dev/null
	bash$ cat file.csv		bash$ cat file.csv
	1.0,1.5,3.0		1.0,1.5,3.0

Sfomel: /* Reading and writing ASCII files */

2018-11-16T23:59:03Z

Reading and writing ASCII files

@@ Line 426: / Line 426: @@
 .0 1.5 3.0
 .8 9.1 7.3
 </pre>

Sfomel at 18:14, 28 January 2018

2018-01-28T18:14:51Z

← Older revision		Revision as of 18:14, 28 January 2018
Line 405:		Line 405:
	6 elements 24 bytes		6 elements 24 bytes
	</pre>		</pre>
	~~Convert~~ from RSF to ASCII is equally simple:		Converting from RSF to ASCII is equally simple:
	<pre>		<pre>
	bash$ sfdd form=ascii --out=file.asc < file.rsf > /dev/null		bash$ sfdd form=ascii --out=file.asc < file.rsf > /dev/null

Sfomel at 18:13, 28 January 2018

2018-01-28T18:13:13Z

← Older revision		Revision as of 18:13, 28 January 2018
Line 81:		Line 81:
	</pre>		</pre>
	In this case, the <tt>cat</tt> utility simply copies the contents of the		In this case, the <tt>cat</tt> utility simply copies the contents of the
	previous file, and the <tt>echo</tt> utility appends new line "n1=50		previous file, and the <tt>echo</tt> utility appends new line "<tt>n1=50
	n2=20". A new value of the <tt>n1</tt> parameter overwrites the old value		n2=20</tt>". A new value of the <tt>n1</tt> parameter overwrites the old value
	of <tt>n1=1000</tt>, and we achieve the same result as before.		of <tt>n1=1000</tt>, and we achieve the same result as before.
	Of course, one could also edit the file by hand with one of the general		Of course, one could also edit the file by hand with one of the general
Line 136:		Line 136:

	<pre>		<pre>
	bash$ sfspike n1=10 out=test1 > spike.rsf		bash$ sfspike n1=10 --out=test1 > spike.rsf
	bash$ grep in spike.rsf		bash$ grep in spike.rsf
	in="test1"		in="test1"
Line 189:		Line 189:
	character, integer, floating point, or complex. By default, single precision		character, integer, floating point, or complex. By default, single precision
	is used for numbers (<tt>int</tt> and <tt>float</tt> data types in the C		is used for numbers (<tt>int</tt> and <tt>float</tt> data types in the C
	programming language). The number of bytes required for represent these		programming language) but double precision and other
			integer types (<tt>short</tt> and <tt>long</tt>) are also
			supported. The number of bytes required for represent these
	numbers may depend on the platform.		numbers may depend on the platform.
	===Form===		===Form===
Line 255:		Line 257:
	<tt>d1</tt>, <tt>d2</tt>, <tt>d3</tt>, etc. The axes origins are given		<tt>d1</tt>, <tt>d2</tt>, <tt>d3</tt>, etc. The axes origins are given
	by parameters <tt>o1</tt>, <tt>o2</tt>, <tt>o3</tt>, etc. Optionally,		by parameters <tt>o1</tt>, <tt>o2</tt>, <tt>o3</tt>, etc. Optionally,
	you can also supply the axis label strings <tt>label1</tt>,		you can also supply the axis label strings: <tt>label1</tt>,
	<tt>label2</tt>, <tt>label3</tt>, etc., and axis units strings		<tt>label2</tt>, <tt>label3</tt>, etc., and axis units strings:
	<tt>unit1</tt>, <tt>unit2</tt>, <tt>unit3</tt>, etc.		<tt>unit1</tt>, <tt>unit2</tt>, <tt>unit3</tt>, etc.
	==Compatibility with other file formats==		==Compatibility with other file formats==
	It is possible to exchange RSF-formatted data with other popular data formats.		It is possible to exchange RSF-formatted data with several other popular data formats.
	===Compatibility with SEPlib===		===Compatibility with SEPlib===
	RSF is mostly compatible with its predecessor, the SEPlib file format.		RSF is mostly compatible with its predecessor, the SEPlib file format.
Line 298:		Line 300:
	<pre>		<pre>
	bash$ sfsegyread < plane.segy tfile=tfile.rsf \		bash$ sfsegyread < plane.segy tfile=tfile.rsf \
	hfile=~~hfile~~ bfile=~~bfile~~ > plane.rsf		hfile=file.asc bfile=file.bin > plane.rsf
	</pre>		</pre>
	The endian flag is needed if the SU file originated from a little-endian		The endian flag is needed if the SU file originated from a little-endian
Line 329:		Line 331:
	The contents of trace headers can be quickly examined with the		The contents of trace headers can be quickly examined with the
	<tt>sfheaderattr</tt> program.		<tt>sfheaderattr</tt> program.
	The <tt>~~hfile~~</tt> is the ASCII header file for the whole record.		The <tt>file.asc</tt> is the ASCII header file for the whole record.
	<pre>		<pre>
	bash$ head -c 242 ~~hfile~~		bash$ head -c 242 file.asc
	C This tape was made at the		C This tape was made at the
	C		C
	C Center for Wave Phenomena		C Center for Wave Phenomena
	</pre>		</pre>
	The <tt>~~bfile~~</tt> is the binary header file.		The <tt>file.bin</tt> is the binary header file.

	To convert files back from RSF to SEG-Y or SU, use the <tt>sfsegywrite</tt>		To convert files back from RSF to SEG-Y or SU, use the <tt>sfsegywrite</tt>
	program and reverse the input and output:		program and reverse the input and output:
	<pre>		<pre>
	bash$ sfsuwrite > plane.su ~~su=y~~ tfile=tfile.rsf endian=0 < plane.rsf		bash$ sfsuwrite > plane.su tfile=tfile.rsf endian=0 < plane.rsf
	</pre>		</pre>
	or		or
	<pre>		<pre>
	bash$ sfsegywrite > plane.segy tfile=tfile.rsf \		bash$ sfsegywrite > plane.segy tfile=tfile.rsf \
	hfile=~~hfile~~ bfile=~~bfile~~ < plane.rsf		hfile=file.asc bfile=file.bin < plane.rsf
	</pre>		</pre>

Line 355:		Line 357:
	bash$ sfsegywrite < plane.rsf tfile=tfile.rsf > plane.segy		bash$ sfsegywrite < plane.rsf tfile=tfile.rsf > plane.segy
	</pre>		</pre>

			====Unusual trace header keys====
			Sometimes, SEG-Y files deviate from the standard by creating additional
			trace header keys. If, for example, you find out that the SEG-Y file
			contains an additional trace header key stored in bytes 225-226, you
			can either remap one of the standard two-byte keys
			<pre>
			bash$ sfsegyread < file.segy tfile=tfile.rsf gut=224 > file.rsf
			</pre>
			or create a new key
			<pre>
			bash$ sfsegyread < file.segy tfile=tfile.rsf \
			key1=mykey key1_len=2 mykey=224 > file.rsf
			</pre>
			Any number of additional keys can be created this way.

	===Reading and writing ASCII files===		===Reading and writing ASCII files===
Line 390:		Line 407:
	Convert from RSF to ASCII is equally simple:		Convert from RSF to ASCII is equally simple:
	<pre>		<pre>
	bash$ sfdd form=ascii out=file.asc < file.rsf > /dev/null		bash$ sfdd form=ascii --out=file.asc < file.rsf > /dev/null
	bash$ cat file.asc		bash$ cat file.asc
	1 1.5 3 4.8 9.1 7.3		1 1.5 3 4.8 9.1 7.3
Line 397:		Line 414:
	<tt>sfdd</tt> to control the ASCII formatting:		<tt>sfdd</tt> to control the ASCII formatting:
	<pre>		<pre>
	bash$ sfdd form=ascii out=file.asc \		bash$ sfdd form=ascii --out=file.asc \
	line=3 format="%3.1f " < file.rsf > /dev/null		line=3 format="%3.1f " < file.rsf > /dev/null
	bash$ cat file.asc		bash$ cat file.asc

Sfomel: /* Datapath */

2016-06-07T09:59:50Z

Datapath

← Older revision		Revision as of 09:59, 7 June 2016
Line 120:		Line 120:
	data file directory are as follows:		data file directory are as follows:

	#Check <tt>out=</tt> parameter on the command line. The parameter specifies the output data file location explicitly.		#Check <tt>--out=</tt> parameter on the command line. The parameter specifies the output data file location explicitly.
	#Specify the path and the file name separately.		#Specify the path and the file name separately.
	#*The rules for the path selection are:		#*The rules for the path selection are:

Sfomel at 23:58, 27 July 2015

2015-07-27T23:58:55Z

← Older revision		Revision as of 23:58, 27 July 2015
Line 1:		Line 1:
	<center><font size="-1">''This page was created from the LaTeX source in [~~http~~://~~sourceforge~~.~~net~~/p/~~rsf~~/~~code~~/~~HEAD/tree/trunk~~/book/rsf/rsf/format.tex book/rsf/rsf/format.tex] using [[latex2wiki]]''</font></center>		<center><font size="-1">''This page was created from the LaTeX source in [https://github.com/ahay/src/blob/master/book/rsf/rsf/format.tex book/rsf/rsf/format.tex] using [[latex2wiki]]''</font></center>