SOC_Data_Writer.html -- Provides a Web Interface to the CRaTER SOC L2 Data Repository



User selects among the options presented for start & stop times, data fields to be retrieved, and output file format. Data is returned in a file ready to be downloaded; in process diagnostics from the underlying CGI script are provided.

If no fields names are selected, all are assumed. But you must be consistent. Selecting field values in one column and then selecting the "Submit" button for a different column will result in a verbose error message.


The HTML code sets up the parameters for a call to socreport.cgi, which in turn translates those parameters into a form sutable for a call to SData. SData is run with a Verbose flag invoked, and the resulting diagnostics are returned to the user.

The data file containing the results from the call to the SOC Level 2 Data Repository is unique to the machine submitting the CGI request. Separate (unique) files are generated for Primary Science, Secondary Science, and Housekeeping; consistent with the structure of the Level 2 Data Repository. The data files so generated are temporary: first, the files are overwritten by subsequent CGI requests from the same requesting machine; and second, the web server will (probably) purge the data directory of old files every few days.


The limitations of SData will apply here, also, the most important of which is that SData and, presumably, socreport.cgi need to be running under a Perl version of at least 5.8.0 to have an SQL interface module available. But this doesn't have to be the same machine as the Web server running this program!

It is a restriction of SData that the L2 data must be retrieved separately on a per-AppId basis.


High Level programs


Low Level programs



Bob Goeke

RCS Information

$Id: SOC_Data_Writer.html,v 1.7 2009/07/22 12:34:14 goeke Exp goeke $

Copyright: Massachusetts Institute of Technology 2009