Flux Standard Screening and Linearity Check

Principal: Chad Engelbracht
Deputy: Dean Hines, Dave Frayer, Susan Stolovy
Data Iguanas: Kate Su, Eiichi Egami
Priority: Necessary
Downlink Priority: Normal
Analysis Time: 7d
Last Updated:


Objective

The purpose of this task is to begin screening the MIPS flux standards to identify those that are unsuitable for calibration due to dust disks, background sources, binarity, etc., and to improve the flux linearity measurement on the three arrays.


Description

This task is designed to perform photometry observations of a large number of stars to begin screening the list of potential MIPS flux calibrators for suitable standards. The second goal is to measure the flux linearity of the data that has passed through the pipeline.

The data will be taken using the same observation design used for our regular standard-star observations, i.e., 2 cycles of small-field photometry at 24µm, 3 cycles of small-field photometry at 70µm, and 2 cycles of superresolution observations at 160µm. This will produce 28, 30, and 12 independent images of each star at 24, 70, and 160µm, respectively. The nominal 1-sigma sensitivity achieved when these images are combined is 0.1, 0.6, and 3 mJy at 24, 70, and 160µm, respectively. The DCE time used will be 3s unless the stars are faint enough to be below 1/4 the nominal 10s saturation level, in which case 10s DCEs will be used. Those thresholds are 127, 120, and 333 mJy at 24, 70, and 160µm, respectively. The nominal 1-sigma sensitivities achieved in the 10s observations are 0.05, 0.4, and 2 mJy at 24, 70, and 160µm, respectively.

To select stars, I used the select-stars.pl script to select stars from the mips calibrator star list within a reasonable flux range (~3-sigma per DCE up to 1s saturation, which is 5.6, 5.3, and 8 Jy at 24, 70, and 160µm, respectively). I eliminated those at high background, those that are already being observed in other calibration tasks, and those that duplicate fluxes already measured.

The candidate stars are listed below. I have generated the AORs using the generate-aors.pl script. I have deliberately kept the AORs separate, even when the same star is observed in multiple bands. This was done so that this task could be scheduled such that all the 160µm AORs are done first, followed by 70, then 24. With this scheduling, an anneal can be done before executing this task and then another will not be required during the task (i.e., it will not be necessary to interrupt this task with an anneal).

Candidate Stars

ID type RA DEC Band flux bkgd. visibility


