| | 1 | == MOPS Detectability Query == |
| | 2 | |
| | 3 | MOPS will query the IPP regarding the detectability of hypothetical |
| | 4 | elongated detections specified using ($RA_0$, $Dec_0$, $Time_0$, |
| | 5 | $RA_1$, $Dec_1$, $Time_1$) tuples by submitting all information |
| | 6 | required to construct a FPA PSF at the time of the detections. It is |
| | 7 | the responsibility of MOPS to generate and manage unique query IDs. |
| | 8 | |
| | 9 | A query should specify the stage of the processing pipeline to measure |
| | 10 | the detections. This is specified by the STAGE parameter, which has |
| | 11 | allowed values of chip,warp,stack, and diff. |
| | 12 | |
| | 13 | All MOPS detectability queries will occur with respect to an |
| | 14 | already-ingested FPA transient detection list. The query being asked |
| | 15 | by MOPS is essentially whether a particular trail in an acquired FPA |
| | 16 | image was masked for any reason and to what degree. Thus the |
| | 17 | originating IPP FPA\_ID is required. A query may request data from a |
| | 18 | different processing stage than given by the transient detection list. |
| | 19 | Because of this, IPP stage id values may be used in place of the |
| | 20 | FPA\_ID. |
| | 21 | |
| | 22 | MOPS will simulate elongated ('trailed') PSFs, relevant for |
| | 23 | fast-moving objects. Since some or all of a trail may be masked, MOPS |
| | 24 | will for all detections provide starting and ending RA and Dec. For |
| | 25 | most detections these two positions will be nearly coincident, |
| | 26 | appearing as a circular point-source PSF, but for fast-moving objects |
| | 27 | these positions may differ by many pixels in the FPA. The |
| | 28 | detectability server currently only supports point source detections, |
| | 29 | using the starting RA and Dec provided by the query. |
| | 30 | |
| | 31 | In addition to the required BINTABLE extension header keywords |
| | 32 | described above, the FITS header for the detectability query shall |
| | 33 | include the following required keywords shown in table |
| | 34 | \ref{detquery-keywords}. The subsequent FITS table, with EXTNAME of |
| | 35 | {{{MOPS_DETECTABILITY_QUERY}}}, shall include columns whose |
| | 36 | definitions are listed in table \ref{detquery-table}. |
| | 37 | |
| | 38 | === MOPS-IPP Detectability Query Keywords\label{detquery-keywords} === |
| | 39 | ||''' Column''' || '''Precision'''|| ''' Description''' || |
| | 40 | ||QUERY_ID || char(20) || MOPS query ID for this batch query || |
| | 41 | ||FPA_ID || char(20) || original FPA_ID used at ingest || |
| | 42 | ||MJD-OBS || F64 || starting time of the exposure, MJD || |
| | 43 | ||FILTER || char(3) || effective filter used for the exposure as a string, allowed values of g, r, i, z, y, B, V, w || |
| | 44 | ||OBSCODE || char(3) || site identifier (MPC observatory code) || |
| | 45 | ||STAGE || char(20) || stage name to perform query on, allowed values of 'chip', 'warp', 'stack', and 'diff'|| |
| | 46 | |
| | 47 | === MOPS-IPP Detectability Query Table Columns\label{detquery-table} === |
| | 48 | ||'''Column''' || '''Precision''' ||'''Description'''|| |
| | 49 | ||ROWNUM || char(20) || identifier for this row in the table || |
| | 50 | ||RA1_DEG || F64 || coordinate at the start of exposure, in degrees || |
| | 51 | ||DEC1_DEG || F64 || coordinate at the start of exposure, in degrees || |
| | 52 | ||RA2_DEG || F64 || coordinate at the end of exposure, in degrees || |
| | 53 | ||DEC2_DEG || F64 || coordinate at the end of exposure, in degrees || |
| | 54 | ||MAG || F64 || apparent magnitude || |
| | 55 | |
| | 56 | |
| | 57 | == IPP Detectability Response == |
| | 58 | |
| | 59 | IPP will return a table listing the submitted query detections and a |
| | 60 | set of values $(N, f, flux)$ indicating the number of pixels relevant |
| | 61 | to the detection's PSF, the fraction of these pixels detectable by |
| | 62 | IPP, and the flux measured for the detection. The table will also |
| | 63 | note if an error occurred while processing the request specification |
| | 64 | by setting the ERROR_CODE for the detection to a non-zero value. The |
| | 65 | values for ERROR_CODE are listed in table \ref{pss-errorcodes}. |
| | 66 | |
| | 67 | For infrequent cases where a trail may completely traverse a masked |
| | 68 | area (due to chip gap, streak removal, or similar), the response may |
| | 69 | be erroneous or incomplete. This error and its effects will be |
| | 70 | studied during PS-1 operations. |
| | 71 | |
| | 72 | In addition to the required BINTABLE extension header keywords |
| | 73 | described above, the FITS header for the detectability response shall include |
| | 74 | the following required keywords shown in table \ref{detresponse-keywords}. |
| | 75 | The subsequent FITS table, with EXTNAME of \code{MOPS_DETECTABILITY_RESPONSE}, shall include |
| | 76 | columns whose definitions are listed in table \ref{detresponse-table}. |
| | 77 | |
| | 78 | === MOPS-IPP Detectability Response Keywords\label{detresponse-keywords} === |
| | 79 | ||'''Column''' || '''Precision''' ||'''Description'''|| |
| | 80 | ||QUERY_ID || char(20) || originating MOPS query ID || |
| | 81 | ||FPA_ID || char(20) || IPP FPA ID used in detectability request || |
| | 82 | |
| | 83 | |
| | 84 | === MOPS-IPP Detectability Response Table Columns\label{detresponse-table} === |
| | 85 | ||'''Column''' || '''Precision''' || '''Description''' || |
| | 86 | ||ROWNUM || char(20) || matching rownum from original request || |
| | 87 | ||ERROR_CODE || U32 || Error code (see text) || |
| | 88 | ||DETECT_N || U32 || number of pixels used in the hypothetical PSF for the query detection || |
| | 89 | ||DETECT_F || F64 || detectability, indicating the fraction of PSF pixels detectable by IPP || |
| | 90 | ||TARGET_FLUX || F64 || flux measured for the PSF fit for the query detection || |
| | 91 | |
| | 92 | === Postage Stamp Error Codes \label{pss-errorcodes} === |
| | 93 | ||''' Name''' || '''ERROR_CODE value''' || '''Description''' || |
| | 94 | ||PSTAMP_SUCCESS || 0 || No errors || |
| | 95 | ||PSTAMP_SYSTEM_ERROR || 10 || Some unspecified system error occurred during processing || |
| | 96 | ||PSTAMP_NOT_IMPLEMENTED || 11 || Feature not yet implemented || |
| | 97 | ||PSTAMP_UNKNOWN_ERROR || 12 || Unknown error || |
| | 98 | ||PSTAMP_DUP_REQUEST|| 20 || Request name is a duplicate || |
| | 99 | ||PSTAMP_INVALID_REQUEST || 21 || Error in request specification. See parse_error.txt || |
| | 100 | ||PSTAMP_UNKNOWN_PRODUCT || 22 || Unknown product in request specification || |
| | 101 | ||PSTAMP_NO_IMAGE_MATCH || 23 || No images matched the request || |
| | 102 | ||PSTAMP_NOT_DESTREAKED || 24 || Image matched, but not yet destreaked || |
| | 103 | ||PSTAMP_NOT_AVAILABLE|| 25||Image not available (temporary) || |
| | 104 | ||PSTAMP_GONE || 26 || Image is no longer available || |
| | 105 | ||PSTAMP_NO_JOBS_QUEUED || 27 || Request specification yielded no jobs. See parse_error.txt || |
| | 106 | ||PSTAMP_NO_OVERLAP || 28 || Center not contained in any image of interest || |
| | 107 | |
| | 108 | |