9. Submitting the mask designs

Once the ODFs have been created and verified, you submit the ODF FITS to Gemini by means of the Observing Tool for double-checking and final cutting.

9.1. Standard naming convention for ODFs

The standard naming convention when submitting a mask is as follows:

G(N/S)YYYYS<type>PPP-XX_ODF.fits
N/S:North or South
YYYY:Year
S:Semester (A or B)
type:Q (Normal Queue Programs), LP (Large and Long Programs), DD (Director’s Discretionary Time), FT (Fast Turnaround)
PPP:Your program number
XX:The mask number

Examples:

  • GS2015AQ023-01_ODF.fits: Regular queue program at Gemini South, mask 01
  • GN2014BLP001-04_ODF.fits: Long-term program at Gemini North, mask 04
  • GS2014BDD008-03_ODF.fits: Director’s time at Gemini South, mask 03

Note

Masks that do not follow this naming convention will be removed from the Observing Tool and must be re-submitted.

The root name (e.g. GS2015AQ023-01) of a mask must be entered into the Observing Tool’s Custom Mask MDF field in the instrument static component when defining the phase II observations:

_images/gmmps_GMOS_MDF_component.png

Fig. 9.1 Entering the ODF’s root name in the Observing Tool.

9.2. Uploading ODFs (et al.)

Use the Observing Tool’s file attachment facility to upload the following files:

  • ODF FITS files (*.cat files are not accepted)
  • Pre-images or pseudo-images (if the masks are based on external catalogs instead of pre-imaging)

Once the ODF is uploaded, you must add a comment to it in the Observing Tool that unambiguously associates the ODF with its pre-image (or pseudo-image). Likewise, you may add a comment to each pre-image associating it with its respective ODF(s). At least one of the two is required.

_images/gmmps_fileattachment.png

Fig. 9.2 Add comments to the preimages (or ODFs) that unambiguously tell us which ones belong together.