= show_info = The show_info command can be used to get information about NetDRMS data. The syntax is involved, the main point of this page is to give some examples. The command does have help, available with the -h option : {{{ show_info -h Usage: show_info [-ahjklpqr] ds= {n=0} {key=} {seg=} sunum= - use instead of ds= argument when SUNUM is known. summary information modes are: -c: count records in query -h: help - show this message then exit -j: list all series, keyword, segment, and link items in jsd file format, then exit -l: list all keywords with description, then exit -s: stats - show some statistics for how many records, etc. per-record information modes are: -a: show information for all keywords -A: show information for all segments -b: disable prime-key logic when opening records -d: Show dimensions of segment files with selected segs -i: query- show the record query that matches the current record -I: print session information for record creation, host, sessionid, runtime, jsoc_version, and logdir -K: show information for all links -o: online - tell the online state -O: disable the code that sets a database query time-out of 10 minutes -p: list the record's storage_unit path (retrieve if necessary) -P: list the record's storage_unit path (no retrieve) -r: recnum - show record number as first keyword -R: retention - show the online expire date -S: sunum - show sunum number as first keyword (but after recnum) -T: Tapename - show archive tapename and file number -v: verbose - print extra, useful information -x: archive - show archive status for the record's storage unit -z: size - show size of storage unit containing record's segments output appearance control flags are: -k: list keyword names and values, one per line -t: list keyword types and print formats as 2nd and 3rd lines in table mode -v: print extra, helpful information -q: quiet - skip header of chosen keywords ds= as {[record specifier]} - required n=0 number of records in query to show, +n from start or -n from end key=, for all use -a flag seg=, for all use -A flag The -p or -P flag will show the record directory by itself or as part of the full path to the segment file if seg= is specified. Note that the -p flag will cause the data to be staged if offline. }}} To show the temporal range covered by a series : {{{ show_info -s aia.lev1 }}} Print 10 minutes worth of data : {{{ show_info key=T_REC_INDEX,T_OBS,WAVELNTH ds="aia.lev1[2013-02-14T23:59:59Z/10m][?WAVELNTH=171?]" }}} or, without wavelength : {{{ show_info key=T_REC_INDEX,T_OBS,WAVELNTH ds="aia.lev1[2013-02-14T23:59:59Z/10m]" }}} For two days rather than 10 minutes : {{{ show_info key=T_REC_INDEX,T_OBS,WAVELNTH ds="aia.lev1[2013-02-14T23:59:59Z/2d]" }}} Having ascertained the record numbers, the information from show_info might be useful in a drms_export_cgi test script like so : {{{ drms_export_cgi 'rsquery=aia.lev1[? wavelnth = 171 and T_REC_index between 1108339235 and 1108339823 ?]{image_lev1}' reqid=SDAC_SDO3_160765 ackfile=/tmp/ACKFILESDAC_SDO3_160765 expversion=0.5 method=url_cgi protocol=FITS path=jsoc 'ffmt={seriesname}.{wavelnth}A_{date__obs}.{segment}' tarfile=aia__lev1_4k_171A_1108339235-1108339823 > drms_export_cgi_tar.hfits 2> drms_export_cgi_tar.err }}} It's worth noting that sometimes it's better to use the jsoc_fetch CGI to get information than it is to use show_info, the syntax is something like this : {{{ http://jsoc.stanford.edu/cgi-bin/ajax/jsoc_fetch_VSO?op=exp_su&method=url_quick&format=json&formatvar=dataobj&protocol=as-is&requestid=NOASYNCREQUEST&sunum=627527822,627527820,627527818,627527817 }}}