Please fill in the following fields and attach this form with your delivery notification. A description of selected fields is given at the end of this page.
Deliveries using separate delivery forms will be considered independent. If it is necessary for any two deliveries to be installed at the same time or at a particular time, please indicate this in field 13. All reference files listed on a single form will be installed at the same time. If you have any further questions, please send an e-mail to cdbs_team_at_stsci.edu (replace _at_ by @)
1-Name of deliverer: (other e-mail addresses) 2-Date of delivery: 3-Instrument: 4-Type of file (bias,pht,etc.): 5-Has HISTORY section in header  been updated to describe in detail why it is being delivered and how the file was created? (yes/no): 6-USEAFTER, PEDIGREE, DESCRIP, and COMMENT have been checked? 6a-Was the DESCRIP keyword updated with a summary of why the file was updated or created? (yes/no) 6b- If the reference files are replacing previous versions, do the new USEAFTER dates exactly match the old ones? 7-CDBS Verification complete? (fitsverify,certify,etc.): 8-Should these files be ingested in the OPUS, DADS and CDBS databases? (if not clearly indicate which ones): 8a-If files are synphot files, should they be delivered to ETC? 9-Files run through CALXXX or SYNPHOT in the IRAF version of STSDAS and the IRAF* version used by the Archive pipeline? (yes/no) List the versions used: 10-Does it replace an old reference file? (yes/no): 10a-If yes, which one? (If the file being replaced is bad, and should not be used with any data, please indicate this here.) 11- What is the level of change of the file? (e.g. compared to old file it could be: SEVERE, MODERATE, TRIVIAL, 1\%, 5\% etc.): 11a-If files are tables, please indicate exactly which rows have changed. Show output of compare_table.pro. 12-Please indicate which modes (e.g. all the STIS, FUVMAMA, E140L modes) are affected by the changes in the file. 13-Description of how the files were "tested" for correctness: 14-Additional Considerations: 15-Reason for delivery: 16-Disk location and name of files:
1-Name of deliverer:
in "(other e-mail addresses)" you should provide all the e-mail address of the people or mailing lists that should be notified of any problem or success of the delivery. However, you can leave this field blank if they are in the Cc: field of the e-mail you will be sending to the INS/CDBS Group with this form.
2-Date of delivery:
The instrument to which the reference files being delivered apply.
4-Type of file:
Give the extension name or whole name of the file(s) being delivered.
5-Has HISTORY section in header  been updated to describe in detail why it is being delivered and how the file was created?:
The history section of the file should have a description of the changes made to the file, in respect to a previously delivered one. If it is a new file, it should have a brief explanation on how the calibration was made to derive the values in the file. You could also refer to any relevant documentation that has this information. The TIR titled "Assessment and Delivery of Reference Files", current version TIR-CDBS-2009-01A, describes what should be listed in the HISTORY section of the header of the files. These items include a complete, concise description of the process used to create the file, any numbers such as crsplits that might be of interest to the user, any relevant ISR/TIR numbers and a listing of the files that went into the creation of the reference file. Refer to the TIR for more detail. The HISTORY should give an idea of the effect that the reference files will have in the calibrated data. Specify whether the header has been updated with this required information.
6-USEAFTER, PEDIGREE, DESCRIP, and COMMENT have been checked? Was the DESCRIP keyword updated with a summary of why the file was updated or created?:
Make sure that you updated the above header keywords with the appropriate information for the new changes or data. The DESCRIP keyword in the reference file header should be updated with a short one-line statement of why the file is being delivered, such as DESCRIP = "Revised sensitivities for first order M modes." The COMMENT keyword should list the people who created the file. If the files are meant to replace older versions, make sure the USEAFTER dates are an exact match, or the older versions will remain active in the database.
7-CDBS Verification complete?:
Make sure that your files are FITS and CDBS compliant. For this, run the fitsverify and certify script. The files should be delivered only when they pass these verifications.
8-Should these files be ingested in the OPUS, DADS and CDBS databases?:
There are cases when some of the reference files, for example STIS Synphot files, are not stored in the Archive or OPUS. In those cases, we have to make sure that we set the delivery properly for this to happen.
8a-If files are synphot files, should they be delivered to ETC?
Indicate if the synphot files should be delivered for use by the ETC as well as being delivered to CDBS.
9-Files run through CALXXX or Synphot?
Make sure that you run CALXXX or Synphot using the reference files that are going to be delivered. We cannot check for the scientific validity of the files, this is the responsibility of the instrument teams, but at least we want to make sure that the delivery of this/these file(s) will be transparent to the OTFR pipeline. The INS/CDBS Group is not going to perform this test, but only when absolutely necessary; we ask the instrument teams to perform this test themselves. Please list the specific version used.
10-Does it replace an old reference file?
If this is an update to previously delivered reference files then the answer should be "yes". If this reference file will cover a set of dates that have not been covered by any previous reference files, then the answer will be "no".
10a-If yes, which one?
If the answer to question 8 was yes, let us know the name of the reference file it replaces. (If the file being replaced is bad, and should not be used with any data, please indicate this here.)
11-What is the level of change compared with the old file?
The level of change depends on what changed in the file. If the file is a new reference file or it covers a range of dates not covered previous then the level of change is SEVERE or 100%. Another case when it should be considered as SEVERE is when the change warrants recalibration of the data. In the case of tables this could be applicable to only some rows. Please let us know which rows were affected by this level of change.
If one or several rows in a file changed and these changes will have a moderate impact in the results of the calibration or just make them better but do not warrant recalibration then the change is MODERATE. Also you could specify the percentage change, for example for the throughputs or images.
If the changes made to the file correct minor mistakes only, and those will not impact or have a negligible impact on the calibrated products, the change level is considered TRIVIAL.
11a-If files are pipeline reference tables, please indicate exactly which rows have changed.
This is determined by running the IDL script "compare_table.pro" You don't need to run this procedure for Synphot Throughput Tables. HOWEVER, if you modify the TMG or TMT Synphot tables, then you need to run this procedure for those two files. Show the output of compare_table.pro in the delivery form.
12-Please indicate which modes are affected by the changes in the file.
For example, for some files like STIS PHT reference file tables, only a few rows change for a given time; e.g. those that have information for E140M and E140H. This means that only STIS,FUVMAMA,E140H and STIS,FUVMAMA,E140M are affected by the changes to the files. For Darks, on the other hand, we can say that all the CCD data taken after the useafter date are affected, for BIAS we can say that all the CCD,Gain=1 bin=1x2 data are affected.
If the delivery of the file was made because there was an issue with the header (e.g. a keyword missing), but no change to the data, this information should be conveyed in this section, so we know that even the file was delivered, the science data will not change.
Another example would be if a STIS, CCD dark file with useafter date of "June 23, 2011" was delivered to remplace a file with useafter date= "June 22, 2011", this field should say that only CCD data take between June 22,2011 and June 23, 2011 will be affected.
13-Description of how the files were "tested" for correctness:
Briefly describe which kind of test you performed to assess the scientific correctness of the files. For example:
"Verified no change for first order modes when compared to previously ingested reference file. Calstis ignores this file for echelle and imaging modes."
"All extensions examined with imstat to count number and size of hot pixels. Run through calstis with data sets from test suite to ensure that changes in calibrated output were minimal as expected."
Remember that for Synphot data files you have to perform a test in Synphot and ETCs.
Are there any special needs associated with this delivery? Is the installation to be coincident with a specific OPUS build or are there other timing requirements or urgency? Note that the INS/CDBS Group makes every effort to deliver your files to OPUS within 24 hours of receiving this form, and will contact you in the event this schedule cannot be met.
15-Reason for delivery:
List details of the reason the files are being delivered, i.e. ”Update gains for instrument combination X and Y” or ”WFPC2 darks to be used for data taken after Dec. 1, 2008”.
16-Disk location and name of files:
Give an accessible disk location from where we can get a copy of the files to be delivered. Remember that the file names should not contain capital letters. Make sure that the files are readable by everybody. List all the reference files that are being delivered. For example,
-rw-r--r-- 2 acsref 10532160 Mar 24 23:13 grp03_hrc_rdrk.fits -rw-r--r-- 2 acsref 10532160 Mar 24 23:13 grp04_hrc_rdrk.fits -rw-r--r-- 2 acsref 10532160 Mar 24 23:13 grp05_hrc_rdrk.fits -rw-r--r-- 2 acsref 10532160 Mar 24 23:13 grp06_hrc_rdrk.fits -rw-r--r-- 2 acsref 10532160 Mar 24 23:13 grp07_hrc_rdrk.fits -rw-r--r-- 2 acsref 10532160 Mar 24 23:13 grp08_hrc_rdrk.fits -rw-r--r-- 2 acsref 10532160 Mar 24 23:13 grp09_hrc_rdrk.fits