NIKA2 run #4 March 2016
Goals of the run
Continue tests on the instrument with same arrays since run 1 and same NIKEL boards as run 3.
Check data & flags consistency & synchronization: Raw, FIT for Pipeline, IMBFIT.
- Test possible improvement on synchronization of NIKA2 tunings and decalage with telescope scans information (e.g. subscan start and stop, etc.): more direct link with ELVIN or use to UDP to a nika2-a port) [see with Granada staff], check tuning and decalage durations vs time between subscans.
- Investigate best threshold for decalage between subscan, because systematic ftone jumps between subscans will kill the sky noise low frequency decorrelation. So decalage between subscan should be only in case sky background variations would be so big that we would loose the resonnaces otherwise, hence the scan. An optimum has to be found.
Test synchronization of NIKA2 samples with telescope coordinates: some hints in previous data of possible systematic error (e.i. using PPS time maybe not sufficient) ==> to test this possibility do scans (beam maps) at various speed and and scan pattern (not only zig-zag, but also only increasing azimuth, only increasing azimuth etc.--> need to edit PaKo scripts to do that!).
- Optimisation of tone comb position: arrays 1 and 3 have systematically about one line of pixels missing per multiplexed feed line; this is due to the limited bandwidth of the NIKEL boards w.r.t. the resonance frequencies span, we may recover a number of pixels by optimizing the tone comb position.
Understand possible stability difference between array 1 and array 3: array 1 seems more stable though both arrays are identical, electronic boards are possible suspects -> 2 exchange boards and do beam maps.
Beams characterization is still a priority, we needs additional maps to investigate beyond current status(*): more beam maps for better statistics, XYZ focus optimization (first probing various locations on the focal plane like run2 focus campaign (see the commisionning how to page), then with several beam maps near optimal XYZ focus position). Pay attention also at the possible dependence with elevation.
- Free bonus of beam maps: increase statistics on kid stability, photometry, sensitivity and time line features.
- Skydips
- A session of KIDs working point optimization ?
- Continue observations of many calibrators to monitor our sensitivity and photometry.
- Continue tests on polarization mode: beam maps, various scan speed and sampling frequencies.
- Depending on the completion of previous items, go for more advanced characterizations, namely deep integrations (check rms vs sqrt(time)) and extended features (test various map making strategies in analysis software [Pipeline, scanamorphos, etc.]).
(*) Status of beams characterization from previous runs:
- At 2mm the dichroic deformation is dominant, besides the array (CPW + bondings design) is visibly more unstable than 1mm arrays (micro strip design).
- On all bands there is an asymmetry on beams pedestal, which is also visible on lab measures, indicating a possible optics problem in the cryostat, though simulations can't re-create it without more destructive effects so far. Need deeper analysis of lab measures vs beams at telescope.
- On all bands the 1st side lobe is at 10% level of the peak against 2% predicted per pure diffraction plus elliptic side lobes. Optics simulations show various possibilities to create such effects. Two of them seem realistic and at least partially recognised: non-optimal XYZ focus, and telescope astigmatism due to high order deformations terms not compensated by the homology structure of the parabola. From holography measurements and beam efficiency obtained with heterodyne instruments (which have 14dB edge taper and thus reduce significantly this effect), simulations show that telescope astigmatism is a significant component. Is it all of it ? To investigate this we need beam maps at optimal XYZ focus, at various elevation and various period of the day; the stable weather low opacity mid night optimal conditions being the most important one.
The detailed characterization plan established for run 1 is still valid, but needs to be updated; you can still look at it to check possible missing action items: http://www.iram.fr/wiki/nika2/index.php/NIKA2_Run1_30m_CharacterizationPlan A more summarized and concise version will be written as soon as possible (SL).
Preparation of the run
Telescope Schedule week 1 Telescope Schedule weeks 2
Staff of the run: table of the nights spent at the observatory for the NIKA2 collaboration members participating to the run (T means Tuesday, S means Saturday, first night with NIKA2 staff is Tuesday 29 September, last night is Monday 9 November, 1 stands for night scheduled at the telescope, p stands for possible extension in case of problem with the cryostat). In italic: not at the telescope but on watch for possible remote help or intervention on the software and/or remote control.
People\Date |
T1 |
2 |
3 |
4 |
S5 |
6 |
7 |
T8 |
9 |
10 |
11 |
S12 |
13 |
14 |
A.Catalano |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
|
|
|
|
|
|
|
A.Maury |
|
|
|
|
|
|
|
1 |
1 |
1 |
1 |
1 |
1 |
|
J.F.Macias-Perez |
|
|
|
|
|
|
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
J.Ph.Bernard |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
M. de Petris |
1 |
1 |
1 |
1 |
1 |
1 |
|
|
|
|
|
|
|
|
A.Beelen |
|
|
|
|
|
|
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
F.Ruppin |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
|
|
|
|
|
|
|
C.Romero |
|
|
|
|
|
|
|
|
|
1 |
1 |
1 |
1 |
1 |
H.Aussel |
|
|
|
|
|
|
1 |
1 |
1 |
1 |
1 |
1 |
|
|
Sleep at obs. |
4 |
4 |
4 |
4 |
4 |
4 |
6 |
4 |
4 |
5 |
5 |
5 |
4 |
3 |
AOD: A.Sievers/P.Garcia on week 1; F.Damour/J.L.Santaren (operators) on week 2. Astronomer on Duty