From: Conor Sayres Subject: Re: [sloan-25mlog 6320] 2.5m obslog 20221101 (SJD 59885) Date: Wed, 2 Nov 2022 12:41:41 -0400 --Apple-Mail=_5B1329E1-A811-4471-9E7A-FB99CB180BE0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I believe the command would be tcc set weather airtemp=3DX (https://www.apo.nmsu.edu/Telescopes/TCC/Commands.html#SetWeather = ) But I don=E2=80=99t think it will have any effect on something like = guiding. Once the guider takes over, it should drag the telescope to = wherever it wants it. > On Nov 2, 2022, at 11:00 AM, Jos=C3=A9 S=C3=A1nchez-Gallego = wrote: >=20 > Oh, but that definitively could have messed up the TCC refraction = correction itself. Conor may know about that. >=20 > Jos=C3=A9 >=20 >=20 > On Nov 2, 2022 at 07:59:03, Jos=C3=A9 S=C3=A1nchez-Gallego = > wrote: >> Actually I think I never got around using current temperatures for = the refraction correction. I think it always uses 10C and RH 50% for all = coordinate conversions and refraction calculates. If the temperature was = very different during that field, maybe that would contribute to the = large RMS, although 3 arcsec looks very large. >>=20 >> Jos=C3=A9 >>=20 >>=20 >> On Nov 2, 2022 at 07:55:31, Kaike > wrote: >>>=20 >>>=20 >>>> On Nov 2, 2022, at 6:30 AM, dmbiz@apo.nmsu.edu = wrote: >>>>=20 >>>>=20 >>>> APACHE POINT OBSERVATORY SDSS 2.5M >>>>=20 >>>> OBSERVING LOG >>>> Tuesday November 01, 2022 >>>>=20 >>>> (SJD 59885) >>>>=20 >>>> ---- Observing Team ---- >>>>=20 >>>> Dmitry Bizyaev >>>> Audrey Oravetz >>>>=20 >>>> ---- Observing Plan ---- >>>>=20 >>>> Tue 01 Nov 2022 59885 0.61 01:06 01:21 12:12 21:03 07:56 --- bright = until 07:16 ( 6.2 h, w/ 0.2 h for 12 deg design), then dark ( 4.9 h) >>>>=20 >>>> ---- Observing Summary ---- >>>>=20 >>>> Started with cloudy sky. Lost 3.7 hours due to the weather. Clear, = productive night with good seeing after that.=20 >>>>=20 >>>>=20 >>>> Notes >>>> ----- >>>> - dust accumulated: 6.4K >>>>=20 >>>> - note to John Donor: we've observed 2 designs out of 4 for field = 101800 at the beginning. The rms for guiding was consistently bad, ~ 3", = and we connected it to the low ALT of the field, ~ 34 degrees. >>>=20 >>> Dmitry and Audrey: Do you recall how many GFAs have solution for the = field? Maybe Jose and Conor can comment on this, but I recall that other = low altitude fields had good guiding RMS in the past. Our weather = station is down, it report a temperature of 92 C, could be due to the = fact that the temperature messes up the refraction?=20 >>>=20 >>> Conor: Can we use tcc set temperature to have tcc make the fraction = corrections with the manual set temperature? >>>=20 >>>> We decided to skip the other 2 designs, and pushed button X against = the first of them. As a result, the 2 designs were removed, but Kronos = then shows next design 119241 field 101746 as crossed, although we did = not load this design yet. As a result, we could not observe the first = design out of 4 for the field 101746. We danced with tambourine around = it and prepend the crossed design to queue. But... it turned out that = after design 119241 was loaded and even started being observed, the top = design in the queue became 119241 again! I reloaded the page by pushing = on Plan Observing - no changes. I tried to remove it with the cross near = it, and it was removed, but it removed all field 101746, 3 left designes = (as might be expected). The next, top design in the queue, as a result, = was fresh, but I noticed that it is a dark_monit field already, despite = 1 hour of bright time left. Then I reloaded the whole Kronos' queue = again, and only then the remained 3 designs for the field 101746 popped = up again, with high priority now. As you imagine, this choreography took = some time.=20 >>>=20 >>> John: If one design on a field is missing, and we are sure it has = not been observed yet, should we manually load it and observe it or if = you prefer us manually add the design to the observing queue (has not = try this yet, not sure this will work as expect)? >>>=20 >>> Thanks, >>>=20 --Apple-Mail=_5B1329E1-A811-4471-9E7A-FB99CB180BE0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I = believe the command would betcc set weather airtemp=3DX(https://www.apo.nmsu.edu/Telescopes/TCC/Commands.html#SetWeathe= r)But I = don=E2=80=99t think it will have any effect on something like guiding. = Once the guider takes over, it should drag the telescope to = wherever it wants it.On Nov 2, 2022, at 11:00 AM, = Jos=C3=A9 S=C3=A1nchez-Gallego wrote: Oh, but that definitively could have messed up the TCC refraction = correction itself. Conor may know about that.Jos=C3=A9 On Nov 2, 2022 at 07:59:03, = Jos=C3=A9 S=C3=A1nchez-Gallego wrote: Actually I think I never got around using current temperatures for = the refraction correction. I think it always uses 10C and RH 50% for all = coordinate conversions and refraction calculates. If the temperature was = very different during that field, maybe that would contribute to the = large RMS, although 3 arcsec looks very large.Jos=C3=A9 On Nov 2, 2022 at 07:55:31, = Kaike wrote: =20 = On Nov 2, 2022, at 6:30 AM, dmbiz@apo.nmsu.edu wrote: = &n= bsp; APACHE POINT = OBSERVATORY SDSS 2.5M = &n= bsp; &nbs= p; OBSERVING LOG = &n= bsp; &nbs= p;Tuesday November 01, 2022 = &n= bsp; &nbs= p; (SJD 59885) ---- = Observing Team ---- Dmitry Bizyaev Audrey = Oravetz = ---- = Observing Plan ---- Tue 01 Nov 2022 59885 0.61 01:06 01:21 12:12 21:03 07:56 --- = bright until 07:16 ( 6.2 h, w/ 0.2 h for 12 deg design), then dark ( 4.9 = h) ---- = Observing Summary ---- Started with cloudy sky. Lost 3.7 hours due to = the weather. Clear, productive night with good seeing after that. Notes ----- - dust = accumulated: 6.4K - note to John Donor: we've observed 2 designs out of 4 for = field 101800 at the beginning. The rms for guiding was consistently bad, = ~ 3", and we connected it to the low ALT of the field, ~ 34 degrees.Dmitry and Audrey: Do you recall = how many GFAs have solution for the field? Maybe Jose and Conor can = comment on this, but I recall that other low altitude fields had good = guiding RMS in the past. Our weather station is down, it report a = temperature of 92 C, could be due to the fact that the temperature = messes up the refraction? Conor: Can we = use tcc set temperature to have tcc make the fraction corrections with = the manual set temperature? We decided to skip the other 2 designs, and = pushed button X against the first of them. As a result, the 2 designs = were removed, but Kronos then shows next design 119241 field 101746 as = crossed, although we did not load this design yet. As a result, we could = not observe the first design out of 4 for the field 101746. We danced = with tambourine around it and prepend the crossed design to queue. = But... it turned out that after design 119241 was loaded and even = started being observed, the top design in the queue became 119241 again! = I reloaded the page by pushing on Plan Observing - no changes. I tried = to remove it with the cross near it, and it was removed, but it removed = all field 101746, 3 left designes (as might be expected). The next, top = design in the queue, as a result, was fresh, but I noticed that it is a = dark_monit field already, despite 1 hour of bright time left. Then I = reloaded the whole Kronos' queue again, and only then the remained 3 = designs for the field 101746 popped up again, with high priority now. As = you imagine, this choreography took some time. John: If one design on a field is = missing, and we are sure it has not been observed yet, should we = manually load it and observe it or if you prefer us manually add the = design to the observing queue (has not try this yet, not sure this will = work as expect)?Thanks, = --Apple-Mail=_5B1329E1-A811-4471-9E7A-FB99CB180BE0--