From: Kaike Subject: Re: [sloan-25mlog 6960] 2.5m obslog 20231214 (SJD 60293) Date: Fri, 15 Dec 2023 09:23:24 -0700 --Apple-Mail=_3F10B303-2A53-4870-BFE1-729A100C2A43 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Dec 15, 2023, at 6:12=E2=80=AFAM, dmbiz@apo.nmsu.edu wrote: >=20 >=20 > APACHE POINT OBSERVATORY SDSS 2.5M >=20 > OBSERVING LOG > Thursday December 14, 2023 >=20 > (SJD 60293) >=20 > ---- Observing Team ---- >=20 > Dmitry Bizyaev >=20 >=20 > ---- Observing Plan ---- >=20 > Thu 14 Dec 2023 60293 0.07 00:56 01:11 12:44 23:41 11:17 --- dark = (11.6 h) plus 0.3 h for 12 deg design >=20 > Conor's tests, weather permits >=20 > ---- Observing Summary ---- >=20 > Clear, productive night. Observed from queue and did Conor's tests.=20 > The seeing was variable and focus drifted a lot, which=20 > lead to rather low signal, especially in RM exposures.=20 > I had to run a GFA focus loop time to time in order to=20 > get the best focus. =20 >=20 > Notes > ----- > - dust collected: 5.4K >=20 > - Conor's tests were run. After their finishing it turned out that > when I issued "tcc rotate 0 mount" (and 120, 240), rotator tracking=20= > stopped, but it wasn't reflected in the STUI Status panel.=20 > As a result, Test 0 was good, but test 1 and Test 2 all brought up > very elongated guider images (all GFAs in X-direction =3D> rotator = problems). > Since I expected some defocused images, it confused me and > the tests 1 & 2 need to be redone. The plan > how to turn on rot tracking during the test is made (tcc track > after the rotator move, or use rot 0 obj instead).=20 >=20 >=20 >=20 > Sad story: > I used STUI menu and went to a crowded field. The stars didn't look = bad, but since I started the test, focus was obviously off, so I was not = surprised by donuts and elongated images. After finishing the test and = taking a close look, it turned that ALL images are smeared in the RA = direction. Despite showing "Tracking" in STUI, The actual tracking was = either completely turned off, or it was very wrong. I tried "tcc track", = and got rounded images, but it was at the end of the test. The test data = are not good. I warned Conor. He thinks that rotator stopped tracking = when it was moved to 0, 120, or 240. >=20 >=20 Tcc keyword mount means the telescope axis will stay where it is. The = command we need here are: The regular tcc track RA Dec command will track the field with at obj = rotator angle =3D0, but the physical rotator angle usually will not be = 0. Check where the rotator angle is, then use "tcc rotator xx.0 = object=E2=80=9D to have the telescope track the same field at a = different physical rotator angle.=20 Example, after the regular track command you find the physical rotator = angle is at 100 degrees (note that STUI shows the obj rotator angle 0 at = this time), and you want to track the same field at a physical rotator = angle of 0 degree, issue a command =E2=80=9Ctcc rotator -100.0 object=E2=80= =9D (the STUI should shows the object rotator angle of -100.0), which = will send the rotator to 0 degree and keep all three axes tracking the = same field.=20 --Apple-Mail=_3F10B303-2A53-4870-BFE1-729A100C2A43 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 On Dec 15, 2023, at 6:12=E2=80=AFAM, = dmbiz@apo.nmsu.edu wrote: = &n= bsp; APACHE POINT = OBSERVATORY SDSS 2.5M = &n= bsp; &nbs= p; OBSERVING LOG = &n= bsp; &nbs= p;Thursday December 14, 2023 = &n= bsp; &nbs= p; (SJD = 60293)---- Observing Team ----Dmitry = Bizyaev---- Observing Plan ----Thu 14 Dec 2023 60293 = 0.07 00:56 01:11 12:44 23:41 11:17 --- dark (11.6 h) plus 0.3 h for 12 = deg designConor's tests, weather permits---- Observing = Summary ----Clear, productive night. Observed from queue and did = Conor's tests. The seeing was variable and focus drifted a lot, = which lead to rather low signal, especially in RM exposures. I = had to run a GFA focus loop time to time in order to get the best = focus. Notes------ dust collected: = 5.4K- Conor's tests were run. After their finishing it turned = out that when I issued "tcc rotate 0 mount" (and 120, 240), = rotator tracking stopped, but it wasn't reflected in the STUI = Status panel. As a result, Test 0 was good, but test 1 and = Test 2 all brought up very elongated guider images (all GFAs = in X-direction =3D> rotator problems). Since I expected = some defocused images, it confused me and the tests 1 & 2 = need to be redone. The plan how to turn on rot tracking during = the test is made (tcc track after the rotator move, or use rot = 0 obj instead). Sad story:I used STUI menu and went = to a crowded field. The stars didn't look bad, but since I started the = test, focus was obviously off, so I was not surprised by donuts and = elongated images. After finishing the test and taking a close look, it = turned that ALL images are smeared in the RA direction. Despite showing = "Tracking" in STUI, The actual tracking was either completely turned = off, or it was very wrong. I tried "tcc track", and got rounded images, = but it was at the end of the test. The test data are not good. I warned = Conor. He thinks that rotator stopped tracking when it was moved to 0, = 120, or 240.Tcc = keyword mount means the telescope axis will stay where it is. The = command we need here are:The regular tcc track = RA Dec command will track the field with at obj rotator angle =3D0, but = the physical rotator angle usually will not be 0. Check where the = rotator angle is, then use "tcc rotator xx.0 object=E2=80=9D to have the = telescope track the same field at a different physical rotator = angle. Example, after the regular track = command you find the physical rotator angle is at 100 degrees (note that = STUI shows the obj rotator angle 0 at this time), and you want to track = the same field at a physical rotator angle of 0 degree, issue a command = =E2=80=9Ctcc rotator -100.0 object=E2=80=9D (the STUI should shows the = object rotator angle of -100.0), which will send the rotator to 0 degree = and keep all three axes tracking the same = field. = --Apple-Mail=_3F10B303-2A53-4870-BFE1-729A100C2A43--