Joint Astronomy Centre
Show document only
JAC Home
JCMT
UKIRT
Contact info
JAC Divisions
OMP
Outreach
Seminars
Staff-only Wiki
Weather
Web Cameras
____________________

JCMT home
Telescope
Pointing
Instrument Collimations

Instrument Collimations

This document is a guide for the Pointing Guru in the use of observed pointing offsets.

  • Collimations are instrument-specific offsets from the model.
  • The collimations are kept in Rx/FE-specific files :
    • /jac_sw/itsroot/src/wrappers/rxa/initialise/instrument_rxa.ent
    • /jac_sw/itsroot/src/wrappers/rxb/initialise/instrument_rxb.ent
    • /jac_sw/itsroot/src/wrappers/rxw/initialise/instrument_rxwb.ent
    • /jac_sw/itsroot/src/wrappers/rxw/initialise/instrument_rxwd.ent
    • /jac_sw/itsroot/src/harpb/XML/instrument_harpb.ent
    and are called X (azimuth collimation) and Y (elevation collimation).
  • For whichever instrument/receiver/FrontEnd is recognized as our primary instrument, the collimations should be (0,0).
  • Updates of the pointing model should be done (for convenience) using data from the 'primary' FE, while the collimations for the other receivers may be updated using smaller datasets.

The instructions below treat, in order of increasing confusion, the various datasets that may be available for use in updating the collimations:

  • Large pointing datasets obtained with the primary FE should be analyzed using TPOINT with appropriate input of the current JCMT pointing model. TPOINT outputs the values for the (7) parameters of the new model which may then be transferred to the appropriate file (/jac_sw/itsroot/src/tcs/thi/THI.tide) for future use.

  • Small datasets or single pointings with other receivers may be used only to update their collimations.

    If (uaz,uel) are the means of the observed offsets as recorded in the last two columns of the TPOINT .pnt file then a TPOINT analysis of the data using the following command sequence

    • fix
    • use IE CA
    • fit

    will produce values of CA and IE that are related to the default values, CAdefault, IEdefault, as stored in the collimation files above, and to uaz and uel as follows:

    • CA = CAdefault + uaz
    • IE = IEdefault - uel

    (See this example data analysis.)

    These new values of CA,IE may be entered as the defaults for future improved performance, i.e. for residuals (uaz,uel) that should be more preciesly (0,0).

  • If small datasets or single pointings with the primary-FE show non-zero offsets and if these are interpreted to reflect changes to the overall collimation of the telescope, then they may be used to update the pointing model terms CA and IE (which will then affect future pointings with any receiver).

    However, there is a sign convention that must be obeyed, as was revealed in a previous document. Simply put, if you point with JCMT/primary-FE and observe pointing offsets in azimuth and elevation of (uaz,uel) -- and you wish to rectify the pointing model so that future pointings (with any receiver) will appear at offsets of (0,0) -- then you should run the data through TPOINT, FIX all 7 parameters, USE IE CA, note the changes to these two collimation values, and change

    *         CA   to    old_CA + d(CA)
    *         IE   to    old_IE - d(IE)
    

  • Large pointing datasets taken with other receivers pose the greatest challenge. They ought certainly to allow the model to be updated, but the impact on the collimations is where it gets messy. Things are simpler if such data are taken under circumstances where there is no expectation of a change in relative collimations.

    Consider first the acquisition of a large pointing dataset obtained with receiver Rx in circumstances where no change to the model is expected. Analysis by TPOINT should suggest no changes to the values for CA, IE, meaning, in reality, no changes to the differences in collimations between Rx and the primary-FE, meaning in effect no changes to the collimations for Rx, since those for the primary-FE are maintained at (0,0). If non-zero offsets are seen you are faced with determining, separately (how ?) whether the problem lies with the model or the receiver (collimations).

    Suppose instead that there is a need to redetermine the model using Rx under circumstances that ought to preserve the relative collimations. Suppose that

    • the old receiver collimations were (XRx,YRx)
    • when processed with TPOINT the new data show non-zero changes in (CA,IE) of (uazdata,ueldata), as well as to the other model parameters.

    What to do with the collimations ? and the others parameters ?

    • Changes to the other parameters reflect structural misalignments which should be common to all receivers and may be incorporated into the TPOINT pointing model irrespective of the RX used.
    • The collimations for the primary-FE may be left as (0,0).
    • Those for Rx must remain as (XRx,YRx) . . .
    • . . so the new values of CA,IE suggested by the TPOINT analysis may then be used as if they had been determined by use of primary-FE data; i.e. change CA to (CA + uazdata), IE to (IE - ueldata).

    If data are taken with Rx when both the model and the relative collimations may have changed then any resulting model may work (i.e. generate no further observational offsets) only for Rx itself. The relative collimations will need establishing separately and the system reverted eventually to one based on the primary-FE.

  • Contact: Iain Coulson. Updated: Tue Jul 3 14:00:56 HST 2007

    Return to top ^