(2000) (2000) (µm) (mJy) (MJy/sr)
HD174123 G5? 18:43:10.3 69:20:59 24 14 15.4 2003/08/24-2006/05/01
HD165459 A2 18:02:30.7 58:37:38 24 16 15.4 2003/08/24-2006/05/01
HD172066 G5? 18:32:30.2 68:36:51 24 17 15.4 2003/08/24-2006/05/01
HD176841 G5? 18:56:49.3 68:17:33 24 20 15.4 2003/08/24-2006/05/01
HD163466 A2V 17:52:25.4 60:23:47 24 21 15.3 2003/08/24-2006/05/01
HD158485 A4V 17:26:04.8 58:39:07 24 25 15.4 2003/08/24-2006/05/01
HD191854 G5 20:10:13.3 43:56:44 24 33 18.7 2003/08/24-2003/12/12
HD172728 A0V 18:37:33.5 62:31:36 24 35 15.3 2003/08/24-2006/05/01
HD158460 A2V 17:25:41.4 60:02:54 24 46 15.4 2003/08/24-2006/05/01
HD166780 K4.5III 18:08:38.8 57:58:47 24 207 15.5 2003/08/24-2006/05/01
HD154391 K2III 17:01:16.9 60:38:56 24 217 15.4 2003/08/24-2006/05/01
HD159048 K0III 17:23:34.5 76:03:18 24 229 15.4 2003/08/24-2004/06/13
HD173511 K5III 18:41:40.6 61:32:47 24 236 15.4 2003/08/24-2006/05/01
HD173976 K5III 18:44:30.1 60:20:56 24 297 15.4 2003/08/24-2006/05/01
HD152222 K2III 16:47:04.6 67:16:01 24 330 15.3 2003/08/24-2006/05/01
HD170693 K1.5III 18:25:59.1 65:33:49 24 1299 15.5 2003/08/24-2006/05/01
HD087901 B7 10:08:22.3 11:58:02 24 1559 52.4 2003/11/14-2003/12/25
HD138265 K5III 15:27:51.4 60:40:13 24 1849 15.8 2003/11/16-2004/08/01
HD216131 G8II 22:50:00.2 24:36:06 24 2075 26.0 2003/11/14-2004/01/01
HD217382 K4III 22:54:25.0 84:20:46 24 2199 17.1 2003/08/24-2004/04/04
HD189276 K5Iab 19:55:55.4 58:50:45 24 2371 15.7 2003/08/24-2004/01/21
HD163588 K2III 17:53:31.7 56:52:22 24 2930 15.5 2003/08/24-2006/05/01
HD180711 G9III 19:12:33.3 67:39:42 24 3724 15.3 2003/08/24-2006/05/01
HD082308 K5III 09:31:43.2 22:58:05 24 4465 48.5 2003/11/02-2003/12/13
HD096833 K1III 11:09:39.8 44:29:55 24 5278 24.9 2003/11/10-2003/12/31
HD158460 A2V 17:25:41.4 60:02:54 70 10 4.4 2003/08/24-2006/05/01
HD166780 K4.5III 18:08:38.8 57:58:47 70 20 5.0 2003/08/24-2006/05/01
HD173511 K5III 18:41:40.6 61:32:47 70 30 4.8 2003/08/24-2006/05/01
HD152222 K2III 16:47:04.6 67:16:01 70 40 4.5 2003/08/24-2006/05/01
HD170693 K1.5III 18:25:59.1 65:33:49 70 150 4.8 2003/08/24-2006/05/01
HD087901 B7 10:08:22.3 11:58:02 70 180 15.9 2003/11/14-2003/12/25
HD138265 K5III 15:27:51.4 60:40:13 70 220 4.3 2003/11/16-2004/08/01
HD216131 G8II 22:50:00.2 24:36:06 70 240 9.0 2003/11/14-2004/01/01
HD180711 G9III 19:12:33.3 67:39:42 70 430 4.8 2003/08/24-2006/05/01
HD082308 K5III 09:31:43.2 22:58:05 70 530 14.7 2003/11/02-2003/12/13
HD096833 K1III 11:09:39.8 44:29:55 70 620 7.0 2003/11/10-2003/12/31
HD213310 M0II+ 22:29:31.8 47:42:25 70 910 7.7 2003/11/08-2004/01/16
HD089484 K1IIIb 10:19:58.4 19:50:29 70 1730 14.3 2003/11/14-2003/12/25
HD089758 M0III 10:22:19.7 41:29:58 70 2110 8.0 2003/11/03-2003/12/21
HD131873 K4III 14:50:42.3 74:09:20 70 3260 4.6 2003/09/27-2004/06/10
HD170693 K1.5III 18:25:59.1 65:33:49 160 30 7.4 2003/08/24-2006/05/01
HD138265 K5III 15:27:51.4 60:40:13 160 40 3.6 2003/11/16-2004/08/01
HD189276 K5Iab 19:55:55.4 58:50:45 160 50 15.6 2003/08/24-2004/01/21
HD163588 K2III 17:53:31.7 56:52:22 160 60 7.2 2003/08/24-2006/05/01
HD180711 G9III 19:12:33.3 67:39:42 160 80 7.4 2003/08/24-2006/05/01
HD082308 K5III 09:31:43.2 22:58:05 160 100 7.8 2003/11/02-2003/12/13
HD096833 K1III 11:09:39.8 44:29:55 160 120 4.0 2003/11/10-2003/12/31
HD213310 M0II+ 22:29:31.8 47:42:25 160 170 21.2 2003/11/08-2004/01/16
HD089484 K1IIIb 10:19:58.4 19:50:29 160 320 6.7 2003/11/14-2003/12/25
HD089758 M0III 10:22:19.7 41:29:58 160 400 4.1 2003/11/03-2003/12/21

Scheduling Notes


Data Collected

As described above, this task will collect 12-30 images of each star in each band. In total, this is a lot of data - over 6000 DCEs each time the task is run. The data will all be collected in photometry mode and the reduction will be identical for each star.

As currently defined, the task requires 6.4 hours for the northern-target version to be run in campaign W. There is a smaller number of stars in the south that have not already been observed in other IOC tasks, so we could contemplate a smaller version of this task to be run in another campaign to get the southern stars, should the time be available.


Data Reformatting Requirements

Array Data Desired:

All Arrays

Data Reformatting Option:

Special Instructions:

Task Dependencies


Calibration Dependencies


Output and Deliverable Products


Data Analysis

The data will be reduced as for the other calibration standards, by running them through the DAT and extracting fluxes with IDP3 (see the routine calibration task cookbooks, MIPS-920, 922, and 924, for more detail). The measured DN/s should then be plotted against the predicted flux (in Jy, for example). Ideally, all the stars would fall on a straight line, indicating they were good standards and that the array was perfectly linear. The expected outcome is that some of the stars will not fall on the curve defined by most of the stars, due to circumstellar dust, binarity, background sources, etc. Those stars should be flagged as poor calibrators and ejected from our calibration list. In addition, the Ge:Ga array data are not expected to fall on a straight line, but rather along a curve that defines the flux nonlinearity not corrected by the pipeline. This curve will be used in conjunction with the data obtained in mips-600 to define a linearity correction for the Ge:Ga arrays.


Software Requirements


Actions Following Analysis


Failure Modes and Responses

If this task fails outright to collect any data, it should obviously be repeated. If it collects data, but there are not enough suitable stars to define the linearity curve, the task should be repeated with new stars.


Additional Notes

This task should be repeated peroidically throughout the first 6 months of the mission, using different stars as they become available. The ultimate goal is to measure all our potential calibration standards and screen out the ones that are not good standards.