SETI@Home (classic) - Revision history

Dan Tobias: /* Sample data */

2020-02-11T14:16:32Z

‎Sample data

2013-11-05T01:28:14Z

2013-04-15T04:28:19Z

2013-04-14T15:57:49Z

2013-04-14T15:57:02Z

‎Classic data files

2013-04-14T15:51:40Z

‎Software

2013-04-14T15:13:26Z

‎Other links

2013-04-14T15:00:57Z

‎Software

2013-04-14T14:58:33Z

‎Software

2013-04-14T13:55:20Z

‎Classic data files

@@ Line 37: / Line 37: @@
 == Sample data ==
-* [http://www.dan.info/sampledata/work_unit.sah Work unit]
+* [https://www.dan.info/sampledata/work_unit.sah Work unit]
-* [http://www.dan.info/sampledata/outfile.sah Result file]
+* [https://www.dan.info/sampledata/outfile.sah Result file]
 == Other links ==

@@ Line 16: / Line 16: @@
 Most of the data files have the '''.sah''' extension. They are generally in UNIX-style [[ASCII]] text format, with lines broken with linefeed characters. Much of the data is in the form of name/value pairs each on a separate line with the equal sign separating the name from the value.
-Work units are in files called '''work_unit.sah''', starting with a line ''type=work unit''. Encoded binary data follows the header fields (which end with ''end_seti_header''). The binary data is in the [[PSRFITS]] format, a variety of the [[Flexible Image Transport System]] (FITS). It is encoded as ASCII characters (there doesn't seem to be any online documentation specifying the specific encoding scheme used; it is perhaps something like [[Base64]], [[UUEncoding]], or [[BinHex]]).
+Work units are in files called '''work_unit.sah''', starting with a line ''type=work unit''. Encoded binary data follows the header fields (which end with ''end_seti_header''). The binary data is in the [[PSRFITS]] format, a variety of the [[Flexible Image Transport System]] (FITS). It is encoded as ASCII characters (there doesn't seem to be any online documentation specifying the specific encoding scheme used; it is perhaps something like [[Base64]], [[Uuencoding]], or [[BinHex]]).
 Results are stored in a file '''outfile.sah''', with data like:

@@ Line 3: / Line 3: @@
 |subcat=Distributed computing projects
 |extensions={{ext|sah}}
 }}

@@ Line 15: / Line 15: @@
 Most of the data files have the '''.sah''' extension. They are generally in UNIX-style [[ASCII]] text format, with lines broken with linefeed characters. Much of the data is in the form of name/value pairs each on a separate line with the equal sign separating the name from the value.
-Work units are in files called '''work_unit.sah''', starting with a line ''type=work unit''. Encoded binary data follows the header fields (which end with ''end_seti_header''). The binary data is in the [[PSRFITS]] format, a variety of the [[Flexible Image Transport System]] (FITS). It is encoded as ASCII characters (there doesn't seem to be any online documentation specifying the specific encoding scheme used; it is perhaps something like [[BASE64]], [[UUEncode]], or [[BINHEX]]).
+Work units are in files called '''work_unit.sah''', starting with a line ''type=work unit''. Encoded binary data follows the header fields (which end with ''end_seti_header''). The binary data is in the [[PSRFITS]] format, a variety of the [[Flexible Image Transport System]] (FITS). It is encoded as ASCII characters (there doesn't seem to be any online documentation specifying the specific encoding scheme used; it is perhaps something like [[Base64]], [[UUEncoding]], or [[BinHex]]).
 Results are stored in a file '''outfile.sah''', with data like:

@@ Line 15: / Line 15: @@
 Most of the data files have the '''.sah''' extension. They are generally in UNIX-style [[ASCII]] text format, with lines broken with linefeed characters. Much of the data is in the form of name/value pairs each on a separate line with the equal sign separating the name from the value.
-Work units are in files called '''work_unit.sah''', starting with a line ''type=work unit''. Encoded binary data follows the header fields (which end with ''end_seti_header''). The binary data is in the [[PSRFITS]] format, a variety of the [[Flexible Image Transport System]] (FITS).
+Work units are in files called '''work_unit.sah''', starting with a line ''type=work unit''. Encoded binary data follows the header fields (which end with ''end_seti_header''). The binary data is in the [[PSRFITS]] format, a variety of the [[Flexible Image Transport System]] (FITS). It is encoded as ASCII characters (there doesn't seem to be any online documentation specifying the specific encoding scheme used; it is perhaps something like [[BASE64]], [[UUEncode]], or [[BINHEX]]).
 Results are stored in a file '''outfile.sah''', with data like:

@@ Line 33: / Line 33: @@
 * [http://swap.poupe.net/sk/ SETI@home Keeper]
 * [http://www.mariovaldez.net/software/phpsetimon/ PHP SETI@home web monitor]
 == Sample data ==

← Older revision		Revision as of 15:13, 14 April 2013
Line 43:		Line 43:
	* [http://setiathome.berkeley.edu/transition.php Transition to BOINC]		* [http://setiathome.berkeley.edu/transition.php Transition to BOINC]
	* [http://setiathome.berkeley.edu/forum_thread.php?id=65274 Discussion of analyzing data]		* [http://setiathome.berkeley.edu/forum_thread.php?id=65274 Discussion of analyzing data]
		+	* [http://www.pisa.org.hk/event/bo.pdf Presentation describing a buffer-overflow exploit in SETI@Home data]

@@ Line 31: / Line 31: @@
 == Software ==
 * [http://code.google.com/p/seti-psrfits-viewer/ Viewer for SETI PSRFITS files]
 == Sample data ==