Back to the NIKA2 main page

Daily Reports (2025/10/21-28, NIKA2 run 75, Cryo run 87)

Observers on-site: Monica Rodriguez, Samuel Leclercq, Raphaël Maris, Stefano Berta and Stergios Amarantidis (AoD).

Operators: Sergio and Mario.

Shifts: 10-16 Raphaël; 16-22 Samuel; 22-4 Stefano; 4-10 Monica.

All times reported are in UTC (if not mentioned otherwise).

Preparatory notes

Please, remember to use the focus value of Ar1 (roughly Ar2 + 0.65 mm, but use directly the focus Ar1 monitor if possible). Please use the custom modified focus script focusOTF-Z_2025.pako.

Therefore, importantly, when checking the quality of the beam on a pointing map to decide if a new focus is needed, it is better to do it on the Ar1 map, because that's the one focused at best.

Project D01-25 (M51) requires DAQ restarting with the run87_newSweep_M51_tp.ini file. Come back to run87_neSweep_tp.ini after observing this project.

Please fill the Table with the Ar1,2,3 focus values as follows. At best, make one table per day.

Similarly, if any beam maps are taken:

October 21st, 2025, Tuesday

15:00-22:00 [All]: Maintenance finished with no issues. DAQ started at 14:10 with 21/3/47 bad KIDS for arrays 1,2 and 3, respectively. Repeating the DAQ at 14:24 with 28/3/89. Trying to point at NGC7027 and MWC349 but the weather is too unstable (p2p~10-20Jy/beam), moving to K3-50A for pointing and focus (using the modified 2025 script). Moving for calib_1scan to MWC349, etc. Switching to project 053-25 (source 1803+784 is better for pointing/focus). One repetition of L1157B. Around 17:12 we moved to a skydip and then to the normal flux calibrators. After pointing/focus on 1803+784 we move to project 022-25. Two repetitions of Ceph-4.

22:00-04:00 [Stefano]: here follows the evolution of the night:

Mercury and Mars at sunset.

October 22nd, 2025, Wednesday

04:00-10:00 [Monica]: Pointing, Focus and calib_1 scan in Uranus. Then project 066-25 (Source M31_inner) for 1 hr (1 round), weather started to became very unstable in the last scan peak to peak variations > 50 Jy/beam (Ar2). Then pointing and focus in Uranus, then the opacity rise to 1.0, so we stopped ~ 50 minutes. Continue with pointing, focus, pointing and calib_1scan in Uranus and Alfori. Then observe project 082-25 (Source PSz2G107) 2 rounds (~ 2hr).

10:00-16:00 [Raphaël]: Pointing Focus on f source 1418+546. Then observe project 082-25 (Source PSZ2G107) 2 rounds (2 hr). Making Skydip. Starting D01-M51 source. Changed to 47 Hz sampling rate: 15/4/37 lost KIDs. Nothing so bright around our science target so we move to 1633+382 to focus. Then back to 1418+546 and then to the science target (observed 6 repetitions of M51).
- @11:15 UT, Jean fixes a problem in the make-imbf. Yesterday the new make-imbf did not produce the imbf files of scan 20251021s171. we ran it manually, but the result was flawed. Jean fixed the manual version of the new make-imbf, that was looking for the Antenna traces in the wrong location. Thank you! The initial issue (that the automatic version did not produce the s171 files) is under investigation.

