Primary and secondary calibrator observations have been reduced using the specifically designed
dimmconfig_bright_compact.lis. The maps produced from this are then analysed using tailor-made
Picard recipes. For instructions on applying the FCFs to your map see Section 8.1 and Appendix E.
A map reduced by the map-maker has units of pW. To calibrate the data into units of janskys (Jy), a set of bright, point-source objects with well-known flux densities are observed regularly to provide a flux conversion factor (FCF). The data (in pW) can be multiplied by this FCF to obtain a calibrated map. The FCF can also be used to assess the relative performance of the instrument from night to night. The noise equivalent flux density (NEFD) is a measure of the instrument sensitivity, and while not discussed here, is also produced by the Picard recipe shown here. For calibration of primary and secondary calibrators, the FCFs and NEFDs have been calculated as follows:
SCUBA2_FCFNEFDtakes the reduced map, crops it, and runs background removal. Surface-fitting parameters are changeable in the Picard parameter file.
FLUX_450.MYSRC = 0.050and
FLUX_850.MYSRC = 0.005(where the values are in Jy), for example.
where is the total flux density of the calibrator, is the integrated sum of the source in the map (in pW) and is the pixel area in arcsec, producing an FCF in Jy/arcsec/pW.
producing an FCF in units of Jy/beam/pW. The measured peak signal here is derived from the Gaussian fit of beamfit. The peak value is susceptible to pointing and focus errors, and we have found this number to be somewhat unreliable, particularly at 450 m.
For a true point source, the measured peak pixel in a map calibrated in units of Jy/beam (using the Beam FCF) is equivalent to the integrated total flux of the same source in a map calibrated in units of Jy/arcsec (using the Arcsecond FCF). The Orac-dr processing routine will automatically select the appropriate FCF based on the default data-reduction recipe that was linked to your data at the time of observations. Note that the data-reduction recipe can easily be changed when running Orac-dr (see Section 4.4.2 for details).
Starlink automatically applies the following multiplicative extinction correction to SCUBA-2 data:
where is the opacity at the given frequency, .
The atmospheric opacity at SCUBA-2’s operating frequencies are defined in terms of the opacity at 225 GHz. Optimizing the uniformity of the SCUBA-2 secondary calibrator fluxes as a function of atmospheric transmission has allowed calculation of the atmospheric opacity relationships for the SCUBA-2 450 m and 850 m pass-bands to be determined. Full details of the analysis and on-sky calibration methods of SCUBA-2 can be found in Dempsey et al. (2013)  with updated relations provided in Mairs et al. (2021) .
Archibald et al. (2002)  describes how the Caltech Submillimeter Observatory (CSO) 225 GHz opacity, , relates to SCUBA opacity terms in each band, and . The JCMT water-vapour radiometer (WVM) uses the 183 GHz water line to calculate the precipitable water vapour (PWV) along the line-of-sight of the telescope. This PWV is then input into an atmospheric model to calculate the zenith opacity at 225 GHz (). Historically, this has allowed for ease of comparison with the adjacent CSO 225 GHz tipping radiometer.
The updated opacity relationships (to be used in Equation B.3) derived by Mairs et al. (2021)  have been adopted as the default as of Starlink Release 2021A:
Previously, (Starlink Versions 2018A and before) adopted as defaults the opacity relationships found by Dempsey et al. (2013) :
The updated opacity relationships as of Starlink Release 2021A will affect 450-m data obtained in very dry conditions and 850-m data obtained in very dry or very wet conditions by up to 5% (see Figure B.1).
Note that the default extinction corrections are intrinsically connected to the default FCFs applied. If applying extinction corrections derived by Mairs et al. 2021 (), the matching FCFs must also be applied (see Appendix E). The Orac-dr software assumes the Mairs et al. (2021)  results beginning in Starlink Release 2021A. Starlink Release 2018A and previous versions assume the Dempsey et al. 2013  values by default.
The SCUBA-2 filter characteristics are described in detail on the JCMT website1.
The extinction correction parameters that scale from
to the relevant filter have been added to the map-maker code. You can override these values by
ext.taurelation.filtname in your map-maker config files to the three coefficients
that you want to use (following the form ),
filtname is the name of the filter). The defaults are listed in