Diff for "CalibNika2Run14"

Back to the NIKA2 2nd Science pool

== Calibration observation plan ==

Draft discussed in ’Tiger Team’ meeting with Hervé, Nico, Juan, Martino, Jean-François, Samuel & Laurence

1. Alignment checks
   • to do if the first pointing sequence (pointing, focus, pointing) is off-source
   • check the alignment using the laser on Monday before the campaign

if beammaps are not good despite a good weather, a better matching of the optical and radial axis can be tempted (using the ecosorb)

1. Mini pointing session
   • to be done the first night of the campaign
2. Beammap at optimal axial and lateral focus
   • perform a beammap sequence, focus + pointing + beammap, at least once a day
   • span various elevation
   • if good weather try and use lateral focus corrections from the maps of the residual after subtraction of a Gaussian beam
   • do a few series of beammaps at different axial focus in a row: at z0 - 0.2mm, z0 - 0.3mm and z0 - 0.4mm
   1. Opacity
      • several skydips a day in all possible weather conditions, basically one per 8-hour shift
   2. Calibration
      • Monitor primary and secondary calibrators. Few of them but repeatedly along the run and at various elev.
      • Observe in priority MWC349: use the loop script comprizing 4 OTF scans, 3 times a day

      • Observe also Uranus, Mars & Neptune + NGC7027 (and optionally CRL2688)

   3. Gain elevation correction
      • at least two complete spans of the elevation from about 20 to 80 degrees using 3C84

Pointing

The pointing model is to be checked on the first night of the campaign by means of a mini pointing session (about 10 sources), and if needed a complete session (minimum 15 sources, 30 is better). [Add here a summary of the pointing session(s)]

Beammaps

Beammap sequences, which are focus + pointing + beammap, are to be done at least once a day, spanning various elevation, at the best average focus (z central - 0.2 mm). If the weather conditions are good enough, lateral focus corrections can be implemented as well, using the maps of the residual after subtraction of a Gaussian beam.

Beammap analysis status

The table below gathers the beammap scan ID, comments related either to the observing condition or to the reduced beammap quality and the analysis status

Status "done" means the analysis is completed, namely the kidpar file is produced using a 2-step iteration analysis, and uploaded in SVN.

Special beammap sequences

• For the optimization of the best average focus, a few series of beammaps at different axial focus in a row are needed: the focus settings to be spanned are z0 - 0.2mm, z0 - 0.3mm and z0 - 0.4mm.
• For the study of the elevation impact and the test of destriping methods, couples of beammap with orthogonal scanning startegy will be made (using @beammap99.. a (default) and e (along the elevation)).

Opacity

A skydip scan per 8-hour observation shift, in all possible weather conditions, is needed

Table for gain curve task (3C84, i.e. 0316+413 in nikas-17)

Gain-elevation monitoring

Table for gain curve task (3C84, i.e. 0316+413 in nikas-17)