Size: 1624
Comment:
|
Size: 1652
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 28: | Line 28: |
Summary (Uranus): 20240122s134 track 20240122s135 to 138 pointing 20240122s139 OTF 140 OTF tTune 5 instead of 3 141 OTF no zigzag 142-144 pointing |
Summary (Uranus):<br> 20240122s134 track<br> 20240122s135 to 138 pointing<br> 20240122s139 OTF<br> 140 OTF tTune 5 instead of 3<br> 141 OTF no zigzag<br> 142-144 pointing<br> |
Back to the NIKA2 Run 64 main page
Daily Reports
Contents
January 22nd, Monday
We take the telescope at 14:50 UT. It was pointing very close to the Sun for a while, because of Sun avoidance tests, therefore it will take at least 2h before it relaxes. Nevertheless, we lauch several scans to study how the tracking behaves.
NIKA2 is tuned. The PIIC monitor tells us that the the data of the pointing pixel (Ar2) are corrupted. We tune again (lost KIDs: 58, 8, 68), but we don;'t recover the pointing pixel.
We study the tracking. Lots of overshooting at the turns between subscans. Experiments with Uranus (starting at 30 deg elevation): pointing scans (20240122s135 to 138) standard OTF (139) OTF with tTune changed from 3 to 5 seconds (140) OTF with no zig zag (141)
When scanning only in Azimuth, the overshoot follows a repeating pattern. Without zigzag we avoid the big positive overshoot
The temperature inside NIKA2 oscillates by 0.2 mK (0.1 mK amplitude) every ~7 minutes Dave reduces the pressure of the pump. We wait a bit for a new equilibrium.
Note that the EMIR pointing model is installed. We have no updated NIKA2 pointing model. We should make a pointing session, as soon as the telescope relaxes. For now we apply the big offsets given by the PIIC monitor (-16 arcsec, -54 arcsec) and the pointing pixel is recovered. Pointing scans: 142 to 144
Summary (Uranus):<br> 20240122s134 track<br> 20240122s135 to 138 pointing<br> 20240122s139 OTF<br> 140 OTF tTune 5 instead of 3<br> 141 OTF no zigzag<br> 142-144 pointing<br> 145-149 focus sequence