|
Size: 6932
Comment:
|
Size: 10402
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 47: | Line 47: |
| 21:00-03:00; Stefano + Angel: the sky improved. YAY! We switch to NIKA2. YAYAYAY!!! Tuning OK. KIDs lost (old sweep!): Ar1 73/1055, Ar2 125/573, Ar3 64/1056. Starting pointing/focus; peak to peak sky along the timeline +/- 2 Jy at 2 mm. Tau(225) drops to ~0.2. We start 199-16 and observe 5 repetitions of PSZ1G080 using the old sweep. At 22:30 UT we perform a whole calibration sequence: skydip; then move to Uranus for pointing, focus, pointing, beammap (old sweep, can nr. 20221013s309), calib1scan (scan nr. 20221013s310), pointing, focus, pointing, SWITCH TO NEW SWEEP (~40 minutes lost), beammap (new sweep, scan nr. 20221014s1, note that box "I" is lost! We do what we can, and we decide to proceed anyway so to have at least one beam map take with the new sweep - although in precarious conditions - to be processed before the weekend), calib_1scan (scan nr 20221014s2), finally SWITCH back to the OLD sweep. | 21:00-03:00; Stefano + Angel: the sky improved. YAY! We switch to NIKA2. YAYAYAY!!! Tuning OK. KIDs lost (old sweep!): Ar1 73/1055, Ar2 125/573, Ar3 64/1056. Starting pointing/focus; peak to peak sky along the timeline +/- 2 Jy at 2 mm. Tau(225) drops to ~0.2. We start 199-16 and observe 5 repetitions of PSZ1G080 using the old sweep. At 22:30 UT we perform a whole calibration sequence: skydip; then move to Uranus for pointing, focus, pointing, beammap (old sweep, can nr. 20221013s309), calib1scan (scan nr. 20221013s310), pointing, focus, pointing, SWITCH TO NEW SWEEP (~40 minutes lost), beammap (new sweep, scan nr. 20221014s1, note that box "I" is lost! We do what we can, and we decide to proceed anyway so to have at least one beam map take with the new sweep - although in precarious conditions - to be processed before the weekend), calib_1scan (scan nr 20221014s2), finally SWITCH back to the OLD sweep (this time it took only 10 minutes). |
| Line 50: | Line 50: |
| a) The make-imbf of the beam maps delays the PIIC QL analysis of what comes later (10 minutes delay after scan nr. 20221013s309). I need to wait nevertheless, because I have to properly prepare for the next important beam map. <<BR>> b) We switch between old/new sweeps by copying the relevant ini files onto run72.ini. We have chosen to keep the numeration 72 for both sweeps, since they belong to the same cryo-cycle. Therefore we have run72_tp_old_sweep.ini and run72_tp_new_sweep.ini (tp=total power). |
a) with the old sweep, the PIIC QL reports that the pointing pixel (central KID of Ar2) is not working. b) The make-imbf of the beam maps delays the PIIC QL analysis of what comes later (10 minutes delay after scan nr. 20221013s309). I need to wait nevertheless, because I have to properly prepare for the next important beam map. <<BR>> c) We switch between old/new sweeps by copying the relevant ini files onto run72.ini. We have chosen to keep the numeration 72 for both sweeps, since they belong to the same cryo-cycle. Therefore we have run72_tp_old_sweep.ini and run72_tp_new_sweep.ini (tp=total power). |
| Line 64: | Line 65: |
| 03:00-09:00; | 03:00-09:00; Quang: Today we observed with NIKA2. The weather was good (taumeter ~0.22-0.29). I started with 122-16 project. When the source was too high, I switched to 093-22 project (1 rep. on PSZ2G186), then back to 122-16 again. Observed B211 and B213. |
| Line 66: | Line 67: |
| 09:00-15:00; | 09:00-15:00; Alexandre: After focus, started with calib_1scan on CRL618 and ALFORI. Then switched to COSMOS. At 11:30, following Dave's suggestion, we rebooted the electronic card that controls the box "I" and it was resuscitated successfully. Thank you! Starting from scan 20221014s66 we have all boxes active again. Still using the old sweep. Lost KIDs: Ar1 58/1055; Ar2 130/573; Ar3 52/1056. Continued on COSMOS until 11UT, switched to project 095-22 with AR2747. Six scans were obtained (~0.5 rep). Speed problems at high elevation (40 arcsec/s is recommended instead of 45), tau rising to 0.4, difficult focus solution. |
| Line 68: | Line 69: |
| 15:00-21:00; | 15:00: We installed the new SWEEP (dated 2022/10/10) permanently in the DAQ. As mentioned yesterday, '''the NIKA2 run number is kept to be 72'''. Number of KIDs lost: Ar1 68/1061; Ar2 5/581; Ar3 92/1077. We also successfully install the new DAFs for the PIIC QL monitor. Note that these DAFS are very preliminary: the beammap taken last night with the new sweep is missing the box "I", therefore the KIDs that belong to box "I" are not used in the PIIC QL monitor processing for now. The data are there, but not used in the quick look. No big deal. As soon as we have the chance to observe new beam maps with the new sweep and all boxes active, the DAFs will be updated and the PIIC QL will also use box "I". First scan on 1633+382 with the new sweep: 20221014s119. Focus and new pointing (20221014s125) after that OK. Thank you Robert for processing the beam map so promptly and for teaching Stefano how to install the new DAFs. |
| Line 70: | Line 71: |
| 21:00-03:00; | 16:00-21:00: Gianluca: We observed with EMIR between 4:30-7:30 PM CET (project ID 019-22). We then moved to NIKA2 (project ID 089-22 until the end of the shift). Acquisition restarted at 19:45. Number of KIDs lost: Ar1 70/1061; Ar2 3/581; Ar3 99/1077. 21:00-03:00; Stefano. I let the observations of 089-22 to reach completion and then I started with enthusiasm on 160-16 observing NGC7731, but it soon went too high (~74 deg of elevation) and therefore I had to interrupt. @20:15 UT tau ~0.2 and moved to 199-16 for 3 repetitions on PSZ1G080 (source completed!) and 2 repetitions on PSZ2G045. Beam map on Uranus, with new sweep and all electronic boxes working properly: scan 20221014s250 (wind gusts ~10 m/s). Calib_1scan 20221014s251. Skydip. Then I switched to 008-22, observing IC348 (2 repetitions, 39 minutes each). Notes:<<BR>> a) at 00:30 UT the taumeter starts giving increasing value of tau(225). Nevertheless in the directions of the observations the sky is stable and the peak-to-peak sky variations along the timeline of pointing./focus scans keeps within +/- 1 Jy. Therefore I go on with science in this direction of the sky despite what the taumeter says.<<BR>> b) Significant delays of the make-imbfits when dealing long scans, which induce long waiting times before starting the processing of subsequent pointing scans. Close encounters...<<BR>> [[attachment:IMG_7416_mod_sm.JPG|{{attachment:IMG_7416_mod_sm.JPG||width=400}}|target="_blank"]] [[attachment:IMG_7434_mod_sm.JPG|{{attachment:IMG_7434_mod_sm.JPG||width=400}}|target="_blank"]] |
Daily Reports
Contents
Oct 11th, Tuesday
16:30-21:00; Angel: Rainy and foggy after the weekly maintenance. Slight snowfall. The atmosphere was quite unstable after that, but mean tau has continuously dropped; still being unstable. Preparing setup for NIKA2.
21:00-03:00; Stergios, Angel: Unfortunately, tau raised above 1 at the beginning of the shift; still being unstable. At ~02h tau dropped up to ~0.7, with clear signs of relative atmospheric stability. DAQ of NIKA2 was started at 02:30 using the run72_tp_old_sweep.ini file ('old sweep': see Monday's report: https://publicwiki.iram.es/DailyReportsNika2Pool101022) as run72.ini file in order to check the instrument, main scripts, and quick data reduction before the science observations. Best of resonances (on-sky) gave the following bad/total KIDs relations: 138/1055 (Ar1), 123/573 (Ar2), 88/1056 (Ar3).
Oct 12th, Wednesday
03:00-09:00; Quang, Stergios, Angel: We carried out some tests with NIKA2, starting with a small pointing session (110 < Az. < 305 deg., 32 < El < 71 deg.) after a good focus. Pointing corrections, averages and rms are given in the table below.
Source |
Azimuth |
Elevation |
tau_225GHz |
Azimuth |
Elevation |
3C454.3 |
304.49 |
32.63 |
1.00 |
4.80 |
1.00 |
3C454.3 |
260.17 |
39.15 |
0.76 |
-4.50 |
-2.40 |
Uranus |
261.04 |
38.18 |
0.72 |
0.10 |
-3.30 |
Uranus |
173.19 |
69.57 |
0.74 |
-1.30 |
-0.30 |
Uranus |
212.62 |
66.66 |
0.79 |
-1.90 |
3.20 |
Uranus |
178.88 |
71.11 |
0.68 |
-2.60 |
3.40 |
Uranus |
235.49 |
59.20 |
0.90 |
-2.10 |
3.20 |
Mars |
182.77 |
69.65 |
0.69 |
-3.80 |
0.70 |
Mars |
110.36 |
60.85 |
1.17 |
-3.10 |
-1.40 |
HLTAU |
213.86 |
54.96 |
0.69 |
-0.50 |
0.50 |
Total average |
|
|
0.814 |
-1.34 |
0.17 |
Total rms |
|
|
|
2.62 |
2.37 |
A couple of calib_1scans on Uranus was obtained (20221012s20 and s42), as well as a skydip (s32). Atmosphere instabilities increased gradually during this test session. Regarding telescope and instrument, everything seems to be ready for starting the observations. At 05:50 we switched to EMIR. At about 06h and up to the end of the shift, Quang observed on behalf of the EMIR backup project 051-22. The tau from taumeter fluctuated a lot from 0.6 to 1.7. Tau at ~100 GHz from MRTCAL was stable: ~0.1.
09:00-15:00; Matthieu (on hold), Angel: Mean opacity was about 0.6 and 1.2 over the shift. Project D02-22 was observed with EMIR-E0 (6 reps. on LH206718 and 4 reps. on LH93597). Noncompatible opacity for EMIR-EO observations (Wsw) after ~12:45. We parked the telescope at ~13:00. Dense fog and light rain after that.
15:00-21:00; Gianluca (on hold): Bad weather, telescope stopped.
21:00-03:00; Angel: Opacity dropping to ~0.7, relatively stable. Continuing with EMIR backup programs, waiting for a qualitative improvement. Starting observations with 1 rep. on field C3, setup 1, project 018-22. Tuning with setup 2. One rep. on the fields C1, C2, and C3. Mean tau_225GHz was about 0.75 with some noticeable spikes, despite tau at ~100 GHz from MRTCAL being < 0.25 (=> pwv < 8 mm in the line of sight). Switching to project 043-22 at ~02:30 for observing the pre-stellar core L1544.
Oct 13th, Thursday
03:00-09:00; Quang: Today, as part of the NIKA2 pool, I observed project 043-22 using EMIR. The tau from taumeter was quite good for that: 0.5 to 0.8.
09:00-15:00; Guilaine: Observing with EMIR project 083-22. Do first pointing/focus on Mars, then pointing on a source close to the target. Observing source 8556-high, problem with the wobbler system, scan 176 canceled. Then do 8 repetitions. Focus on 0923+392. Observing source 18857-high, 3 repetitions, pointing with oscillations (due to anomalous refraction?) PWV is also rising, reaching 7mm. Scan 322 canceled and stop at 12:25UT.
15:00-21:00; Gianluca: Observing with EMIR between 6:00PM to 8:00PM CET (project 019-22). Between 8:00PM-9:30PM we moved to project 083-22, but weather conditions were unstable after pointing+focus, and we stopped the observations.
21:00-03:00; Stefano + Angel: the sky improved. YAY! We switch to NIKA2. YAYAYAY!!! Tuning OK. KIDs lost (old sweep!): Ar1 73/1055, Ar2 125/573, Ar3 64/1056. Starting pointing/focus; peak to peak sky along the timeline +/- 2 Jy at 2 mm. Tau(225) drops to ~0.2. We start 199-16 and observe 5 repetitions of PSZ1G080 using the old sweep. At 22:30 UT we perform a whole calibration sequence: skydip; then move to Uranus for pointing, focus, pointing, beammap (old sweep, can nr. 20221013s309), calib1scan (scan nr. 20221013s310), pointing, focus, pointing, SWITCH TO NEW SWEEP (~40 minutes lost), beammap (new sweep, scan nr. 20221014s1, note that box "I" is lost! We do what we can, and we decide to proceed anyway so to have at least one beam map take with the new sweep - although in precarious conditions - to be processed before the weekend), calib_1scan (scan nr 20221014s2), finally SWITCH back to the OLD sweep (this time it took only 10 minutes).
Additional notes:
a) with the old sweep, the PIIC QL reports that the pointing pixel (central KID of Ar2) is not working. b) The make-imbf of the beam maps delays the PIIC QL analysis of what comes later (10 minutes delay after scan nr. 20221013s309). I need to wait nevertheless, because I have to properly prepare for the next important beam map.
c) We switch between old/new sweeps by copying the relevant ini files onto run72.ini. We have chosen to keep the numeration 72 for both sweeps, since they belong to the same cryo-cycle. Therefore we have run72_tp_old_sweep.ini and run72_tp_new_sweep.ini (tp=total power).
Problem with DAQ at ~00 UT:
When restarting the DAQ in the process of switching to the new sweep, the DAQ had difficulties to start. It showed different symptoms: it had lost many KIDs and boxes; it was not reacting to commands; it died at start. After many attempts, we finally managed to recover, but box "I" remained almost completely lost. We tried with both the new and old sweep and these problems were there in both cases. When loading the new sweep, the DAQ is also very slow at measuring KIDs resonance frequencies. Number of lost pixels (new Sweep, box "I" lost): Ar1 154/1061; Ar2 8/581; Ar3 60/1077
Today's sun show:
Oct 14th, Friday
03:00-09:00; Quang: Today we observed with NIKA2. The weather was good (taumeter ~0.22-0.29). I started with 122-16 project. When the source was too high, I switched to 093-22 project (1 rep. on PSZ2G186), then back to 122-16 again. Observed B211 and B213.
09:00-15:00; Alexandre: After focus, started with calib_1scan on CRL618 and ALFORI. Then switched to COSMOS. At 11:30, following Dave's suggestion, we rebooted the electronic card that controls the box "I" and it was resuscitated successfully. Thank you! Starting from scan 20221014s66 we have all boxes active again. Still using the old sweep. Lost KIDs: Ar1 58/1055; Ar2 130/573; Ar3 52/1056. Continued on COSMOS until 11UT, switched to project 095-22 with AR2747. Six scans were obtained (~0.5 rep). Speed problems at high elevation (40 arcsec/s is recommended instead of 45), tau rising to 0.4, difficult focus solution.
15:00: We installed the new SWEEP (dated 2022/10/10) permanently in the DAQ. As mentioned yesterday, the NIKA2 run number is kept to be 72. Number of KIDs lost: Ar1 68/1061; Ar2 5/581; Ar3 92/1077. We also successfully install the new DAFs for the PIIC QL monitor. Note that these DAFS are very preliminary: the beammap taken last night with the new sweep is missing the box "I", therefore the KIDs that belong to box "I" are not used in the PIIC QL monitor processing for now. The data are there, but not used in the quick look. No big deal. As soon as we have the chance to observe new beam maps with the new sweep and all boxes active, the DAFs will be updated and the PIIC QL will also use box "I". First scan on 1633+382 with the new sweep: 20221014s119. Focus and new pointing (20221014s125) after that OK. Thank you Robert for processing the beam map so promptly and for teaching Stefano how to install the new DAFs.
16:00-21:00: Gianluca: We observed with EMIR between 4:30-7:30 PM CET (project ID 019-22). We then moved to NIKA2 (project ID 089-22 until the end of the shift). Acquisition restarted at 19:45. Number of KIDs lost: Ar1 70/1061; Ar2 3/581; Ar3 99/1077.
21:00-03:00; Stefano. I let the observations of 089-22 to reach completion and then I started with enthusiasm on 160-16 observing NGC7731, but it soon went too high (~74 deg of elevation) and therefore I had to interrupt. @20:15 UT tau ~0.2 and moved to 199-16 for 3 repetitions on PSZ1G080 (source completed!) and 2 repetitions on PSZ2G045. Beam map on Uranus, with new sweep and all electronic boxes working properly: scan 20221014s250 (wind gusts ~10 m/s). Calib_1scan 20221014s251. Skydip. Then I switched to 008-22, observing IC348 (2 repetitions, 39 minutes each).
Notes:<<BR>> a) at 00:30 UT the taumeter starts giving increasing value of tau(225). Nevertheless in the directions of the observations the sky is stable and the peak-to-peak sky variations along the timeline of pointing./focus scans keeps within +/- 1 Jy. Therefore I go on with science in this direction of the sky despite what the taumeter says.
b) Significant delays of the make-imbfits when dealing long scans, which induce long waiting times before starting the processing of subsequent pointing scans.
Close encounters...
Oct 15th, Saturday
Oct 16th, Sunday
Oct 17th, Monday