Date: Mon, 12 Dec 2022 08:27:54 -0700
Subject: Re: [sloan-25mlog 6398] 2.5m obslog 20221210 (SJD 59924)
From: "Daniel Oravetz"
Based on the preload/load commands, it looks like each configuration
should be different because the --no-clone flag was used as needed for
each --safety-factor after the very first one:
2022-12-11 01:23:26,421Z > APO.dgatlin 175 configuration preload 231443
--safety-factor 0.5
2022-12-11 01:51:40,813Z > APO.dgatlin 183 configuration preload 231443
--safety-factor 1.0
2022-12-11 01:53:44,764Z > APO.dgatlin 185 configuration load --no-clone
231443 --safety-factor 1.0
2022-12-11 02:11:58,487Z > APO.dgatlin 192 configuration preload
--no-clone 231443 --safety-factor 1.5
2022-12-11 02:33:01,426Z > APO.dgatlin 200 configuration preload
--no-clone 231444 --safety-factor 0.5
2022-12-11 02:52:21,342Z > APO.dgatlin 208 configuration preload
--no-clone 231444 --safety-factor 1.0
2022-12-11 03:16:11,804Z > APO.dgatlin 216 configuration preload
--no-clone 231444 --safety-factor 1.5
> Sorry, to clarify, for this MJD were the offsets designs configured with
> the —no-clone option (i.e. the offsets were different for each safety
> factor) or was this not used that night (i.e. all exposures are cloned and
> the offsets did not change from exposure to exposure)?
>
> Best,
> Ilija Medan
> ---
> Second Century Initiative (2CI) University Doctoral Fellow
> Georgia State University
> http://www.astro.gsu.edu/~medan/
>
>
>
>
>
> On Dec 11, 2022, at 3:08 PM, José Sánchez-Gallego
> > wrote:
>
> Hi Kaike, Dylan,
>
> Yes, loading the same designs with --safety-factor won't change the logic
> for cloned designs; it will be cloned unless the age of the design is more
> than 2 hours. Use --no-clone and --safety-factor if reloading the same
> designs with a different safety factor.
>
> Thanks,
>
> José
>
>
> On Dec 11, 2022 at 08:02:21, Kaike
> > wrote:
> Thank you, Dylan for getting data on these commission tasks.
>
> Jose:  Dylan reports that ”jaeger configuration load” with
> “—safety-factor” results loading a “cloned” configure if the
> same design is loaded for a different safety-factor, which mean that
> robots will not move since no new paths are calculated. I think that Dylan
> use both “no-clone” and “safety-factor” options to load the same
> design, different safety-factor”. Will this do the trick?
>
> Dylan: we can use the twilight flat script to take dome flats in the
> evening.
>
> Thanks again
>
> On Dec 11, 2022, at 6:01 AM,
> dgatlin@apo.nmsu.edu wrote:
>
>
>                       APACHE POINT OBSERVATORY SDSS 2.5M
>
>                                 OBSERVING LOG
>                          Saturday December 10, 2022
>
>                                  (SJD 59924)
>
> ----  Observing Team ----
>
> Dylan Gatlin
>
> Kaike Pan
> Jose Sanchez Gallego
> John Donor
>
>
> ---- Observing Plan ----
>
> Sat 10 Dec 2022 59924 0.91 00:55 01:10 12:42 23:25 11:00 --- dark until
> 02:03
> ( 0.9 h), then bright (10.9 h, w/ 0.3 h for 12 deg design)
>
>
> ---- Observing Summary ----
>
> A clear night with stable seeing starting around 1.5", but eventually
> working
> down to 1". We were able to get two offset designs and four dither
> designs.
>
> Offsets are for designs 231443 231444. Starting with 0.5 safety factor,
> ending
> with 1.5. See main log for exposure numbers
>
> Dithers are for designs 35890, 35900, 35914, 35926 with a non-dithered, 6
> dithered, 1 non-dithered, 6 dithered, 1 non-dithered. 300s each. See main
> log
> for exposure numbers and cherno offsets
>
>    Time  Field-Design Cadence                  APOGEE    BOSS
> Completion
> 00:33:38 104436-128414 bright_single_15x1_v1    1xAB      1x900s  Done
> 01:19:33 100619-115218 bright_single_9x1_v1     1xAB      1x900s  Done
> 01:38:06  23148-231443 Offsets                  6xAB      6x900s  Done
> 04:06:17  16189-35890  Dither                   1xA 0xB   15x300s Done
> 07:01:04  16199-35900  Dither                   No APOGEE 15x300s Done
> 08:40:53  20883-35914  Dither                   No APOGEE 15x300s Done
> 10:19:48  20895-35926  Dither                   No APOGEE 15x300s Done
> 12:00:37 101285-117583 bright_1x1_v1            1xAB      1x900s  Done
> 12:23:12 101271-117566 bright_1x1_v1            1xAB      1x900s  Done
>
> APOGEE Dome Flats
> Missing Fibers: [21]
> Faint fibers: [25, 75, 225, 289]
> Average Throughput: 0.921
>
> Notes:
>
> - Because we had less than an hour of dark time, Kronos couldn't find
> anything
> to fill the dark time, so it's actually a fully bright night, despite the
> plan.
>
> - After the apogee cals finished, I still didn't see the FPI image in the
> /data
> archive directory. I looked in the logs and saw a weird authorization
> error,
> and assumed the cal sequence failed, and took a 30-read FPI manually.
> Turns out
> it was just the disk being slow and the error was something Jose was
> testing.
> No issues, we just have a bonus FPI exposure.
>
> - After taking twilight flats with the STUI script, the HAL window showed
> the
> "in progress" wheel on the dome flat run button for the rest of the
> night.
> Later on this also happened to the science exposures when I ran a hal
> command
> in stui to start a science sequence. When the in progress animation is
> playing,
> it cannot be cancelled and you cannot start a sequence.
>
> - The command jaeger configuration slew failed for my dither fields with
> the
> following error. I slewed using HAL
>
> 03:54:11 APO.dgatlin 153 jaeger f error="Cannot slew to a dithered
> configuration."
> 03:54:11 CmdDone: APO.dgatlin 153 jaeger configuration slew
>
> - After loading a new dither field, I ran a configuration reverse from a
> dithered position back to the undithered position, then again from
> undithered
> to folded. One of those two reverses seems to have loaded a new config
> and
> loaded the previous design again!
>
> - Integrated dust counts: ~1900 dust-hrs
>
> ____________________________________________________________
> Logs of Nightly APO Activities
> >
> https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html
>
>