16:00-22:00 [Samuel]: Tau values have increased above the threshold of the project D01-M51 (0.4) thus we move to calib_1scan observations with the higher sampling rate of project D01-25 and monitor the weather. Pointing on MWC349 with p2p~10Jy/b, repeating + focus. Weather seems to go better in fact: calib_1scan on MWC349 gives now p2p ~ +-5Jy/b and tau=0.37... same for CRL2688 and for NGC7027 --> weather stabilized below D01-25 limits, so we iterate more on it after all. Alas, the time to point on nearby point source and run the script weather evolved just above limits. Switch back to 23 Hz acquisition. After reloading frequencies and tune: bad pix = 30/5/123 for Arr 1/2/3. Lots of lost kid on Arr3 probably due to relatively high sky fluctuations now. But conditions still good enough for project 053-25, though with a little doubt regarding the stability, p2p still < +-10 Jy/b in pointing scans preceding the series of scans on L1157.
- Below, screenshot showing the difference of response to sky fluctuation between Arr1 and Arr3: Arr3 gets x3 higher p2p response than Arr1 besides identical calibrated value for the source! (see today's regular NIKA2 meeting for the discussion about this topic).

Hello!

22:00-04:00 [Stefano]: Here follows th evolution of this shift:

@22:15 UT. While observing, I am thinking again about the different behaviour of Ar1 and Ar3 in variable sky noise. Practical example: one scan can have Ar1 sky noise peak to peak variations of 10 Jy/beam, and the same scan, same sky, same time, has a peak to peak variation in Ar3 of 20 Jy/beam. I asked myself if this could be due to a problem of calibration in Ar3 or Ar1. Last week, I have checked the extracted fluxes (in the PIIC QL monitor on the fly at the telescope) for few pointing scans and did not find any factor of two difference. I will have to check again more systematically when I have time. Note, anyway, that the calibration factors for run 75 are not available yet (they'll be determined at the end of the run or of the semester, as usual). The calibration factor we're using are those of March-June, when the Ar3 RPPs/Kidpars were missing the majority of KIDs. Therefore anything is possible at this point.

New example of Ar1 (left) and Ar3 (right) different behaviour. This is scan 20251022s209:
Ar1 (left); Ar3 (right); scan 20251022s209.

Yesterday/today I reduced the biggest scans taken during the recommissioning week (last week) and produced with the NEW make-imbf. The reduction went fine. This means that thee is no problem of non-monotonic MJD in these scans (this was spotted some time ago and was traced to some differences between old and new make-imbf and on how the new ACU traces are treated.

New make-imbf fail events:
20251022s196 is missing the Ar3 imbf (new make-imbf)
20251023s5 is missing the Ar1 imbf (new make-imbf)
20251023s17 is missing the Ar2 imbf (new make-imbf)

A friendly vulture at Pico. The view from above. Our beloved telescope.

October 23rd, 2025, Thursday

04:00-10:00 [Monica]: Pointing, focus and calib-1scan in Uranus and Alfori. Unfortunately the tau was ~ 0.5 all the time and seems to stay in that value or increase. So I decided to move to EMIR since the NIKA2 projects require tau values ~ 0.3. For EMIR I selected project D06-25 but there was a problem with band E150 (check the operator's report for details). So I moved to project 003-25 since they only require the band E090. At 6:00 UTC the weather improves a bit, and tau is ~ 0.4 so we moved back to NIKA2. We started the DAQ (run87_newSweep_M51_tp.ini). Bad KIDS were 24/6/91 for Ar2/Ar1/Ar3 respectively. Then observe project D01-25.

10:00-16:00 [Raphaël]: Pointing on the f source 1418+546 , observe D01-25. At around 8:10 UTC the weather were unstable (p2p~10Jy/b). At 8:17 UTC, I did the 9 repetition of the project D01-25 (Source M51) even with this unstable condition (p2p ~10Jy/b) and with a tau ~0.4. At 9:00 UTC, gain unstable condition (p2p ~ 10 Jy/b) and tau > 0.4, decide to move from another project. Pointing source b 1641+399 (p2p ~10 Jy/b). Focus 1641+399. At 9:57 UTC, I move to project 051-L1157B

16:00-22:00 [Samuel]: ...

22:00-04:00 [Stefano]: ...

October 24th, 2025, Friday

04:00-10:00 [Monica]: ...

10:00-16:00 [Raphaël]: ...

16:00-22:00 [Samuel]: ...

22:00-04:00 [Stefano]: ...

October 25th, 2025, Saturday

06:00-12:00 [Stergios]: ...

12:00-18:00 [Raphaël]: ...

18:00-24:00 [Samuel]: ...

24:00-06:00 [Stefano]: ...

October 26th, 2025, Sunday

06:00-12:00 [Stergios]: ...

12:00-18:00 [Raphaël]: ...

18:00-24:00 [Samuel]: ...

24:00-06:00 [Stefano]: ...

October 27th, 2025, Monday

06:00-12:00 [Stergios]: ...

12:00-18:00 [Raphaël]: ...

18:00-24:00 [Samuel]: ...

24:00-06:00 [Stefano]: ...

October 28th, 2025, Tuesday

06:00-10:30 [Stergios]: ...